Have to unplug DirectX devices to get BMS to run? feedback requested

Darkman

We’ve seen a few posts now from people with multiple DirectX controllers which were working for them in 4.32 who have found they have to remove some of them in 4.33 to avoid CTDs. Now in some cases they are running with very old hardware, no longer supported by modern operating systems, but that still doesn’t answer the question of why it works in 4.32 but not in 4.33. In some reports they even work in 32-bit 4.33 but not 64-bit 4.33. A couple of examples below:

https://www.benchmarksims.org/forum/showth…l=1#post339866
https://www.benchmarksims.org/forum/showthread.php?23354-BMS-4-33-x64-Crash-on-launch&p=342771&viewfull=1#post342771
Has anything changed which could potentially account for this behaviour? The short answer is no and further testing by the developers with more devices than anyone has yet reported using has not resulted in any issues, so those of you suffering from these problems we need your help to try to understand what may be going on here.

Please could you add -mono as a command line argument to your Launcher shortcut as in the first screenshot below. If done correctly you will see -mono in the top left of the Launcher menu as shown in the second screenshot.

Enabling this debug print should result in a text file in the \user\logs directory of your Falcon4 BMS install. The files are created each time you run the game with logging enabled and the filenames are of the form: YYYY-MM-DD_hhmmss_xlog.txt where the YYYY is the system year, MM is the month, DD is the day and hhmmss is the time in hours minutes seconds for the time at which you launched the game for this logged session.

Don’t worry about the information contained therein; the coders understand this stuff

If you can post with a download link to any logs,crashlogs and dumps you get, with a list of devices you have plugged in and your system specification we can get the coders to dive into this information and see what is happening on your PC.

Darkman

Some additional background information on DirectX which may be of interest to those with multiple devices plugged in:

Note 1: As you know, BMS supports up to 16 DX devices (easy math: 512 buttons max, 32 buttons for each device = 16 devices). So no problem here?

Well: we have the possibility to use DX shifting. What happens by default is that there is a shifting offset defined in the config (256), which means as soon as you hit the DX shift button (whatever that is), your device suddenly gets “promoted” 256 buttons up in the range. Hence: shifting actually makes a DX device occupy 2 device slots at the same time:

Device 1 uses device 1 buttons (0-31) for unshifted, and device 9 buttons (256-287) for DX shifting.
Device 2 is device 2 and device 10 … device 8 is device 8 and device 16.

Device 9 is device 9 and device 17… oops!!! 1st, device 9 is already in use (virtually) by device 1 shifting - which is no real issue other that you will probably not get the input you think you’ll get - and 2nd, trying to access device 17 will obviously fail badly. Does this make sense?

In short: if you use more than 8 devices, you probably need to make sure NOT to use DX shifting at all.

Note 2: don’t assume by just adding up the buttons you have programmed and finding that the overall number is below 512 that you can’t run into issues. It’s important to understand that each device ALWAYS uses 32 buttons, regardless whether it actually has that much physical buttons or not. So in the case in the link above with 13 devices he is using 1 stick, 1 throttle, 2 MFDs, 9 boards = 13 devices = 13 x 32 = 416 buttons (assuming that the EHSI and indexers are not DX input devices… if they are, they need to be added as well, i.e. an additional 64 buttons).

andre_a330

Hello Darkman

Here is my log:

================================== CRASHLOG =====================================
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
00000000047F1A51 Falcon BMS.exe, CheckForForceFeedback()+49 byte(s), d:\wip\bms\svn\source\releases-4.33\sim\siminput\sijoy.cpp, line 1111+12 byte(s)
Exception handler called in UnhandledExceptionHandler.
Read from location 00000000a7527ce0 caused an access violation.
Bytes at CS:RIP: 48 8B 0C D9 48 8B 01 FF 50 18 8B 0D BF 27 43 00 

Registers:
RAX=0xffffffffffffffff  RBX=0x00000000144d1bd0  RCX=0x0000000004e99e60  RDX=0x000000000012e370
RSI=0x0000000013ca9078  RDI=0x000000000012e55c  RBP=0x000000000012eb90  RSP=0x000000000012e350
RIP=0x00000000047f1a51  FLG=0x0000000000010297  
 R8=0x000000000012e583   R9=0x00000000143a3674  R10=0x0000000000000010  R11=0x0000000000000001
