4.33u3 CTD on start
-
Try windowed mode.
sent from my mi5 using Tapatalk
-
Try windowed mode.
sent from my mi5 using Tapatalk
I’ve tried adding the –window –nomovie parameters to the launcher, which correctly reflects them in the launcher window. The black/white splash screen now launches in window mode but then I still get the same error.
Also, when I start BMS 4.33U1 or 4.33U2, the game goes very quickly from splash screen into the actual UI / game menu. But BMS 4.33U3 shows the splash screen for much longer and there is a lot of hard disk activity, which I assume is the creation of the 120MB dump file?
-
If you have your display scaling set on your graphics card through it’s software driver… turn it off. that solved my issues.
-
If you have your display scaling set on your graphics card through it’s software driver… turn it off. that solved my issues.
Thanks for the tip! But I had a look in the Nvidia control panel for my GTX 760 but I cannot find any such option?
But looking at the crash logs, it really does seem to be a display related problem. But I’m not running any exotic video setup nor have I overclocked my videocard or anything else that could cause issues.
BMS 4.33u2 (which I am running right now) works perfectly fine. Very strange. -
Use the first driver version for your vga and not the last one.
If it works work your way up version bt version.sent from my mi5 using Tapatalk
-
I’ll download the oldest driver I can find on the Nvidia website and try again.
Interestingly, I also installed BMS 4.33 on my Windows 7 x64 Home Premium installation, which is my main OS. There BMS 4.33u3 works just fine - both in 32-bit and 64-bit. So it’s definitely a software issue of sorts.
-
OK… I removed the previously installed Nvidia 368.81 drivers, rebooted the PC and all that and installed the 353.62 drivers. These are the oldest drivers for the GTX 760 that I can download from the Nvidia website.
I made sure to ONLY install the display driver and not to install the HDMI Audio driver and PhysX driver.Still get the same result after applying the U3 update … I put my BMS 4.33 U2 game and setup directories back (I had made copies before) and U2 just fires up without a problem.
-
Why are you installing stuff one-by-one? I know you’ve done this before to test it, but have you tried installing DIRECTLY to U3? Something may be going wrong on your U2-to-U3 transition…
-
Why are you installing stuff one-by-one? I know you’ve done this before to test it, but have you tried installing DIRECTLY to U3? Something may be going wrong on your U2-to-U3 transition…
Yes, I’ve tried that as well - patching the U1 setup directory all the way to U3 and then install it. It has the exact same effect. In fact, that’s how I originally installed BMS 4.33 as I wanted to go straight to the latest version. That didn’t work.
It wasn’t until I started installing it one by one, I noticed that U1 and U2 ran fine but U3 didn’t. -
running Windows XP SP3 32bit
Winxp support was dropped in U3 due to various reasons but then even M$ don’t support XP anymore either it is advisable to update your O/sys anyway
-
System requirements page has been updated to reflect that XP support was dropped with U3. Yes you are looking for trouble if you don’t upgrade. Support ended 3 years ago and the last Service Pack was 9 years ago!
-
That explains why U2 works fine but U3 doesn’t. My U3 install runs fine under Windows 7 though.
I am running Windows 7 (I will upgrade to Windows 10 only over my dead body or when I get a Kaby Lake system. Considering my mortgage, that’s not likely to happen soon) but until I have converted my FLCS and TQS to USB, I’m rocking a XP install on the side so I can at least use my HOTAS. However, I have just received my second/donor set of another FLCS and TQS (from one former Stray Dog to another) and I’ll start ordering the conversion parts. (2x Arduino Micro, PCBs, etc.)
Of course, if someone is willing to donate a Cougar, I’m absolutely not against charity
I’ll just use my XP-bound U2 install to get back in the groove again for now. Because I don’t think “rusty” applies to a 10 year absence any more
-
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