Hi I did the registry mod to give up the rudder axis for the analog cursor using X52 pro’s ministick.

The registry mod script and instructions are from here: https://github.com/alex-smtv/X52-PRO-Mouse-Ministick-to-Axes

When I try to assign the axis in the alternative launcher both “Cursor Y” and “Cursor X” does not get registered. So I wondered what was going on and entered the actual BMS Falcon UI in Advanced settings.

I mapped the axis to the respective axis and turns out it is stuck at the lower bound of the curve:

As you can see there is input (shown on the blue bar) and it does have a mid-point and can do increment or decrement but only by a small amount. It is probably a resolution/scale thing I guess. This is also why the Alternative launcher does not register because the movement is too small to notice.

I didn’t use any profiles in the SST software, uninstalled and install them multiple times, and still does not work.

Any ideas what could happen? I also defaulted all deadzone and in Window’s game controller setting.

Probably not related I bought this few months ago so it is Logitech version not Saitek/MadCat ones.

Thanks

It seems like version 4 will comes with OpenXR implementation and that will increase some fps without steamVR layer

Hi I experienced CTD with 4.36 U3.

The first crash relates to fast forward the game x64 in 2D. (Last Stand)

And the second CTD is about 4 to 5 hours in-game (Last Stand) when landing at Hualien AFB.

Kindly tell me any dump file you would like to see?

Thanks

@Spcialist40k

I don’t think dead zone has anything to do with it but probably has something to do with DX (from what I gather it is the API the game uses to communicate with the joystick) axis assignment. Though I have absolutely no idea what’s going on, having googled for two days no one seemed to have my problem…

Let me explain…

To make DX recognize the mini stick axis we have to label them by changing the number in the reg file and put the unused (give-up) axis at number ‘8’. It does not matter to me because I don’t need the slider or rudder on the joystick anyway.

From my testing or in my case there is a specific combination to make both axis works. To complicate things further the midpoint of one axis is not at 50% at all. (just like my first post)

I have tested many combinations by putting “Ministick Y” and “MiniStick X” in different orders here are my findings:

Y (order) --- X (order) --- Midpoint Y --- Midpoint X
       5             7     Working @50%      Stuck
       5             6     Working but @10%  Stuck
       6             5         Stuck    Working but @10%
       7             6    Working but @ 10% Working @50%
       6             7    Working @ 50% Working but at 10%

Clearly, you can see there is a pattern where ministick Y and X must put in 6 or 7 in order to work, and one channel will have full deflection 0%-50%-100% and the other will have limited deflection 0%-10%-20% something like that. One will not able to use this because depending on the axis assigned you will either constantly drift LEFT or UP because one axis will always at the lower bound of the curve (10%).

I did not mess with the order for 0 to 4 as they are unrelated, they are (Joystick X, Y, Throttle, big and small rotary). So I only mess with the rest 5 to 8 (slider, rudder, ministick X and Y).

I am out of clues really, not sure what is going on. Did numerous reinstall Logitech’s driver and SST (I cannot download Saitek’s one as it is gone now). The same problem happens. I am not sure if it is hardware problem but it works fine with non-analog method (setting bands on SST software).

The reason why I drill on this is that:

1. people said it feels much better than ‘SST band method’.
2. 4.37 introduce a new problem where you can only input one command at a time. Say If you press Up, you cannot press Left or Right diagonally. That means the command cannot stack up and now is incredibly hard to slew with targets moving this is probably the reason why they add a new callbacks for UP-LEFT, UP-RIGHT, DOWN-LEFT, DOWN-RIGHT which is a step back the direction.

For point 2, one guy have the same problem.

And dev responded

Anyways if any of you have ideas please chime in I am out of clues after spending two days diagnosing this on holiday when I could enjoy the game Though I should thanks BMS dev for their hard work because they do this for free!

@mbarb there is no FFR in amd, they only support it in directX 12 so the best bet is turn that off or sell the card and get Nvidia one

@eerturk