R12=0x0000000000000000  R13=0x0000000000000000  R14=0x0000000004470000  R15=0x0000000004e99e50
CS=0x0033  DS=0x002B  SS=0x002B  ES=0x002B  FS=0x0053  GS=0x002B

Call Stack:
0033:00000000047F1A51 Falcon BMS.exe, CheckForForceFeedback()+49 byte(s), d:\wip\bms\svn\source\releases-4.33\sim\siminput\sijoy.cpp, line 1111+12 byte(s), Parameters(0x0000000000000001 0x000000000012EB90 0x0000000013CA9078 0x000000000012E55C)
0033:00000000047F1C7D Falcon BMS.exe, InitJoystick()+381 byte(s), d:\wip\bms\svn\source\releases-4.33\sim\siminput\sijoy.cpp, line 1274, Parameters(0x0000000022344830 0x0000000013CA9078 0x0000000000000000 0x000000000012EB90)
0033:00000000F84F264A DINPUT8.dll, DllCanUnloadNow()+1390 byte(s), Parameters(0x00000000144D0350 0x0000000013CA9078 0x0000000013CA9078 0x0000000076F9AD51)
0033:00000000F84F23EB DINPUT8.dll, DllCanUnloadNow()+783 byte(s), Parameters(0x0000000013CA9080 0x00000000FFFFFFFF 0x0000000000000000 0x0000000000000000)
0033:00000000F84F26D0 DINPUT8.dll, DllCanUnloadNow()+1524 byte(s), Parameters(0x0000000000000002 0x0000000000000004 0x0000000000000000 0x0000000000000000)
0033:00000000047F3290 Falcon BMS.exe, SetupDIJoystick()+208 byte(s), d:\wip\bms\svn\source\releases-4.33\sim\siminput\siloop.cpp, line 511, Parameters(0x0000000000000000 0x000000000006053E 0x0000000000000000 0x0000000000000170)
0033:0000000004476B01 Falcon BMS.exe, SystemLevelInit()+961 byte(s), d:\wip\bms\svn\source\releases-4.33\ui\src\winmain.cpp, line 1944, Parameters(0x000000000E567BE0 0x0000000000000170 0x0000000000282F31 0x0000000004470000)
0033:0000000004475C2D Falcon BMS.exe, HandleWinMain()+717 byte(s), d:\wip\bms\svn\source\releases-4.33\ui\src\winmain.cpp, line 947, Parameters(0x0000000002609A30 0x0000000000000005 0x0000000000282F31 0x0000000000000002)
0033:0000000004475DB0 Falcon BMS.exe, WinMainWrapper()+48 byte(s), d:\wip\bms\svn\source\releases-4.33\ui\src\winmain.cpp, line 1016, Parameters(0x0000000002609A30 0x0000000002609A30 0x0000000000282F31 0x0000000004475D80)
0033:00000000044B526D Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), d:\wip\bms\svn\source\releases-4.33\falclib\ehandler.cpp, line 1567+5 byte(s), Parameters(0x0000000004470000 0x0000000000000000 0x0000000000000005 0x0000000000000000)
0033:0000000004475E27 Falcon BMS.exe, WinMain()+71 byte(s), d:\wip\bms\svn\source\releases-4.33\ui\src\winmain.cpp, line 1042, Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000005 0x0000000000000005)
0033:0000000004A9CDB4 Falcon BMS.exe, __tmainCRTStartup()+328 byte(s), f:\dd\vctools\crt\crtw32\startup\crt0.c, line 251+17 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:0000000076E65A4D kernel32.dll, BaseThreadInitThunk()+13 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:0000000076F9B831 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)

