Hi all,
as far as I know many had the problem I experienced with the CannonUK maps regarding the mono.sim not created with the russian paratroopers that hangs the map before it loads.
We know that the workaround is setting the TexCompress to S3TC and enable the TextureARBExt, but what is the problem itself? I tried to use the mono.sim (and all the files) of the German paratroopers (only these two are embedded at the game) but it still hangs up at the same place.
One strange thing I realized is that after having set the TexCompress, the other typical problem many had (when the FMB hangs its visual when you switch or change the properties of a new plane as the Halifax) have dissapeared too.
I'm using an ATI 3800 series card. Do all the rest of the users with these problems share the same video card?
Isn't there a real solution instead of a workaround regarding this? Which is the real cause of this behavior?
Thanks,
Pablo
... i wouldn't know i have NV9800Gx2 1G and still no joy without text. compression for that map
I have pretty decent system ( Intel Quad 9550 @283Gh ... clocked at 3.65 ... 4Gb DDR2 ) so i believe reason is game engine and new objects or way they have been introduced ( pure speculation here )
don't know if that helps ...
Z
Posts: 47
Threads: 8
Joined: Mar 2008
Greetings Flyzo and benitomuso, could you two pro's help this amateur with how to "setting the TexCompress to S3TC and enable TextureARBExt" - I'm really lost here. I run 1.11 (not new 4.09) and Nvidia 8600 GTS card. Please be kind enough to help with to reset these two settings. Thank you in advance. DW
I have tried the Channel maps in two PCs, one has 2x GeForce 8800 GT in SLI and the other has one GeForce GTX 260. The GTX 260 PC loads the map without texture compression in simple cases, but today I got the mono.sim problem when I tried to test fly the new SM.79. The other PC can't load the map like fly_zo's PC. Both PCs have 64bit Vista, 4GB ram and Quad core CPU.
It seems that the Channel map needs more than 512MB graphics memory for uncompressed textures, and even almost 1GB is not enough to fly a complex multicrew bomber. Thus I'd like to see a light version of the map with smaller textures for new objects and less textures.
Yes +1
Channel map lite please!
Eckhart
ps: and I am running a GTX 295 hydrocopper, Asus STRIKER II NSE,
Intel® Core™2 Extreme CPU Q6850 @ 3.00GHz, Windows Xp SP3 Pro, 4 Gb DDR3 1067Mhz RAM....no joy without texcompress for this map ... no fun...all the rest blazing 60 FPS all maxed out
DocktorWho; Both of these settings should be in your game's config.ini file, located in your game's main folder.
Open it using notepad and scroll down until you find the section called; [Render_OpenGl] . Find the line that reads; TexCompress=x ("X" being whatever value is currently there). Change it to read; TexCompress=2.
Now look further down in the same section until you find TexCompressARBExt="X". Make sure it reads TexCompressARBExt=1.
Save the changes and close the file.
Birdman,
that's very said wht you said. 512Mb should be enough for many, many things. It's a pitty that it isn't enough for Cannon's map.
Have you ever seen the other effect that I told? It is specially evident with the Halifax plane. If being in FMB you try to switch the player checkbox to make it the flyable one, it makes that ugly screen where you only see a section of the FMB with the cursor reference moved: a full mess and usually you have to close the IL-2 by shutting down the application. I think that with the HE-219 and other new planes the same happens. This is something that is solved with the texture compression too. Why? Here is not so logical as in your explanation of the Channel map.
Texture compression is not terrible, but it impacts some detail level in the cockpit of the planes.
DoktorWho, the Murph explanation es perfect, you should do that and you will solve the problem.
Thank you everybody.
Posts: 47
Threads: 8
Joined: Mar 2008
Many thanks Murph, that was a big help.
DW
