DirectX stops working
-
So Ive run into an unexpected technical problem.
Ive started a campaign, and Im flying the first sortie of it. Ive got an F-16C Block 40 under me, loaded with 8 SDBs, 2 slammers, 2 9Xs, 370 gallon tanks and a 184 jammer. I am carrying an ATP. Ive got the FCR and TGP on the left MFD, and the SMS, HSD and TEST page on the right MFD. The FCR is SOI and displayed, the HSD is displayed.
I bugged an FCR contact about 40 miles out, and DMS left’ed to switch to the TGP. I made a number of switch changes of TMS up, DMS down, and DMS left, though the exact order escapes me. I ended up in the TGP view, with no directX button presses working. The axes worked, but no button presses were recognised. I could click switches with the mouse, and keyboard presses still worked. No F-ACK page was displayed upon pressing it.
Upon recovering to the BMS setup page, all of the button presses were now recognised again. I initially assumed it was a controllers issue, but now I am certain that the issue is within BMS - otherwise it would be weird for all of my controllers to simultaneously stop functioning.
I have reproduced the issue the once myself on the same computer with the same .cam file. With instruction, a wing mate was unable to reproduce the issue. When I reproduced the issue, I ended in the FCR view instead of the TGP view.
Two other things stood out to me about the mission. I noted that the TGP when switched to, did not need to be switched to with the DMS down - it was already displaying the SOI border. This was in contrast to the behavior I was accustomed to, in 4.32. I also for the initial sortie, had a flashing FPM in the NAV mode. I was able to reproduce the flashing FPM in the second flight. Both times it happened several minutes prior to the TGP issue, and both times it was preceded by an inadverted pickle. For the second time, I was able to stop it flashing by changing master modes. I was not able to reproduce it consistently. I pressed the pickle three times in NAV mode on the second flight, and it only made the FPM flash on the second pickle. I was therefore not certain that the pickle was the cause of the flashing FPM. I understand that typically a flashing FPM indicates a weapon release condition, so I was surprised to see it in NAV mode.
I will try to narrow down the exact series of steps I take to reproduce the issue. Has this behavior been seen before?
-
Interesting bug… could be that u caused some mess with your device DX setup? I don’t remember such a issue that all DX buttons are lost suddenly.
FWIW we did had some bug with TGP DX commands not working in AA mode but that was fixed prior to Release and wasn’t reproduced by anyone, so I think what you describe here is much more severe (all DX buttons lost when in 3D).
-
I dont think its based on the device DX setup, as BMS setup recognises everything correctly.
-
…. FWIW we did had some bug with TGP DX commands not working in AA mode but that was fixed prior to Release and wasn’t reproduced by anyone, so I think what you describe here is much more severe (all DX buttons lost when in 3D).
That’s interesting. In an AG test flight today, I ‘lost’ DMS functions. TGP was on the right, WPN (AGM-65D) on the left. Had to switch master modes a couple of times to get my DMS functions back. I thought it was something I’d done, and maybe it was. If it happens again I’ll try to see what specific actions preceded it.
-
Interesting bug… could be that u caused some mess with your device DX setup? I don’t remember such a issue that all DX buttons are lost suddenly.
FWIW we did had some bug with TGP DX commands not working in AA mode but that was fixed prior to Release and wasn’t reproduced by anyone, so I think what you describe here is much more severe (all DX buttons lost when in 3D).
It appears to have indeed been some mess with my DX setup.
The issue was with the shifted layer. Specifically, that I was pressing the pinky EXP FOV button on the stick. This button is the shift button, although my keyfile deliberately does not contain a shifted layer. In 4.32 I had disabled the shifted layer - however in 4.33 it was enabled by default.
Setting the shifted offset from 256 to 0 disabled the shifted layer, and I can confirm the EXP FOV button works as intended now. It seems that without any shifted layer present, pressing the shift key interrupted all the other subsequent keypresses from getting through.
-
That’s interesting. In an AG test flight today, I ‘lost’ DMS functions. TGP was on the right, WPN (AGM-65D) on the left. Had to switch master modes a couple of times to get my DMS functions back. I thought it was something I’d done, and maybe it was. If it happens again I’ll try to see what specific actions preceded it.
Interesting as well, I spent a lot of time on campaign missions with TGP and I don’t remember ever losing DMS. It could be that you gone to Maverick VIS mode maybe?
If you are able to reproduce again with TGP while Mavericks are loaded (or anything else for that matter) please let me know and I will investigate deeper.@BlueWolf I’m glad that you found the cause
-
And if you can have a “repro case” available (saved mission, steps to induce the issue each time) => it will be more easy for I-Hawk to track the problem down more easily and to fix it
BB
-
The issue was with the shifted layer. Specifically, that I was pressing the pinky EXP FOV button on the stick. This button is the shift button, although my keyfile deliberately does not contain a shifted layer. In 4.32 I had disabled the shifted layer - however in 4.33 it was enabled by default.
Setting the shifted offset from 256 to 0 disabled the shifted layer, and I can confirm the EXP FOV button works as intended now. It seems that without any shifted layer present, pressing the shift key interrupted all the other subsequent keypresses from getting through.
I’ve had the same thing happen a couple of times. When it does, pressing S3 (the pinky button) again sorts it out.
-
Thank you blue!
This was making me go crasy.
All ok now.A m a z i n g update guys!
-
It appears to have indeed been some mess with my DX setup.
The issue was with the shifted layer. Specifically, that I was pressing the pinky EXP FOV button on the stick. This button is the shift button, although my keyfile deliberately does not contain a shifted layer. In 4.32 I had disabled the shifted layer - however in 4.33 it was enabled by default.
Setting the shifted offset from 256 to 0 disabled the shifted layer, and I can confirm the EXP FOV button works as intended now. It seems that without any shifted layer present, pressing the shift key interrupted all the other subsequent keypresses from getting through.
Blu3wolf, can you explain how to " disable the shifted layer " ?
-
in your falcon bms.cfg file found in the User/Config folder, find the following line:
set g_nHotasPinkyShiftMagnitude 256 // Enable DirectX Shifting and specify button offsetset the 256 to 0 - this will disable the shifted layer entirely.
-
Blu3wolf, can you explain how to " disable the shifted layer " ?
…/Docs/Key Files & Input/BMS Key File Manual … pages 7-31+
-
Thanks for the prompt response Blu3wolf & Kolbe !
-
Abit old thread but neverless actual for me, had this wierd behaviour in flight, all the sudden it switch to MRM or dogfight mode, swapped the mfd’s, kicking out the brakes, disable the autopilot etc. Will give it a try to disable the overlay, my pinky is set to the none DX shift but still getting the wierd behaviour.
@Kolbe, flying this sim since release with thousands of hours. Falcon has since we started to improve it (sounds better than hacking right) into FF and BMS in all forms, I know the keyfile has always been the heart of trouble (together with Graphics), did’t excpect to read a 30+ manual about a file that was clearly stated in the new manual that it now was good to edit directly in the setup page.@ the devs, clearly a mistake to has layers on as default, for us that not even know what it is and what it does. Also seen in the joystick docs.
“DirectX is implemented into the key file for the shifted and an unshifted layer of Saiteks X52. On the following pages you can find all info about setting up your Cougar and how to change functions. It is assumed that you’ve read the BMS-Keyfile Manual and the DirectX Shifting Facility Article in the forum.”
That page is non available for us regulars, if I could read it I might get into my old thick head how things work nowdays in BMS. Just need to gt the stick work as intended first.
@devs and modders, Amazing work so far, had a Quick peek into Israel and Balan maps too, will keep me busy for a whileSaitek X-55 on a W10-64 latest drivers for W10
Computer, Black and Cool with a window on itreg. M
-
This is cause by Win10 putting your “unused” USB devices into power-saving mode. Not sure where in Win 10 but you need to turn power-saving off for USB devices.
A Search will get you more information as I have answered this question at least once before and others have addressed it too.
-
Abit old thread but neverless actual for me, had this wierd behaviour in flight, all the sudden it switch to MRM or dogfight mode, swapped the mfd’s, kicking out the brakes, disable the autopilot etc. Will give it a try to disable the overlay, my pinky is set to the none DX shift but still getting the wierd behaviour.
Saitek X-55 on a W10-64 latest drivers for W10
Computer, Black and Cool with a window on itreg. M
Regarding DX and shifted functions on a X55 I have no problems at all in using my current setup. 1 problem though with throttle after shift-paddle.
Perhaps my keyfile sorts your problems out, or at least eliminates the keyfile as the reason for occuring.https://www.benchmarksims.org/forum/showthread.php?24506-X55-keyfile-Full-DX-Programmed
-
@Tiffy, that I’ve sorted out when installing W10. No powersaving for USB’s :), screw the enviroment and run everythin on full throttle
@Snelle, Already have tested your file. Also tried the reg trck for the mouse “stick” thx for that.
Anyway sorted it out by turning of the shifting in Falcon BMS.cfg, thx Blu3wolf. No more wierd behaviours, stable as a rock… now I need to fing whan commando is doing the final zooming in Mavericks… anyone?
Reg M
-
Then I would bet my monney on WIndows 10 and Directx related problems, google for it as it there might be a solution.
You have direct9.0c support? Link for download at Microsoft.
-
yeah got version 12
DXDIAG INFO
–----------------
System InformationTime of this report: 2/10/2016, 19:44:37
Machine name: MEGAGAMING
Operating System: Windows 10 Home 64-bit (10.0, Build 10586) (10586.th2_release.160104-1513)
Language: Swedish (Regional Setting: Swedish)
System Manufacturer: ASUS
System Model: All Series
BIOS: 1901
Processor: Intel
Core
i7-5930K CPU @ 3.50GHz (12 CPUs), ~3.5GHz
Memory: 16384MB RAM
Available OS Memory: 16286MB RAM
Page File: 4847MB used, 13870MB available
Windows Dir: C:\WINDOWS
DirectX Version: 12
DX Setup Parameters: Not found
User DPI Setting: Using System DPI
System DPI Setting: 96 DPI (100 percent)
DWM DPI Scaling: Disabled
Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
DxDiag Version: 10.00.10586.0000 64bit UnicodeFound all devices and no errors on anything.
Got hold of the document for the DXShifting thats implemented, from this thread https://www.benchmarksims.org/forum/showthread.php?25486-Where-is-the-Directx-Shifting-facility-articleWill give it Another go tomorrow, quality time now
Regards M
-
…
Two other things stood out to me about the mission. I noted that the TGP when switched to, did not need to be switched to with the DMS down - it was already displaying the SOI border. This was in contrast to the behavior I was accustomed to, in 4.32. I also for the initial sortie, had a flashing FPM in the NAV mode. I was able to reproduce the flashing FPM in the second flight. Both times it happened several minutes prior to the TGP issue, and both times it was preceded by an inadverted pickle. For the second time, I was able to stop it flashing by changing master modes. I was not able to reproduce it consistently. I pressed the pickle three times in NAV mode on the second flight, and it only made the FPM flash on the second pickle. I was therefore not certain that the pickle was the cause of the flashing FPM. I understand that typically a flashing FPM indicates a weapon release condition, so I was surprised to see it in NAV mode.I will try to narrow down the exact series of steps I take to reproduce the issue. Has this behavior been seen before?
I’m having the same issues: the FPM starts flashing in NAV mode and the FCR switches to expanded mode by itself.
I have set the pinky magnitude to 0 but that doesn’t solve the problem.
I have also tried removing the pinky callback from my keyfile and still the FCR goes in expanded by itself (and I don’t have any possibility to return back to normal view having removed the callback…).
Has anybody found other solutions?
