4.33u3 CTD on start
-
Win 7 is absolutey fine
-
Yes 4.33u3 works fine on my Windows 7 x64 install… but I can’t use my FLCS+TQS there, well not until I’ve coverted them to USB.
Will 4.33u3 have any issues if the throttle and stick are 2 separate USB devices? (Instead of 1 device?)
-
heya Tazz
cant remember of the top of my head (someone will pop up soon ) how many devices BMS can see but I see no reason why throttle and stick cant be separate
edit
do a search here and you see guys running cougar throttle and warthog stick so indeed its possible
-
Looks like I will need to get this conversion started sooner rather than later because I’m having some issues with 4.33u2 under XP as well.
I created a TE with a carrier group (CVN with single and dual Super Hornet Squadrons and a E-2 squadron) , added some A-10C squadrons to Osan, based my F-16CM Block 52 Squadron at Seoul and added both a KC-135R and E-3 Squadron as well.
And a bunch of enemies to shoot atAll goes well, I can ramp start, take-off etc. But I noticed as soon as the tanker called for take-off, I would CTD. So I removed the tanker from the TE.
Then I got half way to my target , after using the carrier group to boresight my AGM-65Ds, and I just randomly CTD.I’m sure it’s due to me running this under XP - perhaps I’ll reinstall just 4.33u1 and see how that goes while I’m waiting for my parts to arrive from China.
The carrier group was awesome though. Couldn’t believe my eyes …. a full on carrier, with Hornets taxiing to the cat and lauching… nearly flew into the sea as I kept looking at the deck action
-
Better redo a same mission from scratch. Maybe u found something that might be an actual bug. I’m talking about the once tanker… I get a CTD.
Before that I would suggest a reinstall.
sent from my mi5 using Tapatalk -
Better redo a same mission from scratch. Maybe u found something that might be an actual bug. I’m talking about the once tanker… I get a CTD.
Before that I would suggest a reinstall.
sent from my mi5 using TapatalkYup, I did that. While going through the aircraft views to have a peek at the A-10s and F-18s (using the 8 key), I noticed a bit of lag, a bit of hard disk rumbling and then the game crashed. I wasn’t quite sure why BMS 4.33u2 was lagging when switching these views and it was that contributing to the crash…given that it was installed on a Black Caviar WD 1 TB drive, which aren’t super slow or anything.
So I did a fresh install on my Samsung 840 Pro SSD and redid the TE but still experiencing these random crashes and occasional lags while quickly going through other aircraft view. I’ll do another fresh install and this time see if I can repeat the issue with 4.33u1.
-
You need to post a crashlog. Sounds more like a graphics issue.
C9
-
Quickly changing external views has this common issue.
sent from my mi5 using Tapatalk
-
I’ll try to post a crash log shortly. After reinstalling 4.33.1 (leaving it on U1 to see if that works better on XP), I’ve had no issues creating TEs and flying them.
However, last night I tried a campaign (Rolling Fire). Rampstart is fine, I get airborne … but at random times between me leaving Osan and actually reaching the FLOT, the game would CTD.
So it seems like if things get really busy, it just crashes. At the time it crashed, I wasn’t using any external views. I had my head down in the pit, navigating and using the FCR. As soon as I get home tonight, I’ll see how I can post a crash log.
-
Link to the crash log is here: https://www.dropbox.com/s/92yvw197pjuax9f/2017-06-12_221121_crash.txt?dl=0
The actual dumb file is 0 bytes so I have not uploaded that onto dropbox.
-
Well, first off you have BMS installed in G:\Falcon4\BMS\Falcon BMS 4.33 U1.
It’s contained in two folders. Why aren’t you running it in it’s own folder as G:\Falcon BMS 4.33 U1??
Given the fact your running on XP, I’d do everything possible to help it run correctly, since there’s no longer support for XP.
Have you looked again in your User\Config folder to make sure you have the dx9display.dsp file?? And have you tried deleting it again?
Crashlog is incomplete?
C9
-
@Cloud:
Well, first off you have BMS installed in G:\Falcon4\BMS\Falcon BMS 4.33 U1.
It’s contained in two folders. Why aren’t you running it in it’s own folder as G:\Falcon BMS 4.33 U1??
Because I like to keep everything neatly organised
My Falcon 4.0 directory contains my original F4 installation, the BMS setup directory and the actual deployment directory.But I will reinstall BMS directly into a root sub directory and see if that helps.
Given the fact your running on XP, I’d do everything possible to help it run correctly, since there’s no longer support for XP.
I certainly appreciate the assistance and I’m planning to move off XP as soon as I get my Hempstick conversion done. (However tangling with electronics isn’t working for me by the time I get home from work very late in the evening….)
That’s also why I reverted back to 4.33.1 as that still had XP support. It was dropped with 4.33.3, which doesn’t run at all under XP. I tried 4.33.2 but I ran into some issues there as well. Other than this particular campaign crash, 4.33.1 has been the most stable under XP so I went with that.Have you looked again in your User\Config folder to make sure you have the dx9display.dsp file?? And have you tried deleting it again?
Yes it’s there but I can try deleting it again and have it re-generate. In terms of my configuration, I am running this with high-res tiles, but with the rain options mostly off, water reflections are off as well and I have changed the MFD configuration line to disable the double resolution for HUD and MFDs in order to keep FPS up. With this setup, I typically get around 52-55 FPS, with dips as low as the 35 FPS when doing a lot of TGP work.
Crashlog is incomplete?
Yes I noticed and also the actual dump file is empty so I think BMS must have completely terminated before it was able to complete all these tasks. That’s literally all I got after the crash. Which was extremely sudden and unexpected.
My system itself is very stable with all other 3D games, but all of those run under Windows 7 x64. So I’m definitely not ruling out a conflict between XP, my hardware and XP driver availability, although my hardware is old enough to have actually still been supported under Windows XP. With the exception maybe of the GTX 760, which wasn’t introduced until 2013, which which time Windows 7 was very mainstream. Although Nvidia still released XP drivers for it. I tried both the oldest and newest XP drivers I could download.
-
I have changed the MFD configuration line to disable the double resolution for HUD and MFDs in order to keep FPS up.
Hmm, thats interesting because the crash was initiated with: “Exception handler called in CRT Memory Depletion”
But who know as it’s incomplete.
The reason I asked about you having your install inside two other folders, which is with your Falcon 4 install, is due to the fact that back in time, when XP was the OS of the day, there were numerous issues with having Falcon installed that way, i.e., not directly on the drive in it’s own folder(some could get away with it, come couldn’t). Also, having any space in the address was an issue.
So at the moment it’s sort of a crap shoot to figure out your specific issue.
Also the running of the HiRes tiles.
Personally I would set everything back to normal, no HiRes tiles, turn all Shaders off, go back to the double reso HUD/MFD, delete the dx9display.dsp file.
Then work your way back up, turning/adding one thing back at a time to see if you can isolate the issue. But then again that’s me.
Its worth a shot and not really much work, except the part where you have to get BMS running to see if it’s gonna CTD on you.
C9
-
Yup. I will do a clean 4.33.1 install, directly under the root of G:\ and leave all options as default and try again. Hopefully I will be able to do so tonight.
-
Sounds like a solid plan. If ya can get this figured out, that would be great. Then you could at least get some flying in until you get your FLCS and TQS converted.
Good Luck, Lemme know how it progresses.
Cheers,
C9
-
Hmmmm no good news. I did a fresh install, into G:\Falcon BMS 4.33 U1 … I turned all the shaders off, no hires tiles, left the MFD resolution as default. I created a new logbook and new pilot. Set all the graphics options and controller options.
I started a Tiger Spirit campaign. It CTD’d on my way up north. I tried again and was able to fly (but I ran into a group of Chinese SU-30s, I got two before they got me). I started a new Iron Fortress campaign and also had a CTD before getting to the FLOT.
Both cases with the same error:
================================== CRASHLOG ===================================== Falcon BMS.exe caused an EXCEPTION_BREAKPOINT in: 001B:7C812FD3 <unknown>Exception handler called in CRT Memory Depletion. BreakpointBytes at CS:EIP: 7C 5E C9 C2 10 00 85 FF 0F 8E 5E 8E FF FF 8B 55</unknown>
and:
================================== CRASHLOG ===================================== Falcon BMS.exe caused an EXCEPTION_BREAKPOINT in: 001B:7C812FD3 <unknown>Exception handler called in CRT Memory Depletion. BreakpointBytes at CS:EIP: 7C 5E C9 C2 10 00 85 FF 0F 8E 5E 8E FF FF 8B 55</unknown>
In both cases the crash log is incomplete and there isn’t a dump file either…… ah sigh, oh well.
-
your running out of memory Tazz
scrolling though the crash log you see```
85 MB user address space freemakes sense as your on 32 bit win XP upgrade and slap some more memory in as 32 bit only sees upto 4GB not worth upgrading that until you upgrade your O/system
-
your running out of memory Tazz
scrolling though the crash log you see```
85 MB user address space freemakes sense as your on 32 bit win XP upgrade and slap some more memory in as 32 bit only sees upto 4GB not worth upgrading that until you upgrade your O/system
I know that any 32-bit OS can only address up to 3.5 GB of memory (not even 4 GB). I’m running 8 GB on Win7 x64 but I was using an additional XP installation for my FLCS and TQS which I am planning to convert to USB but I haven’t had the time yet.
What strikes me as odd though, is that even with 3.5 GB of available RAM and 32-bit XP SP3, my config is matching the minimum system requirements for BMS 4.33.1 as outlined here:
https://www.benchmarksims.org/forum/content.php?132
XP SP3? Check. Minimum of 2 GB of RAM? Check. 1 GB video card? Check.
I’m not going to argue against the fact that running this under Windows 7 64-bit is going to make more sense and that’s certainly the plan, I completely agree with that. But either these published minimum requirements are incorrect (we’re talking 4.33.1 here, not 4.33.3) or there is something else at play. I’ll take a close look at the memory consumption - maybe something else is ballooning up (my ESET NOD32 antivrius perhaps?) and starving BMS for memory? If in testing it was shown that BMS 4.33.1 can run on as little as 2 GB of RAM (and that’s me assuming that each configuration is actually tested before specs are being published), then I’m puzzled as to why it’s giving me grief with 1.5 GB of more RAM?
Note that I’ve had the very same behaviour with 4.33.2 (which should still be XP supported, XP support wasn’t dropped until 4.33.3), even when creating a TE. (with ~ 10 squadrons and ~ 20 sorties happening).
-
Kill everything else not needed for Falcon, services and processes. Since u use it and for other things game booster might be handy.
sent from my mi5 using Tapatalk
-
minimum requirements are correct and been tested from what I can recall ( been a long time )
something chewing up your memory here AV, FW, external apps running in the background etc. etc.
as arty said kill everything