seowhq.net

Tanker wrote: 242 Tanker and 242 Cat had a freeze and disco at about one hour and five minutes into mission. Both of us had it almost simultaneously. I'm not really sure how to tell which exe I was using. I think it was the 512.

Please can you zip the il2fb.exe file and send it to me?
E-mail sent via PM

Thanks
Maraz

6S.Maraz wrote:

22GCT_Gross wrote:We experienced similar troubles during the J42_Midway/Crimea (see the forums below).
By the internal DSC log I found the disconnected people stopped to send their data to the server. During Midway it seemed related to a naval task force turning. During Crimea to a concentration of players/objects fighting in the same area.

I will restore the crashes, but I need the time...

The graphic card has been just updated. Hope it helps.

It could have been a memory issue.
We experienced this problem in Midway-J42, at that time we had smaller exes.

Maybe with larger exes this problem happens later in the mission, at that time the Garbage Collector has a lot of memory to "clean", this might fail on some PCs due to their configuration.

Did also other players experience a freeze at the same time, I mean also those who did not crash?

Also we would need confirmation of which exes pilots were using.

Thanks
Maraz

Yes, from 102nd all of us had freeze at exact same time. Time was something about Tanker said 1:05-1:10, not sure.

i had no problems. i do not use any extra memory exe.

also i can say that in the moment of the problem i sow a ship going in one direction and then turning for 180 in lace

Myself and Thor both had complete freeze at the same time...

both planes/pilots were claimed "KIA" in the stats...bummer

22GCT_Gross wrote:We experienced similar troubles during the J42_Midway/Crimea (see the forums below).
By the internal DSC log I found the disconnected people stopped to send their data to the server. During Midway it seemed related to a naval task force turning. During Crimea to a concentration of players/objects fighting in the same area.

I will restore the crashes, but I need the time...

The graphic card has been just updated. Hope it helps.

Thankyou Gross, 3 EAF gunners were also taken out with this error, EAF331_Starfire, EAF92_Keets and myself EAF19_Classic

I'm working on a copy of the database to test the corrections

6S.Maraz wrote:

Tanker wrote: 242 Tanker and 242 Cat had a freeze and disco at about one hour and five minutes into mission. Both of us had it almost simultaneously. I'm not really sure how to tell which exe I was using. I think it was the 512.

Please can you zip the il2fb.exe file and send it to me?
E-mail sent via PM

Thanks
Maraz

Sure.

I restored the 11 crashed players so flagged in the database:

Then I restored all the others disconnected around 13:11

Thanks, mate

S!

I've flown 2 missions and had 2 disconnections. The game freezes and I get kicked to desktop.

I've had the 512 exe in use on the first mission and 512 6dof on the second.
I have now done a complete reinstall of the game(IAF.Viff suggested this) and will try again on Monday. Hopefully it works better this time.
But I am grateful for any ideas you guys may have that could help.

Please all players check they have the 512 MB exe enabled.
If you are unsure about your exe, install it again from folder "HSFX V5 Tools & Read me's" file All_Ivans_il2_exe_s.

Two of the players who crashed last Thursday had the 256MB exe instead of the 512 (they were the only player whose exe I could check), so we are almost sure that the 256MB exe is not enough for this campaign and it might cause a crash due to lack of Java VM memory.

Thanks
Maraz

S!

The amount of lag in last mission was horrid. When the action got intense, we got lag spikes freezing the game for 1-2s every 5-10s.. and they were perfectly timed on every moment I was about to pull the trigger

Hi guys. Good SEOW and fun.

But this is the problem for me. In yesterdays mission, I had terrible lag the first 6-10 minutes of the flight. Then it smoothed out and was good until about 90 minutes when we flew in over Guam to attack AAA positions, when I got terribly low FPS when looking towards land and AAA guns firing.

Once over the water things were fine, until we got back to the CV and the low FPS started again when looking at the CV. About 15 mins later when over open water the game crashed to desktop. So about 2h 15 mins of play time for me. Another aircraft lost to CTD. Three out of three for me.

Apollo EAF331

We have been investigating since Guadalcanal campaign on 2007 about disconnections during massive campaigns. Marianas is probably the heaviest campaign ever flown, isnt it Charlie?

The main issue is the Java Il2fb.exe allocated memory (96Mb in the stock version)

Most of the problems were found in the same way by playing the same mission off line. So problems on packet exchange from/to the server can not be excluded in principle, but we had never evidence of that.
On the contrary, analisis of disconnections tells us that the server keeps on trying to send packets to the client but no packet comes back from the client.

We dont know how il2 manages the dedicated memory, but it seems clear that the memory consumption is affected by:
- type of the map and its textures;
- nr. of AI static objects;
- nr. of AI moving objects;
- effects (flaks, smokes etc.)
- nr. of players connected;
- density of the objects in the same area;
- use of track ir;
- some cases told us that multiple disconnections happened just at a naval convoy turning;

Il2 is not able to clean the memory used, so we have to front a progressive increasing of the dedicated memory usage.
The only solution we have found (thanks to rnzoli & 72sqIva) was to edit the stock il2fb.exe and increase the Java dedicated memory value; that is as we put more fuel in our plane to fly a longer distance.
The more the memory is increased (256, 384, 512, 1Mb or 2 Mb) the more the graphic handling on the pc becomes unstable.
That's why we recommend to use to lower version of the modified file able to sustain the mission.

When the memory limit has been reached, Il2 stops working. No packets are sent to the server and you're out of the game. You have 131 seconds to establish a connection back to the server; after that, the sever will kick you out (cheating has been detected message).
The time the memory takes to limit depends on the speed which the memory has been used, that is different for one flying alone across the see than one flying into a furball.

Lags
you are not syncronized; you are not sending packets to the server for a while, or you have a different netspeed setting on your conf.ini. [You Apollo have netspeed = 5000 (5000 byte/sec * 8 bit/byte= 40kbit/sec) instead of 10000 byte/sec as default value for seow campaign.]

Low fps
It depends on local graphic card capability.

ATI
Sometimes we noticed malfunctions (CTD) on players equipped with ATI GC. Someone solved installing older drivers.

Player list
We noticed that scrolling the player list in the ready room or opening the map in the very first part of the mission can lead you to overlay the Player list to the game screen. Avoid to scroll or open the map.

Tranferring mission
Sometimes you got the transeferring mission screen while playing. No informations on this bug at the moment.

Freeze
there is a case where the freezing was due to an overclocking on the graphic card. Restoring the default setting, no more freezes.