Brilliant.
Problem solved, I was missing the FreeTrack protocol which I needed to download.
airtex2019, really appreciate your help.
Thanks
JB
Brilliant.
Problem solved, I was missing the FreeTrack protocol which I needed to download.
airtex2019, really appreciate your help.
Thanks
JB
Hi,
I’m trying to get FaceTrackNoIR/Tobii EyeTracker 5 working with Falcon BMS. When I run FaceTrackNoIR I can see from the app that it is picking up my head and eye movements, but when I run Falcon BMS 4.37.2 I get no head movement whatsoever. I am in the 3D cockpit View (3).
Has anyone had a similar issue and know what I need to do to fix this. I’m pretty sure it’s something simple but at the moment this has me stumped.
Many thanks
Here’s a screenshot
Update: I reinstalled BMS, which seemed to fix the problem
I forgot to add, I have applied ‘Temporary fixes for 4.36.0’
I am experiencing game crashes at the same point in a mission - this has occurred to me three times now :
================================== CRASHLOG =====================================
Falcon BMS.exe caused an EXCEPTION_ACCESS_VIOLATION in:
0000000004741ECA Falcon BMS.exe, BombClass::Exec()+778 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\BOMB\Bombmain.cpp, line 445+26 byte(s)
Exception handler called in UnhandledExceptionHandler.
Read from location 0000000000000481 caused an access violation.
Bytes at CS:RIP: 0F B6 88 81 04 00 00 89 4D B8 8B 83 80 04 00 00
Registers:
RAX=0x0000000000000000 RBX=0x00000002e3a4d610 RCX=0x000000000e34b180 RDX=0x0000000000000000
RSI=0x00000002e3a4d610 RDI=0x000000002c309d10 RBP=0x000000003061f8f0 RSP=0x000000003061f7f0
RIP=0x0000000004741eca FLG=0x0000000000010246
R8=0x000000003061f7a0 R9=0x000000003061f790 R10=0x0000000000000007 R11=0x000000003061f730
R12=0x0000000000000000 R13=0x0000000004f51840 R14=0x0000000000000001 R15=0x000000000e290180
CS=0x0033 DS=0x002B SS=0x002B ES=0x002B FS=0x0053 GS=0x002B
Call Stack:
0033:0000000004741ECA Falcon BMS.exe, BombClass::Exec()+778 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\BOMB\Bombmain.cpp, line 445+26 byte(s), Parameters(0x0000000043F00000 0x0000000000000000 0x0000000000000000 0x000000003061F940)
0033:0000000004746932 Falcon BMS.exe, ChaffClass::Exec()+50 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\BOMB\ChaffMain.cpp, line 138, Parameters(0x000000008EFA8A60 0x000000003061FBF0 0x0000000000000000 0x0000000000000000)
0033:0000000004A18D39 Falcon BMS.exe, SimVuDriver::ExecModel()+41 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\SIMLIB\simvudrv.cpp, line 31, Parameters(0x0000000000000001 0x000000003061FBF0 0x0000000004854413 0x0000000000000000)
0033:0000000004B7C893 Falcon BMS.exe, VuMaster::Exec()+35 byte(s), E:\WIP\BMS\SVN\Code-4.36\vu2\src\vudriver.cpp, line 590, Parameters(0x0000000000000001 0x000000000E7CFC30 0x0000000000000001 0x000000000E7CFC30)
0033:00000000049CB874 Falcon BMS.exe, SimulationDriver::Cycle()+2660 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\SIMDRIVE\Simdrive.cpp, line 762, Parameters(0x0000000000000001 0x0000000000000003 0x000000001E860F00 0x0000000004F527A8)
0033:0000000004A1A84B Falcon BMS.exe, SimulationLoopControl::Loop()+2459 byte(s), E:\WIP\BMS\SVN\Code-4.36\SIM\SimLoop\Simloop.cpp, line 558, Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x00000000CF14E24F)
0033:00000000045113DD Falcon BMS.exe, ThreadUnhandledExceptionWrapper()+109 byte(s), E:\WIP\BMS\SVN\Code-4.36\FALCLIB\ehandler.cpp, line 1588+5 byte(s), Parameters(0x0000000000000000 0x000000002F924160 0x0000000000000000 0x0000000000000000)
0033:0000000004E2BA19 Falcon BMS.exe, thread_start<unsigned int (__cdecl*)(void * __ptr64)>()+93 byte(s), d:\th\minkernel\crts\ucrt\src\appcrt\startup\thread.cpp, line 115+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:00000000AD8154E0 KERNEL32.DLL, BaseThreadInitThunk()+16 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:00000000AEDE485B ntdll.dll, RtlUserThreadStart()+43 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
Can anyone help me stop this happening
Using the alternative launcher to set up controls I’ve been able to get this to work. Whoo hoo.
I still can’t get this to work using the normal config but to be honest, I can now fly and I’ve spent enough time trying to fix this so I’m not going to waste more time.
In response to wolfman - the range of raw values (actuals) is 0-4095, but if this was calibrated, then shouldn’t this still be 0-100%? I start in the Taxiway, so the engine has been already started and is running. when in the cockpit (3D) whatever movements I made with my throttle (physical), the throttle representation in the 3D pit hardly moved at all - the engine was at mil power and didn’t change.
I’m a happy man - and appreciate all those who have posted messages to assist…
Couldn’t wait until morning
Tested using the alternative launcher. Didn’t solve the problem but some interesting observations:
1. It kept defaulting to my joystick Z axis for the throttle and it took me 3 or 4 attempts to remove this. Not quite sure what the Z axis is, think it’s my joystick paddle
2. I did manage to configure the TUSBA as the throttle. When I flew, I did get some movement, but only 80 to 100 % - which I guess is better, but still not fixed
3. Checked setup and again it showed that when I moved my throttle I was getting full movement
3. Tested in DCS again and as before worked perfectly
Hi, thanks for your comments.
I’ve started the game in both instant flight or the ground ops mission - both times with engine already started. The throttle is always set to mil power and however much I move my throttle there is only the smallest amount of movement of throttle in the jet. I use the 3D cockpit.
I had configured the throttle in the normal controller setup - and this is what I find strange, I can select the controller axis without a problem and when I move my throttle I get full and free movement of range shown in the setup page. It seems to not work only when I’m in the jet. (Works perfectly in DCS)
I haven’t tried the alternative launcher, but will tomorrow morning. As I said earlier, I have no issues whatsoever configuring it, the problem only seems to affect me when I’m in the jet.
Thanks for the responses. Sorry, I should have mentioned this. After installing 4.35, I had tried to run ‘Ground Ops’ from the taxiway and was surprised when the first thing that happened to me was that I careered away at almost full throttle! I’ve since been testing in Instant Action - so am in flight.
I did try moving the throttle as suggested by M79, by that didn’t help
Further information:
Thinking that it might be a DX issue I’ve run DXView which reports all OK I’ve run sfc /scannow and that didn’t report any problems either. I checked DIView and that seems to report all was OK. Again, I’m having no problems whatsoever with DCS.
I’ve gone switched the pot back to the Vipergear one, since that didn’t seem to make any difference.
If it helps anyone, here is the contents of my DeviceSorting.txt file:
{100412E0-0000-0000-0000-504944564944} “TUSBA TQS R2”
{B679044F-0000-0000-0000-504944564944} “T-Rudder”
{B352044F-0000-0000-0000-504944564944} “F16 MFD 2”
{B351044F-0000-0000-0000-504944564944} “F16 MFD 1”
{40C83344-0000-0000-0000-504944564944} “RIGHT VPC Stick WarBRD”
For the moment I’ve run out of ideas…
Since installing 4.35 I’ve experienced a problem with my throttle - can anyone please help me as it’s stopping me flying in BMS.
Issue:
In Setup/configuration and all seems OK - my joystick, throttle and pedals are correctly assigned and seem to be working as expected; in the Joystick Buttons section, when I move my throttle, the throttle slider moves as expected showing full movement and that my Idle and Afterburner are set.
However, when I get into the cockpit and try to fly the throttle won’t respond (apart from a very small amount of movement). All other controllers are working properly.
Observations:
Up until I installed 4.35, I had been using 4.34 and all was working perfectly.
After installing 4.35, I found that 4.34 behaved the same way and I was experiencing the same issues with my throttle.
I have since removed both 4.34 and 4.35, re-installed 4.35 and still have the same problem.
I also fly DCS and my throttle works as expected. It seems I’m only having this issue in BMS.
Setup:
Joystick: Virpil Warbird
Throttle: Thrustmaster Cougar TQS with TUSBA 2 (I have the Vipergear throttle upgrade pots)
I’m running it on Windows 10 Pro which is fully up to date with patches and updates
My throttle is calibrated using the TUSBA calibration tool (RS_HID_DEV_TOOL). I have removed my throttle and re-calibrated it twice. I have also replaced my upgraded throttle pots with the originals and the same issue occurs.
Can anyone offer any advice? This is really really frustrating
Thanks in advance