4.11: Some Missions Locking-Up

[JtD]

That's really odd. On the software side, what changed over these couple of days?

FWIW, I just loaded the Solomons maps into my FMB no problem.

[majorfailure]

Problem still present here, too.

Coop on Iasi Map, there are long breaks (10-30 secs), where the game seems to freeze, then most of the time the game continues, but sometimes it crashes altogether. The Il2fb.exe process in Windows Task Manger at these points decreases its memory usage by ~100meg and reduces cpu percentage. If it crashes cpu percentage stays low(0-10%).

Seems to be related to Iasi Map, had a very similar campagin on the Krim map for ~20 missions with no crash and very little breaks ever.
And the load of the Map seems a factor, too, if I add enough flights of planes (40+planes), to get the whole mission stuttering all the time I can get the game to crash almost reliably within ~60 minutes. If I do load the same mission twice, then the game does not crash at the same mission time twice.

[KG26_Alpha]

Originally Posted by JtD

FWIW, I just loaded the Solomons maps into my FMB no problem.

Same here, even on an old laptop I use solely for editing in FMB, all Solomon maps are fine.

All of my updates are through torrent so the check sums are ok.

[Aviar]

Hold your horses....I may have found the answer to my problem. I still need to do some testing before I post anything.

Stay tuned for developments!

Aviar

[Aviar]

Well, for now, I seemed to have found a workaround for my problem. This is what I did.

I took my Missions folder, which has grown quite large after 12 years of missions (254MB) and replaced it with a 'clean' Missions folder from 4.12. That one is only 142MB. As soon as I did that, I could open any Solomons map in the FMB.

I'm not sure why that was an issue, but I tried it on a hunch and it worked...for now anyway. It's an easy workaround for when when I need it. I even tried adding back my more important missions and it's still working (at 203MB now).

Possibly it's some kind of memory issue. As I stated earlier, I don't have this problem with HSFX 6 and for one thing, I know they have made some core changes to IL-2. For instance, the HSFX il2fb.exe is only 156kb, while the stock 4.12 is 4.33MB.

In any event, I think I have it under control for now so we'll see what happens.

Aviar

[KG26_Alpha]

Originally Posted by Aviar

Well, for now, I seemed to have found a workaround for my problem. This is what I did.

I took my Missions folder, which has grown quite large after 12 years of missions (254MB) and replaced it with a 'clean' Missions folder from 4.12. That one is only 142MB. As soon as I did that, I could open any Solomons map in the FMB.

I'm not sure why that was an issue, but I tried it on a hunch and it worked...for now anyway. It's an easy workaround for when when I need it. I even tried adding back my more important missions and it's still working (at 203MB now).

Possibly it's some kind of memory issue. As I stated earlier, I don't have this problem with HSFX 6 and for one thing, I know they have made some core changes to IL-2. For instance, the HSFX il2fb.exe is only 156kb, while the stock 4.12 is 4.33MB.

In any event, I think I have it under control for now so we'll see what happens.

Aviar

I don't see that as being an issue unless you have other problems as mines nearly a 1 gig in size.


The only people I know online who have problems with the Solomons map, joining a CooP,
were those who had messed up installations or problematic PC's and that's with HSFX 6


If there were any memory leaks there would be more reports of problems with the map IMHO, unless you meant on your PC.
.





I wonder if some investigation into performance of your system when it locks up to find the root cause of the problem,
it's strange the HSFX v Stock comparison though as it makes no sense removing a few mission files allows the map to open !!


Good luck.





.

[Aviar]

Alpha,

Yea, it's a strange situation. I really shouldn't make any speculations at all because I have no clue what could be causing my issue.

As I stated before, I don't have any 'problems' with Solomons maps/missions. I can play/host any Solomons mission as well as use the Solomons map in the QMB. The only issue I have (had) is actually LOADING a Solomons map/mission into the FMB. This is where my game would freeze before the map would even load. I would need to exit to my desktop and shut down the game from there.

As far as having a 'problematic' computer, I guess that's always a possibility. However, consider the fact that I have no such issues loading Solomoms maps/missions in HSFX 6. As you know, To create a working version of HSFX 6, you need a clean install of 4.11 and then add your HSFX mods/files on top of that. So basically, HSFX 6 is just a souped-up version of 4.11.

Yet, my 'Solomons' issue started with stock 4.11 (and now continues with stock 4.12). Common sense may tell you that a 'problematic' computer would cause this issue to be present in both stock and HSFX versions. However, that is not the case. This is why I keep reporting any findings I come across. Maybe someone can one day come up with an answer.

In my own little world, I'm happy that I have at least found a workaround. A 'workaround' does not mean that the problem has been identified. It's simply a temporary solution to sidestep the problem until it gets correctly identified.

I know I was kind of pointing to the fact that MY Missions folder was so large and maybe that might be a clue. That seemed like a logical assumption, but after looking at YOUR missions folder (which is almost 4 times larger), maybe size can be ruled out. However, maybe there is something in MY Missions folder (but not in YOUR Missions folder) that may be the culprit. Then again, I used the same Missions folder with my HSFX 6 and I had no problems there.....so confusing.

I've run out of things to say, but thanks for at least being concerned.

Aviar

[KG26_Alpha]

One test would be to move the problematic mission folder to another stable IL2 v4.12 machine and try to break the FMB that way.







.