[solved] 4.33 "Has stopped working" before accessing 3D world
-
Same thing here. Instant ctd when trying to enter the 3d world. I’m running win7 64bit.
Problem signature:
Problem Event Name: APPCRASH
Application Name: Falcon BMS.exe
Application Version: 4.14753.0.0
Application Timestamp: 562b288d
Fault Module Name: KERNELBASE.dll
Fault Module Version: 6.1.7601.19018
Fault Module Timestamp: 560a0094
Exception Code: 80000003
Exception Offset: 000000000000b3dd
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 2715
Additional Information 2: 2715fc7b53c3b3daad88d3de968e54b1
Additional Information 3: 6f34
Additional Information 4: 6f346f410e1b721f23dec548a7c08127I have exactly the same issue only when im trying to play in windowed mode. In fullscreen it runs fine. I have win10 x64 and amd r9 290x video card.
-
… Tests …
Thanks for trying all those things.
Looking more at where this all gets caused, it looks to me as if the problem lies in OTWDriverClass::DoOncePerRenderFrame().
Somewhere there, something wants to put something into something (sprintf_s).
More specific, I guess, or the Format, or the data that should feed the function to fill the buffer, contains something perhaps longer (but this would result in a buffer Overflow), or different Format, or wrong data.did you try to disable all Video Settings (In the Configuration before launching falcon, and ingame in the Video Settings)?
Another idea might be an older/newer videodriver. Do you have an exotic Hardware? -
Is your callsign longer than 12 characters?
See if reducing the length below 12 characters fixes the issue. Then we can address it for the next update. -
Thanks for trying all those things.
did you try to disable all Video Settings (In the Configuration before launching falcon, and ingame in the Video Settings)?
Another idea might be an older/newer videodriver. Do you have an exotic Hardware?I disabled every option under the Hardware tab of the configuration and then unticked everything in the advanced tab. Same error with the same stack trace etc.
My system is pretty standard I think. Here is the full output of DxDiag which is probably the most comprehensive I can give: https://gist.github.com/anonymous/487f12a82b803278bb0b
-
Is your callsign longer than 12 characters?
See if reducing the length below 12 characters fixes the issue. Then we can address it for the next update.You Genius!
Shortened RurouniJones -> Jones and mission starts
Confirmed fixed
-
Is your callsign longer than 12 characters?
See if reducing the length below 12 characters fixes the issue. Then we can address it for the next update.Thanks, that did the trick.
-
I’m having this issue…anny tips :
This is BMS running Full Screen, clean install…
These logs were created :
dtc_last_flight_faults
[ 0:00] [ 0:00] [SET] [17] [ENG ] [-1]
[ 0:00] [ 0:00] [SET] [29] [FAULT OIL PRESS ] [-1]
[ 0:00] [ 0:00] [SET] [32] [FAULT HYD A FAULT ] [-1]
[ 0:00] [ 0:00] [SET] [33] [FAULT HYD B FAULT ] [-1]
[ 0:00] [ 0:00] [SET] [24] [FAULT SEC ] [-1]
[ 0:00] [ 0:00] [SET] [39] [FAULT SEAT NOT ARMED ] [-1]
[ 0:08] [ 0:08] [SET] [35] [FAULT CANOPY ] [-1]ErrorsInClassTable
This file is restarted each session
PtHeaderDataTable[0].features[0]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[1]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[2]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[3]=0 >= Objective[0]'s Features 0
PtHeaderDataTable[0].features[4]=0 >= Objective[0]'s Features 0ErrorsInSFX
LoadSFX() didn’t load 264:C:\Falcon BMS 4.33\Data\Sounds\engines/fighter/a-10/Ext.ogg
LoadSFX() didn’t load 277:C:\Falcon BMS 4.33\Data\Sounds\sndAero1.ogg
LoadSFX() didn’t load 330:C:\Falcon BMS 4.33\Data\Sounds\engines\fighter\SndAbInt2.ogg
LoadSFX() didn’t load C:\Falcon BMS 4.33\Data\Sounds\F-18\flare.ogg -
Linda, no problems there. The Errors are to be expected with this version and the faults are by design.
From the TO-BMS1F-16CM-1 page 80:
All MFLs are recorded in the dtc_last_flight_faults.txt file (\User\Logs) at the end of each flight. It is overwritten with each new flight.
As to what is causing the issue in the video I have no idea. I’m sure someone else will though.
-
I’m not running a super computer though…
Intel Core 2 Q8300 Quadcore on a P5B Deluxe Mainboard, 8 GBytes DDR2 RAM, Ati Radeon HD 4870 X2.
Though ARMA 3 runs nicely? -
Is your callsign longer than 12 characters?
See if reducing the length below 12 characters fixes the issue. Then we can address it for the next update.THANK YOU! That was almost too easy haha