Thanks no problem

@eerturk

Can you try making your wingman 2 miles line abreast, does your wingman disappear other than the fuel tanks?

@Seifer

https://forum.falcon-bms.com/topic/29592/pbr-texture-in-cloudy-condition

Related?

@mbarb there is no FFR in amd, they only support it in directX 12 so the best bet is turn that off or sell the card and get Nvidia one

@airtex2019 hi it isn’t hard to replicate, and even I can post a pic one cannot see the problem cause the jet will be invisible anyway.

All you need is overcast condition, cloud tops at about FL150 ish (Current Korea weather can simulate that) and you fly above the cloud with the sun shining.

Make your wingman or lead line abreast 2 miles (we did this not with AI)

Sometimes it goes invisible sometimes not so I think it is probably related to the render engine choosing which light to cast.

Hi, have anyone notice with blk52 PBR texture under cloudy condition where reflection from the PBR material reflects off as a big white blob blending the whole jet into the cloud or the view with only external tank visible? Especially hard to see during formation flying because your lead or wingman now goes invisible.

Just to make sure before Letting There Be “more” Light this gets fixed since AFAIK not much mention on this

Thanks

Hi it worked!

Is there any way to upscale with set g_fVRResolution in the future? In virtual desktop i need to be at high to use the camera mask (the pink mask to show outside world), then set it to 1.5 to upscale the rendering.

For now perhaps setting at Ultra in VD and disable mask for the time being…

Thx

Hi, I cannot enter 3D with Virtual Desktop and OpenXR. OpenXRtoolkit have uninstalled and no necksafer layer too.

2D screen displayed but when going to 3D it CTD.

Here is some of the crash logs

================================== CRASHLOG =====================================
Falcon BMS.exe caused an Microsoft C++ Exception in:
000000001D15B699 KERNELBASE.dll, RaiseException()+105 byte(s)
Exception handler called in UnhandledExceptionHandler.
UnknownBytes at CS:RIP: 0F 1F 44 00 00 48 8B 8C 24 C0 00 00 00 48 33 CC 

Registers:
RAX=0x00000000005f0000  RBX=0x00000000052253d0  RCX=0x00000000005f02d4  RDX=0x00000000332d76d8
RSI=0x0000000039a7f8c0  RDI=0x0000000019930520  RBP=0x0000000039a7fad0  RSP=0x0000000039a7f760
RIP=0x00007ff81d15b699  FLG=0x0000000000000206  
 R8=0x00000000000000d0   R9=0x00000000000000c0  R10=0x0000000000000020  R11=0x00000650fffffb30
R12=0x000000000000005b  R13=0x0000000032a3aa28  R14=0x00000000422b1538  R15=0x0000000000000000
CS=0x0033  DS=0x002B  SS=0x002B  ES=0x002B  FS=0x0053  GS=0x002B

