Jump to content

Recommended Posts

Posted

Hi 

I dont fly Tomcat all that often so not sure when this issue crept in but in the latest release I cannot select any commands in Jester menu using my trackir. Neither I can see Jester camera. Though both options are checked in under Special Tab.

There's no selection bar visible and when moving head around nothing happens.

The menu is also very large and plain, transparent compared to refined F4 menu. 

Is there a fix to get the trackir to work again please?

Playing in 2D with no mods.

Posted
21 minutes ago, tpisko said:

Neither I can see Jester camera.

(That feature is broken since DCS moved to multithreaded. It is unlikely to come back.)

Posted

Oh my word, so we occasionally get out of early access. When we do, we break it with updates and leave it at that? Not that the camera is bugging me. Trackir selection is, I cannot help it but to feel we're on a slippery slope with it all. I own 95% of all modules and maps. Maybe 2 or 3 are " finished"and maintained. Where's all this going?

Posted (edited)

No such issues with trackir 5 here, can you upload a dcs.log and a dxdiag.txt?

Edited by BJ55

I7-12700F, 64GB DDR4 XMP1 3000MHz, Asus Z670M, MSI RTX 3070 2560x1440 60Hz, TIR 5, TM WH VPC base, TM rudder, Win10 Pro

Posted (edited)

What draconus wrote, +

2025-05-14 23:42:48.662 WARNING EDCORE (Main): hypervisor is active
Disable Hyper-V from BIOS. (re-enable if issue persists and you really need it)
2025-05-14 23:43:03.913 WARNING SECURITYCONTROL (2180): IC fail: /shaders/deferred/atmosphere.hlsl @ bazar/shaders
Perform a full repair of DCS.
Be sure to not run DCS as Admin.

Edited by BJ55

I7-12700F, 64GB DDR4 XMP1 3000MHz, Asus Z670M, MSI RTX 3070 2560x1440 60Hz, TIR 5, TM WH VPC base, TM rudder, Win10 Pro

Posted

Thanks for responding.

I don't have mods, I changed level of atmospheric haze. I changed it back, makes no difference. How it could affect menu behaviour? 

I'm not running as admin.

I will try the Bios and repair tomorrow. 

Posted
4 minutes ago, tpisko said:

I don't have mods

Right.

C:\Users\tompi\Saved Games\DCS\Mods/aircraft/CJS Super Hornet Mod v2.4/

C:\Users\tompi\Saved Games\DCS\Mods/tech/SAMSitesAssetPack/

C:\Users\tompi\Saved Games\DCS\Scripts\Hooks\lottafGameGUI.lua

IC fail: /shaders/deferred/atmosphere.hlsl @ bazar/shaders

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted (edited)

Shoot. My bad. Apologies. Yes I have assets, no core mods. Still agree, mods. 

Edit: I removed these assets from save games, no change to F14 issue.

I dont have hyper-v in bios.

Edit: hyper-v is also disabled in Windows feature list.

Did full repair, no change to f14 jester menu.

Edited by tpisko
Posted

After removing the mods or renaming "Saved Games\DCS" folder did you perform a full repair? As last resort try with NV 566.36 drivers, the current ones are causing a lot of different issues.

I7-12700F, 64GB DDR4 XMP1 3000MHz, Asus Z670M, MSI RTX 3070 2560x1440 60Hz, TIR 5, TM WH VPC base, TM rudder, Win10 Pro

Posted (edited)

So the normal look around with trackIR works fine in F-14, just not in the Jester menu? Have you tried to toggle the special option regarding this, try, then toggle again and try? Maybe it needs DCS restart.

6 hours ago, tpisko said:

Edit: I removed these assets from save games

Might be not enough. Clean profile is much better for troubleshooting. As BJ55 said - best to rename \saved games\dcs folder temporarily, DCS will start with new config.

Edited by draconus

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted (edited)

Thanks BJ, I did repair, tested, then removed mods, tested.

Asset mods in saved games shouldn't cause issues in jester menu but I can try rename saved games then repair again.

F4 is working beautifully so it's puzzling. It feels more like settings to a degree. But i tested all i could think of.

Can revert to older drivers but I'm pretty sure the selection wasn't working before I updated. 

Thank you Draconus. Yes the view works beautifully. Yes I did try to turn off, then back on the trackir selection. Though I didn't restart in between.

I will try to rename and start fresh profile. Perhaps simapppro or others are affecting it.

EDIT: Renamed DCS folder in saved games, new, default profile, it still doesn't work. 

Edited by tpisko
Posted

Simapp? It could be, there were similar issues in the past with WW software interfering with other devices.

I7-12700F, 64GB DDR4 XMP1 3000MHz, Asus Z670M, MSI RTX 3070 2560x1440 60Hz, TIR 5, TM WH VPC base, TM rudder, Win10 Pro

Posted

I had to dig out my camera and tracker and tested myself - it just works in the latest DCS F-14 - both for view and Jester menu. Out of ideas here.

Do other special options work in your F-14?

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted (edited)

Hi mate, thanks for checking, legend.

See attached. Menu even looks strange - it doesn't have the transparent background. Have no issue with other planes, F4 works beautifully.

My PC is dedicated to DCS, no other apps, games on it. Have latest drivers, tried older ones, or studio drivers as well, no change. I use standard nVidia settings for DCS, really out of ideas.

I use Open track for head tracking.

F14.png

Edited by tpisko
Posted
9 hours ago, tpisko said:

Menu even looks strange - it doesn't have the transparent background.

Ouch, that is borked. Missing texture and some elements. I found similar problem here:

https://www.reddit.com/r/hoggit/comments/1emhdry/where_did_my_jester_wheel_go/

Unfortunately he fixed it only by full DCS reinstall. I hope that repair+clean is enough: https://www.digitalcombatsimulator.com/en/support/faq/repair/#2463807

 

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted

Thank you again, that posts indicated that Vaicom might be the culprit as well. I will uninstall and test.

Otherwise full reinstall it is. Major pain if you have all modules. 😞

Posted

Before you do full reinstall, try removing the F-14 module full restart, then reinstall the F-14 module. It may be something weird Repair can’t see.

Or just do a full reinstall when you go to bed or work and let it chug overnight.

  • Like 1
Posted (edited)

Fixed! Deleting, reinstalling module did it.

Should have thought of that rather than looking for a culprit in settings. @rustbelt - legend.

Thank you all again.

Edited by tpisko
  • Like 1
  • Thanks 1
Posted
47 minutes ago, tpisko said:

Fixed! Deleting, reinstalling module did it.

Unbelievable! That disqualifies the long trusted repair process. I'll go do it myself. Maybe it'll fix some other issues...

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

Posted
On 5/20/2025 at 1:14 PM, draconus said:

Maybe it'll fix some other issues...

It didn't.

🖥️ Win10  i7-10700KF  32GB  RTX4070S   🥽 Quest 3   🕹️ T16000M  VPC CDT-VMAX  TFRP   ✈️ FC3  F-14A/B  F-15E   ⚙️ CA   🚢 SC   🌐 NTTR  PG  Syria

  • 2 weeks later...
Posted (edited)

FYI: The new update messed up my F14 Jester menu again. Back to exactly where it was before reinstalling. 😞
At least I know it is a module delete, reinstall. I think it it might be a good idea to a complete DCS reinstall soon. Not sure how a DCS update can mess up F14 Jester menu. Something developers might be able to answer.

Edited by tpisko
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...