Top of Stack:
0x000000000012E350: 000000000012E55C 0000000004A99AAB 0000000000000027 0000000000000027 \...............'.......'.......
0x000000000012E370: 000000000000002C 0000000100000000 0000000000350001 0000000000000000 ,.................5.............
0x000000000012E390: 0000000004E99E50 0000000000000000 00000000144D1BD1 00000000047F1C7D P.................M.....}.......
0x000000000012E3B0: 0000000000000001 000000000012EB90 0000000013CA9078 000000000012E55C ................x.......\.......
0x000000000012E3D0: 0000000D0000002C 0000000300010114 0000000000000000 0000000000000000 ,...............................
0x000000000012E3F0: 0000000000000000 0000000000000000 000007FEF84F260C 000007FEF84F264A .................&O.....J&O.....
0x000000000012E410: 0000000022344830 0000000013CA9078 0000000000000000 000000000012EB90 0H4"....x.......................
0x000000000012E430: 7E4900D000000244 4544028011E2A12D 076406A300005453 4950000000000000 D.....I~-.....DEST....d.......PI
0x000000000012E450: 0001011444495644 50206B6574696153 6867696C46206F72 7461626D6F432074 DVID....Saitek Pro Flight Combat
0x000000000012E470: 2072656464755220 0000736C61646550 000000000012E510 000000000012E494  Rudder Pedals..................
0x000000000012E490: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E4B0: 00000000000E000C 000007FEF8507348 0000000004E99E50 0000000000006E30 ........HsP.....P.......0n......
0x000000000012E4D0: 000007FEF8507348 000000000012E5E0 0000000016975FE8 0000000000000004 HsP.............._..............
0x000000000012E4F0: 0000000000000001 000007FEFF06F06D 0000000000006E30 0000000004E99E50 ........m.......0n......P.......
0x000000000012E510: 0000000000000004 0000000000000000 000000000012E5E0 000000000012E5C0 ................................
0x000000000012E530: 000000000012E5B0 000007FEF84FED92 0000000000000000 000007FEF84FC349 ..........O.............I.O.....
0x000000000012E550: 0000000000006E0C 7469615316975FE8 46206F7250206B65 6F4320746867696C .n......._..Saitek Pro Flight Co
0x000000000012E570: 647552207461626D 6164655020726564 000000000000736C 0000000000000000 mbat Rudder Pedals..............
0x000000000012E590: 0000000000000000 000007FEF84F7F05 000000000012E640 000000000012EB90 ..........O.....@...............
0x000000000012E5B0: 0000000000000000 0000000016975FE8 0000000100000004 0000000300010114 ........._......................
0x000000000012E5D0: 000000000012E640 000007FEF84E8DAE 0000000022344628 0000000022344628 @.........N.....(F4"....(F4"....
0x000000000012E5F0: 0000000013CA9078 000007FEF84E460A 0000000022344628 000007FEF84E4F9C x........FN.....(F4".....ON.....
0x000000000012E610: 00001BC8B615A4A1 000007FEF84F22C7 0000000000000000 0000000022344628 ........."O.............(F4"....
0x000000000012E630: 0000000022344628 000007FEF84E9508 0000000000000000 0000000300010114 (F4"......N.....................
0x000000000012E650: 0000000000000000 000000000012EB90 0000000000000000 0000000000000000 ................................
0x000000000012E670: 0000000000040001 000000000012E6E0 00001BC8B615A3D1 0000000000000000 ................................
0x000000000012E690: 00000000144D0350 000007FEF84F23EB 00000000144D0350 0000000013CA9078 P.M......#O.....P.M.....x.......
0x000000000012E6B0: 0000000013CA9078 0000000076F9AD51 000000000012E6D0 0000000004B37210 x.......Q..v.............r......
0x000000000012E6D0: 00000000144D0350 0000000000000000 7E4900D00000044C 4544028011E2A12D P.M.............L.....I~-.....DE
0x000000000012E6F0: 076406A300005453 4950000000000000 0001011444495644 0074006900610053 ST....d.......PIDVID....S.a.i.t.
0x000000000012E710: 00500020006B0065 00460020006F0072 006800670069006C 006F004300200074 e.k. .P.r.o. .F.l.i.g.h.t. .C.o.
0x000000000012E730: 007400610062006D 0064007500520020 0020007200650064 0061006400650050 m.b.a.t. .R.u.d.d.e.r. .P.e.d.a.
0x000000000012E750: 000000000073006C 0000000000000000 0000000000000000 0000000000000000 l.s.............................
0x000000000012E770: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E790: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E7B0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E7D0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E7F0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E810: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E830: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E850: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E870: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E890: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E8B0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E8D0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E8F0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E910: 0074006900610053 00500020006B0065 00460020006F0072 006800670069006C S.a.i.t.e.k. .P.r.o. .F.l.i.g.h.
0x000000000012E930: 006F004300200074 007400610062006D 0064007500520020 0020007200650064 t. .C.o.m.b.a.t. .R.u.d.d.e.r. .
0x000000000012E950: 0061006400650050 000000000073006C 0000000000000000 0000000000000000 P.e.d.a.l.s.....................
0x000000000012E970: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E990: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E9B0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E9D0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012E9F0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EA10: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EA30: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EA50: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EA70: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EA90: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EAB0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EAD0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EAF0: 0000000000000000 0000000000000000 0000000000000000 0000000000000000 ................................
0x000000000012EB10: 0000000000000000 0000000000000000 0000000000000000 000007FE00040001 ................................
0x000000000012EB30: 00001BC8B615A161 FFFFFFFFFFFFFFFF 000000000012F338 0000000000000004 a...............8...............

================================================================================
Object at RCX(0000000004E99E60)
Data inaccessible

================================================================================

Compiler Options:
_MSC_VER=1800  WINVER=0x502  _WIN32_WINNT=0x502  _WIN32_WINDOWS=0x502  
NTDDI_VERSION=0x5020000  _WIN32_IE=0x602  ANSI  _M_AMD64  _AMD64_  _WIN64  Release*  

System Information:
'C:\Falcon BMS 4.33\Bin\x64\Falcon BMS.exe', run by André.
Error occurred at 13:00:50 on 2015-11-10.
Version: Falcon BMS 4.33.0 (x64) 14753
Not in game
Theater terrain path: 'C:\Falcon BMS 4.33\Data\Terrdata\korea'
Operating System: Windows 7 (6.1.7600) Platform 2 .
Computer Name: ANDRÉ-PC   Domain: WORKGROUP.
8 logical processor(s), type 8664.
CPU:        Intel(R) Core(TM) i7-2600K CPU @ 3.40GHz. GenuineIntel. Stepping: 7  Model: A  Family: 6.
GPU 0: AMD Radeon R9 200 Series. Vendor: 4098\. Device: 26640\. SubSys: 2457147010\. Revision: 0.
GPU 1: AMD Radeon R9 200 Series. Vendor: 4098\. Device: 26640\. SubSys: 2457147010\. Revision: 0.
GPU 2: AMD Radeon R9 200 Series. Vendor: 4098\. Device: 26640\. SubSys: 2457147010\. Revision: 0.
17% memory in use:
     16384 MB physical memory
     13503 MB physical memory free
     32767 MB paging file
     29690 MB paging file free
   8388608 MB user address space
   8387851 MB user address space free

Module List:
C:\Falcon BMS 4.33\Bin\x64\Falcon BMS.exe, loaded at 0x0000000004470000 - 9171968 bytes - TimeDateStamp 0x        562b288d - File date is 04:43:28 on 2015-10-24
C:\Falcon BMS 4.33\Bin\x64\dbghelp.dll, loaded at 0x0000000065b00000 - 1558912 bytes - TimeDateStamp 0x        4b673670 - File date is 08:33:04 on 2010-03-03
C:\Windows\system32\atiumd6a.dll, loaded at 0x0000000067240000 - 8927704 bytes - TimeDateStamp 0x        52a23780 - File date is 19:57:20 on 2013-12-06
C:\Windows\system32\sfc.dll, loaded at 0x0000000071450000 - 3072 bytes - TimeDateStamp 0x        4a5be057 - File date is 23:33:08 on 2009-07-13
C:\Windows\system32\USER32.dll, loaded at 0x0000000076d50000 - 1008128 bytes - TimeDateStamp 0x        4ce7c9f1 - File date is 11:27:28 on 2010-11-20
C:\Windows\system32\kernel32.dll, loaded at 0x0000000076e50000 - 1164800 bytes - TimeDateStamp 0x        560a0093 - File date is 01:10:54 on 2015-09-29
C:\Windows\SYSTEM32\ntdll.dll, loaded at 0x0000000076f70000 - 1730496 bytes - TimeDateStamp 0x        560a0083 - File date is 01:13:52 on 2015-09-29
C:\Windows\system32\PSAPI.DLL, loaded at 0x0000000077130000 - 9216 bytes - TimeDateStamp 0x        4a5bc29d - File date is 23:41:54 on 2009-07-13

Environment Variables:
    1:  <allusersprofile=c:\programdata>2:  <appdata=c:\users\andr‚\appdata\roaming>3:  <commonprogramfiles=c:\program files\common="" files="">4:  <commonprogramfiles(x86)=c:\program files="" (x86)\common="">5:  <commonprogramw6432=c:\program files\common="" files="">6:  <computername=andr-pc>7:  <comspec=c:\windows\system32\cmd.exe>8:  <fp_no_host_check=no>9:  <homedrive=c:>10:  <homepath=\users\andr‚>11:  <localappdata=c:\users\andr‚\appdata\local>12:  <logonserver=\\andr-pc>13:  <number_of_processors=8>14:  <os=windows_nt>15:  <path=c:\program files="" (x86)\nvidia="" corporation\physx\common;c:\windows\system32;c:\windows;c:\windows\system32\wbem;c:\windows\system32\windowspowershell\v1.0\;c:\program="" (x86)\ati="" technologies\ati.ace\core-static="">16:  <pathext=.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc>17:  <processor_architecture=amd64>18:  <processor_identifier=intel64 6="" 42="" family="" model="" stepping="" 7,="" genuineintel="">19:  <processor_level=6>20:  <processor_revision=2a07>21:  <programdata=c:\programdata>22:  <programfiles=c:\program files="">23:  <programfiles(x86)=c:\program files="" (x86)="">24:  <programw6432=c:\program files="">25:  <psmodulepath=c:\windows\system32\windowspowershell\v1.0\modules\>26:  <public=c:\users\public>27:  <systemdrive=c:>28:  <systemroot=c:\windows>29:  <temp=c:\users\andr~1\appdata\local\temp>30:  <tmp=c:\users\andr~1\appdata\local\temp>31:  <userdomain=andr‚-pc>32:  <username=andr‚>33:  <userprofile=c:\users\andr‚>34:  <windir=c:\windows>35:  <__COMPAT_LAYER=RunAsAdmin Win7RTM>

================================================================================</windir=c:\windows></userprofile=c:\users\andr‚></username=andr‚></userdomain=andr‚-pc></tmp=c:\users\andr~1\appdata\local\temp></temp=c:\users\andr~1\appdata\local\temp></systemroot=c:\windows></systemdrive=c:></public=c:\users\public></psmodulepath=c:\windows\system32\windowspowershell\v1.0\modules\></programw6432=c:\program></programfiles(x86)=c:\program></programfiles=c:\program></programdata=c:\programdata></processor_revision=2a07></processor_level=6></processor_identifier=intel64></processor_architecture=amd64></pathext=.com;.exe;.bat;.cmd;.vbs;.vbe;.js;.jse;.wsf;.wsh;.msc></path=c:\program></os=windows_nt></number_of_processors=8></logonserver=\\andr-pc></localappdata=c:\users\andr‚\appdata\local></homepath=\users\andr‚></homedrive=c:></fp_no_host_check=no></comspec=c:\windows\system32\cmd.exe></computername=andr-pc></commonprogramw6432=c:\program></commonprogramfiles(x86)=c:\program></commonprogramfiles=c:\program></appdata=c:\users\andr‚\appdata\roaming></allusersprofile=c:\programdata>

My System:
Windows 7 Home Premium 64 bits
Intel Core I7-2600K CPU@ 3.40GHZ (8CPUs),3.7GHz
32768MB RAM
Directx 11
AMD Radeon R9 200 Series 4095 MB

Full Pit: 1 Hotas Warthog Stick 1 Hotas Cougar Trottle (Tusba), 2 MFD´s, 1 Saitek Rudder Combat Pedals, 1 EHSI and 2 Indexers (By Martin Pegasus), 3 AIC Boards (By Arend White Eagle), 3 Monitors, and 9 PCB Boards (each capable to handle 24 inputs).

I think we already found the issue but a lot of people is looking for solution. Today the same thing: I disconected 3 of my 9 PCB Boards and worked very fine. When i connect all the 9 PCB´s the game doesn´t lunch (even in 32 or 64 bit)

Thanks again for the time guys. I don´t want to suck waste your time fellows, but is very frustrating to have such a fine equipment that worked in previous version and in the awaited amazing new version, nothing zip!
But the solution will come for sure

Best Regards

Darkman

That’s a start but coders will need to see the dump (same name but ends in _crash.dmp) as well, which is why I asked for a download link, as the file is large (zip it first before uploading it and providing a link please).

@Darkman:

If you can post with a download link to any logs,crashlogs and dumps you get, with a list of devices you have plugged in and your system specification we can get the coders to dive into this information and see what is happening on your PC.

Thank you.

andre_a330

Here is the DMP File (Drop box):

https://www.dropbox.com/s/6p7rprnku8c3l0f/2015-11-10_133718_crash.rar?dl=0

Thank You

Darkman

andre_a330 that was exactly what was needed. Thank you.

This is indeed a bug in BMS, having too many analogue axis devices will make BMS crash.
We will try to get this fixed as soon as possible, hopefully for the next update.

Background info: if DX devices have only buttons, the limit is no problem. But if DX devices have analogue axis and you add more than BMS supports, we get an array overflow, leading to the CTD seen here. Currently 12 devices with analogue axis is OK. If you have more, BMS will crash.

andre_a330

Gotcha! I have a complete set of analogue axes on those 3 pcb boards that are making me crazy (Comm 1 and 2, Trims, HUD brightness Threat, msl volume and Intercom.Everytime i disconect those boards, problem solved.
Thank you very much

Moose

@Darkman:

andre_a330 that was exactly what was needed. Thank you.

This is indeed a bug in BMS, having too many analogue axis devices will make BMS crash.
We will try to get this fixed as soon as possible, hopefully for the next update.

Background info: if DX devices have only buttons, the limit is no problem. But if DX devices have analogue axis and you add more than BMS supports, we get an array overflow, leading to the CTD seen here. Currently 12 devices with analogue axis is OK. If you have more, BMS will crash.

Darkman, that’s verified on my setup as well. 4.33 starts up fine if I remove my rudder pedals and volume controls (Bodnar BUO836 analog connections)

Darkman

Understood. Our resident DX meister is confident it’ll be sorted in the next update, so just work within the 12 analogue axis limit until then.

Arty

I’ll get my wheel pedals back? Yeeeeaaaaaaa….

Arty

Is it ready yet? :rofl:

black-viper

Same problem here, too. Thanks for this thread- now I know why my Falcon 4.33 was running in the beginning, but stopped working. I added two more DX Devices! When I disconnect them, Falcon 4.33 works again! No problem for Falcon 4.32 with ALL
devices connected….
Do you still need Log files, or are you OK with what you got???

Darkman

No need for further log files, thank you. Just wait for updated code in the next update, when you should be able to plug everything back in.

black-viper

Hi Darkman,
thanks a lot for your reply- 4.32 still is great, but what I can see from 4.33 on youtube seems to be absolutely incredible! So no problem to wait a bit longer. I will start trying with a little bit reduced setup (I´m using a USB Hub, where I easily can switch on and off some devices)
and wait till the problem is solved! Thanks again for your incredible work, makes (together with the DCS guys) all my “Cockpit dreams” come true

Grooz

Look for older librares for direct X 9.0 or 9.0 C http://https://www.benchmarksims.org/forum/showthread.php?25203-BMS-4-33-AND-WIN-8-PROBLEMS

black-viper

Hi Grooz,
sorry for the late reply, just saw your answer, yet. But the link is not working on my PC- and I´m using Win7. Really seems to be a matter of how many DX devices someone is running. When I reduce them, I think to nine or ten, (not quite sure how many exactely) Falcon runs great, if I add only one more,
it imediately stops working. Hope the next patch will solve this problem. Thanks a lot all of you for your help….

OverDhill

I added another joystick interface card and BMS stopped working. I hope they fix this

OverDhill

@Darkman:

No need for further log files, thank you. Just wait for updated code in the next update, when you should be able to plug everything back in.

Did this get fixed in the latest update?

Darkman

@OverDhill:

Did this get fixed in the latest update?

Yes. Did you not read the changelog?

https://www.benchmarksims.org/forum/showthread.php?26567-Falcon-BMS-4-33-U1-Full-Installer

Have to unplug DirectX devices to get BMS to run? feedback requested

HOT LIST

System Specs:

HOT LIST

System Specs:

69

9.3k

22.2k

362.6k