Call Stack:
0033:000000001D15B699 KERNELBASE.dll, RaiseException()+105 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x00000000422B1538 0x0000000004C695E8)
0033:0000000004DF7B3B Falcon BMS.exe, _CxxThrowException()+151 byte(s), D:\a\_work\1\s\src\vctools\crt\vcruntime\src\eh\throw.cpp, line 82, Parameters(0x00000000051253E8 0x0000000032EA4F00 0x0000000005125670 0x0000000042670A38)
0033:0000000004F268DB Falcon BMS.exe, Throw()+171 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\OpenXR\src\common.h, line 19+40 byte(s), Parameters(0x0000000005125670 0x0000000039A7FAD0 0x0000000042670A38 0x00000000332D7660)
0033:0000000004F2692E Falcon BMS.exe, ThrowHrResult()+78 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\OpenXR\src\common.h, line 27+66 byte(s), Parameters(0x00000000333042B0 0x00000000FFFFFFFF 0x0000000000000000 0x0000000000000000)
0033:0000000004F26789 Falcon BMS.exe, `anonymous namespace'::D3D11GraphicsPlugin::RenderView()+937 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\OpenXR\src\graphicsplugin_d3d11_base.hpp, line 142+14 byte(s), Parameters(0x0000000000000000 0x0000000039A7FDB0 0x00000000E7D42DE0 0x00000000E7D42DE0)
0033:0000000004F2AC9A Falcon BMS.exe, `anonymous namespace'::OpenXrProgram::RenderLayer()+874 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\OpenXR\src\openxr_program.cpp, line 600+37 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:0000000004F2A7D4 Falcon BMS.exe, `anonymous namespace'::OpenXrProgram::RenderFrame()+164 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\OpenXR\src\openxr_program.cpp, line 548, Parameters(0x0000000000000001 0x0000000039A7FED0 0x00000000326E2878 0x0000000004F2A730)
0033:0000000004A69959 Falcon BMS.exe, VrSystemOpenXRClass::Render()+121 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\SIM\OTWDRIVE\vrSystemOpenXR.cpp, line 257+82 byte(s), Parameters(0x0000000039A7FED0 0x0000000000000000 0x0000000000000A6A 0x0000000000000000)
0033:0000000004A36959 Falcon BMS.exe, OTWDriverClass::VRSubmit()+57 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\SIM\OTWDRIVE\otwloop.cpp, line 6389, Parameters(0x00000000326E2730 0x00000000326E22E0 0x0000000000000000 0x0000000000000001)
0033:0000000004653165 Falcon BMS.exe, bp::RendererD3D11::renderThreadCB()+341 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\Graphics\Bluebox\Engine\D3D11\RendererD3D11.cpp, line 1136, Parameters(0x0000000000000A6A 0x00000000326E2730 0x000000002EDC0040 0x0000000032925FB0)
0033:0000000004653498 Falcon BMS.exe, bp::RendererD3D11::renderThreadImpl()+56 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\Graphics\Bluebox\Engine\D3D11\RendererD3D11.cpp, line 1082, Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:00000000044C359B Falcon BMS.exe, ThreadUnhandledExceptionWrapper<void *>()+27 byte(s), D:\Runner\workspace\8311d2ca3d042895\hostexecutor\FALCLIB\INCLUDE\ehandler.h, line 24+5 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:000000001EA87374 KERNEL32.DLL, BaseThreadInitThunk()+20 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)
0033:000000001F45CC91 ntdll.dll, RtlUserThreadStart()+33 byte(s), Parameters(0x0000000000000000 0x0000000000000000 0x0000000000000000 0x0000000000000000)

Any ideas? It was working in 4.37.5

Thanks

@Korbi by what I mean is you can create a box, be able to resize and move around the box like comms menu and that box is the passthrough area. (Basically a box filled with pink color?)

I have tried openkneeboard, first you need drawing tablet and second if you combine with VR, once it is opened, it reduces frame rate so it is very choppy when opened.

It seems like the current MR implementation is only suited for real full cockpit built only.

Yes I have pico 4 and the camera isn’t bad at all

Like this

https://cdn.discordapp.com/attachments/1193927497314734130/1193927498510110760/A07A4987-E5B1-47EC-8C13-CB81B8DE83C4.jpg?ex=662b1461&is=6629c2e1&hm=b202e47a7d9e4e7d038f060506e97eb413ac50b8169799c825e8013eeee4f6b2&

https://cdn.discordapp.com/attachments/1193927497314734130/1193927498027778048/F4EA1E76-B360-4BB5-B346-ECA799B8367F.jpg?ex=662b1461&is=6629c2e1&hm=dc08f5726113fc3ee0a6287e8c65e40aa6f799483003479d774de99a5c67b89b&

@oleuzop hi will there be a choice to create a box to passthrough things written on your table instead of the whole cockpit with panel? I could imagine you can place the box on the knee while leaving other panels in virtual world.

Like this one
https://flightsim.to/file/64739/color-panel-for-vr-passthrough

Very useful if you jot down things, and be able to read it while flying