![]() |
Quote:
it is the blind leading the blind in forums like this, why believe he knows anything more then you do ? there is a few posters here who have some inside information, as beta testers etc..., but he aint one of them thats for sure right now you know about as much as anybody else here, or even more because you have tried to approach 1c to fix it and seen for yourself how important they judge it. from the information we have to go by right now, dont hold your breath waiting for it to be fixed. |
Quote:
naive, is for you to have any confidence in it being fixed, just because you seem to believe il2 is perfect and everything that is identified as a problem will always get fixed cynical, is for me to believe it is not going to be fixed, just because i have noticed 1C have already overlooked so many other important bugs that could have been easily solved |
Quote:
I simply stated that the bold text in your quote I reiterated was a naive one to make, nothing to do with the claims you are making at me now. Ranting away at 1c in this thread is not helpful. Quote:
This may help you. http://forums.ubi.com/eve/forums/a/t...5/m/4521077615 Sorry I could not be any more help to you e69 v. Merry Christmas. |
Quote:
I was just waiting for an "official answer" when I opened the post. I was wondered that nobody reported this problem in this forum. And I wanted to avoid that Maddox Games could say that nobody reported this error and we never solved it for that reason. Now if they will not solve this problem is because they don't want to solve it. Thank you Alpha and Merry Christmas. |
This is highly unlikely to be fixed since all work on il2 has stopped.
|
Quote:
|
Quote:
|
All times are GMT. The time now is 06:40 PM. |
Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.