Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Berserker]

Does this have problems with some systems? I'm running Vista 32, UP2, and some SAS mods on top, and I keep getting paratrooper.sim error when the mission loads. Any ideas?

I have the same error, and in some missions the game completely down. For example flying a mision over Crete map, 4 Hurris, 12 SM79 and
4 MC200 and when start the mission I only cant see the propeller (without cockpit or something) and after few seconds the game completely freezes

I have Dual core 6750, motherboard gigabyte P-35C ds3r-atx socket 775, 3G DDR2 Pc 800Kinston, VGA PCIE GF 8800GT 512MBBFG OC, WESTERN DIG 500GB SATA2 16M 7.2K .

I haven't any megamod packs installed.


Actually I have very very interested in this MOD, any idea why this happens?

[Spinnetti]

ATI Radeon HD 2600XT, 256 mb. Not sure what driver's I'll check later when I can.

I've got ATI, and can't get these to work either. Tried various drivers, dlls config.ini settings... either get the paratrooper errors or ctd on mission start. I've got a i7 quad core, 4 gig mem, 4850 vid card....

[Birdman]

For me it seems like that the Paratrooper error just means that the IL-2 runs out of memory it can reserve.

If you use the 1GB .exe, then the Java core of the game can use more memory and that leaves less memory for other things like preloaded sound samples or textures. After loading the core, sounds, textures and all other things there may not be enough memory available at the end of mission loading and that causes the famous Paratrooper error, that appears with maps with a lot of textures (Channel map loading issues) or when preloaded sounds use some memory (UV2 issues).

To solve this issue we can use any method that either reduces memory consumption or increases the amount of memory available for IL-2:
- reverting to the original .exe to reduce the memory consumption of IL-2 core (all advantages of the new .exe are lost)
- texture compression to make textures smaller in memory (I don't like this because of image quality issues)
- downsizing of textures (used in HSFX/Ultr@Pack to get rid of errors with Channel map)
- remove preloading of sound samples (will cause stutters when someone spawns online with new plane type)
- increase available memory from 2 GB to 4 GB in 64bit systems with the 4 GB .exe version (I solved all my paratrooper errors with this method)
- adjust 32bit Windows to allow IL-2 use more memory (this method is worth trying, but none seems to have tried this and I don't know how it can be done)

The appearance of issues depends on many factors because at least size of graphics memory, display drivers and SLI/Crossfire may affect the memory requirements, and 32/64 bit Windows with different settings offers different amounts of memory for IL-2.

[Birdman]

I really haven't seen any paratrooper error or other weird error since I started using the 4GB .exe, although I've tried some torture testing like maximum number of different planes in QMB on Channel map (the HSFX version with smaller textures) with my flying in the 250 MB cockpit of Bf-109. That test caused stutters (due to only 512 MB graphics memory per GPU filled by cockpit textures), but significantly less than with original .exe.

I have Ultr@Pack 2.0 as base install with a lot of mods on top, but I don't have the UV2 yet.
I also have 4 GB RAM, but I have Vista x64, Q6600 @2.4 GHz, 2x GeForce 8800GT in SLI with 185.85 drivers.

[kreed]

I'm using UP 2.0 with the 1 GB modified Exe, had al lot of paratroopers mono.sim errors.
I have only 1GB RAM and an old NVDIA 6800 videocard.

Using texture compression in the setup (STC3) improved al lot for me, but what really did the trick was
changing the Texturecompress=0 to Texturecompress=2 in config.ini.
No more errors, and overal a smoother performance without loss of quality.

[agracier]

changing the Texturecompress=0 to Texturecompress=2 in config.ini.
No more errors, and overal a smoother performance without loss of quality.

I looked in my own config.ini and could not find any line with 'Texturecompress' - nowhere to be be found.

While I don't have any problem at all with this mod - it works just great - I would like to know what 'texturecompress' does and where it should be located.

Can anyone give me the relevant lines?

[kreed]

Sorry Agracier, I made that post at my work, but indeed I meant Texcompress.

Did it work for you?

[alotef]

Thank you very much for a useless mod which not only managed to crash my IL2, but somehow managed to bugger up the entire install, so when I replaced the modded .exe with the original, it still crashed. Great, great stuff.
 

[SAS~CirX]

We are all so sorry. Next time make a backup of files that may be affected and rewritten by the game before trying anything like modding it. These would be the ini files in your main game directory. But even so, we are surely horrible irresponsible terrorists, who fully deserve scorn, and you are clearly entitled to having all the money back that you paid to be a member of this forum.

My deepest appologies, on behalf of myself and all the...how did you put it?...
... horny old men , who hang out at this creepy site.

Cheers!
 

[alotef]

You misread me.. I did not mean the SAS site is for horny old men.. I meant the 'Babe of the week' thread, not the whole forum (Thew topic the image above is taken from is about an AAA 'babe of the week thread;, which I thought would be a bad idea). And yes, I would like my money back, considering I paid so much!
Anyway, you know what it's like when you get home from work, and IL2 buggers up.. Super frustration. I'd just like to get this thing figured out, so sorry for the snide comments.

So I did back up everything the readme told me to... But still, I get CTD or a white screen... Which is not good for me. -_-
Any ideas?

[alotef]

Ok, will try. Thanks Bravo.

[SAS~CirX]

good luck with it. Gerard, that chick is fucking awesome! Dimples is ass and everything! Thanx for making my day!!