Jump to content

slughead

Members
  • Posts

    1361
  • Joined

  • Last visited

Everything posted by slughead

  1. I draw your attention to the third paragraph of the first post of this thread
  2. Excellent. We got there in the end. That's intentional. The other column has been left spare for future development.
  3. Almost. You have all the .tmh and .tmc files left over in the hooks folder from your previous installation. They can stay there although it isn't an appropriate place for them. You should place those in a folder of their own that isn't part of DCS, e.g. C:\Users\Darren\TargetScripts\THHotasLEDSync\ dcs2target.lua must remain in the Hooks folder. All the best, Slughead
  4. You have installed the source code zip files rather than the dcs2target.zip and TMHotasLEDSync.zip. You must remove the "-main" folders as they are not part of the toolset. You only need to install the files contained within dcs2target.zip and TMHotasLEDSync.zip per the instructions on the GitHub pages for each file: https://github.com/iknowkungfutoo/DCS2Target?tab=readme-ov-file#installation https://github.com/iknowkungfutoo/TMHotasLEDSync#installation
  5. Can you show me the contents of: Saved Games\DCS\Scripts\dcs2target Saved Games\DCS\Scripts\Hooks Saved Games\DCS\Scripts
  6. Thanks. Have you started a mission or just started DCS and grabbed the log? The scripts are loaded only when the mission begins.
  7. Can you share your exports.lua file please? It's in your Saved Games\DCS\Scripts folder.
  8. I’m going to need something to go on. The Thrustmaster console output and dcs.log would be a start. But before that. Please get the files from the links in the first post that are on GitHub. I can only support the latest version.
  9. I haven't used QVFR for a while now. When I did, I only used it for turbo mode, not the QVFR, because you had put a workaround in your QVFR layer to stop DCS crashing when Quest headsets were removed. You didn't push that fix (workaround) into the OpenXR Toolkit. I think I stopped using QVFR during the first half of 2023.
  10. By popular demand, we are extending the Christmas sale until the end of January! Prices will return to normal in February!
  11. Unadvertise for DCS always worked for me.
  12. Not supported doesn’t mean it doesn’t still work. QVFR is probably no longer supported either as the developer has said he doesn’t have the license (I think) to build OpenXR Toolkit anymore which I expect applies to QVFR too. Maybe he could clarify.
  13. I know you didn't ask me, but I turn off sharpening in DCS and OXRTK and just do it in Virtual Desktop. It's one less thing for the PC side to do, and there's a slight gain in frame time headroom.
  14. Oh. It used to work. I’ve nit used QVFR for quite some time. Perhaps it worked before the app changed from DCS to DCS World.
  15. You can use QVFR for just the turbo mode (and it fixes the Quest / DCS hang if you remove the headset while using the META link). In the QVFR settings file, just create an excluded app section for DCS. This will turn off the quad view generation and keep turbo mode. (Written from memory - check the wiki for actual changes required to the settings file).
  16. Also, check the Ultraleap troubleshooting section. Ultraleap | HTCC
  17. Hey Tom! You’ll need to turn off Ultraleap in DCS. There are other settings too as per the instructions on the HTCC website that you must set. https://htcc.fredemmott.com/ Be sure to complete all the steps in the links at the bottom of the page for Ultraleap and then DCS World setup. Essentially, Ultraleap in DCS has taken priority and DCS is using your fingers to strike controls. So follow the instructions on the HTCC page, disable gloves and you should be good to go.
  18. Take a look at Home | HTCC
  19. Does this happen with QVFR turned off?
  20. It's all explained in the first post of this thread. Yes. DCS does not include the code for quad view foveated rendering. Just the means to enable/disable it.
  21. It allows you to turn your hands into mice to point at cockpit controls and click without fumbling around for your normal mouse. It's currently on a 25% Christmas discount. Full details here:
  22. Merry Christmas. Don’t forget to order a Slugmouse
  23. Yup. See how you get along with that. If you're still struggling to stay at 72fps, drop it down to 1.2x. You won't be able to stay at 72fps in all scenarios, especially using MSAA. DLSS will give you a lot more headroom.
×
×
  • Create New...