FoolTrottel

Dunno how I do it or why it does happen to me again, but the very first mission I load to check the running of the RC2 gets messed up pretty badly. The mission is 'Balaton Zerstoerer', the eight 109's that are supposed to be in are all missing, and the 110's who should be ready for take off float at 10m to 200m, as speed 0, and then crash. Can't exit the mission, as the Quit mission button clicks, but does not quit the mission. Looking at the log.lst file, something's wrong while it tries to load the Bf-109G-6Early(hu) stuff.... Can anyone please try and play attached mission, just in Single mission? TIA! (Put both files that are attached in your Mission/Single/DE/Bf-110G-2 folder, then 'play' the single mission.) Edit: Think this is related to the Hungarian Regiments/Squadrons. As soon as I select one of those (like 102 Vadaszosztay or the ones below that) it goes haywire... Oh dear oh dear, how I hate this mess!!! Balaton_Zerstorer.mis Balaton_Zerstorer_ru.properties

Just for the record: Cause was a lot of files (like the mission files) had their Read-Only file attribute set. The fix was resetting that attribute for all files and folders in the game folder.

Oops... well... they do not appear when you load the mission in Multiplay you mean? That's really strange... how do they appear when you load that mission in the full mission builder, after you've changed it with QMT? Is QMT looking at the very same folder you are loading the mission in IL2 from?

Me thinks the latest models are not in your QMT... yet ... you did get an update to it though, but was it an update specifically for UP30 ? Edit: Tempest FB MK II is in my version of QMT... The QMT_Aircraft.txt is attached here, download it and put it in the folder where QMT is installed QMT_Aircraft.txt

UP3 uses files named il2corSSE3.dll and/or il2corSSE4.dll, whereas 4.10.1m uses IL2Core.dll and/or ILCoreP4.dll. In other words, they use different modules for the graphics... UP3 uses files named il2corSSE3.dll and/or il2corSSE4.dll, whereas 4.10.1m uses IL2_Core.dll and/or IL2_CoreP4.dll. In other words, they use different modules for the graphics...

The troubles I ran into with that Western Front / Tempest II mission are all fixed by a fresh install, and mainly a fresh conf.ini... something must've been wrong in the old one...

+11

Welcome here! Someone that can really 'add' you to the group will be along here in a while... (Hm, maybe I could even do that, but wouldn't know how...or what to do...Oh well..) (A sheepfarm, oh dear... wonder what comments will follow... ) Anyways, as I said, Welcome!

Very nice pictures Swep, you apparently not only look like a professional photographer... Maybe try it out at Duxford?

Either assign a separate button/key for it in Controls, or add this to your conf.ini: [Mods] BombBayDoors=0 (This prevents you to even have to open them, they then work as in the stock version: Fully Automatic.)

Think I have found what was causing the troubles I ran into. Given (after some more testing:) - Map Western Front Summer - Not too big a mission, but lots of action still. - Issue with garbled screen occures after using Shift-F2/Ctrl-F2, so switching views/camera's (when one's killed early in the mission, one tends to use those views quite a lot, also when one is testing a mission one just built.) - Errors in Log.lst: GL error 0x0505 (which could mean -according to some googling- OUT OF MEMORY.) - Errors in Log.lst: WARNING: Camera: unexpected 'ActivateWCM' Using some google, I ended up on the ultrapack forums, where someone was getting these errors. And he fixed it by using 'a different conf.ini'. Well, my conf.ini (as the complete UP30) is just a very recent copy of 4.10.1m which runs quite nicely. Opened it up... and thought a bit.... calculated 1+1.... decided it could be three here -me jumping to conclusions- and attempted to set LandGeom=3 back to LandGeom=2 ... and voîla, no more graphics garbling up here... Mission now runs fine, I can follow all views untill the C47's and the 190's have landed at their home base... Then doublechecked it, by setting LandGeom=3 again, and for sure, some 15 minutes into the mission Mayhem joins in again... So, here's a question for the ones that tested this Tempest IIFB based mission with me: What's your Landgeom= set at? (it's in the [render_OpenGL ]section of conf.ini)

Getting a bit worried about UP 30. On my system, the 'bigger' maps (new ones, like Western Europe) with a newly created mission (Tempest IIFB, w00t!) when I host it as coop, after some 15 to 20 minutes, my screen becomes garbled when looking at the ground, looking at the skies initially clears it up, later it's all messed up and the game comes to a complete stand still, though the computer does not. Also a lot of crashes (no error message, just game exit, a hispiderr...log is being created, while building this mission. I have to try and figure out if I caused the problem by using certain objects (test runway 5?) or there's maybe too many objects? (Total lines in the missionfile is 1300, so it's not that big). Anyways, I'm getting the impression they've now put more in than the original engine could handle... hence the introduction of that sub-menu when starting IL2?

Beau X is the one with gunner... it is absent? It's not over here, using FB's files... As for the empty folder, select any folder below coop that has missions in it... like coop\0 Cephas PF? TS/TV session?

(...) As a programmer, I really don't like it when they fix things that are not broken, like the shippack stuff. Yes, it would be nice if it was part of the original ships, but if that is the only reason they made this fix... that broke 100's of missions, then that was a bad fix... But they seem like smart guys, and maybe there was another reason I hope... Well, they are smart guys, but they did mess-up. In my opinion, they messed up in 2.0, by creating that 'Shippack.' stuff. That was completely weird, it was a dirty trick to keep the new ships separate from the existing ones I think. And now, they appear to have fixed that mess. But, by doing so, they did not really think of the consequences, as to keep it compatible. And, changing them aircraft names is just silly... I found they've also gotten rid of C_47A, F4U1.... silly... Oh well, there's ways to get around it...

They do not show up in the Full Mission Builder? One thing I found out is that in the FMB the sorting of the list of name is done in a kinda creative way.... (Similar in the QMb, there you can select to sort 'alphabetical', dunno what ABC they've been using, I'm not familiar with that one. Like this: Hurricane ... Hurricana ... Sea Hurricane ... SeaHurricane ... Sikorsky ... Sikorsky ... I-15 (...) I-153 I-16 UTI-4 type 16, 1937 I-16 I can see why one would want to put the Sea Hurricane near the Hurricane, but why is the next one a Sikorsky? And there's more like that. What aircraft are you missing?

Well, there's 3 ppl on TS now... so hop in... who knows we might be able of help...

Thanks! Nice read!

To get into it, I've re-worked Taranto (Nighttime colors are rather different as of 4.10.1m, the night is pitch black now!) and Naro Fominsk (A mass of 110's attacking village, in the orginal mission they were G2's, for 1941 now less incorrect: C4's, C4/B's, F1's, F2's.)

Welcome!

Just outside of Dover. Outside of Dover? Me thinks your nick should be 'bongodiver' ?

School?

Maybe a Swedish windows version won't allow loading a Finnish map?

What Crash said, and this from the bug thread at up's forums: "Solution: Enable expert mode, 4GB address space and 1200MB of memory in the IL2 selector and try again." Edit: 1200Mb crashes IL2 on my system, so as you're on XP as well, try 1024, and leave the 4GB address space off.