-
Posts
245 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Mordants
-
The next thing I would suggest is do a repair. How to repair/cleanup or update DCS World? (digitalcombatsimulator.com)
-
I had similar thing a while ago. If you have any mod's disable them and try again in the first instance.
-
DCS Super Hercules mod by Anubis
Mordants replied to Eight Ball's topic in Flyable/Drivable Mods for DCS World
Unzip file and put the folder into saved games/DCSopenbeta/Mods/aircraft and away you go. Do not put the folder in the DCS World root folder. -
-
I had similar shenanigans too, my solution was to zero out the translations and shift an extra degree into rotations. Whether or not it had anything to do with it, the next time I used it, it was fine.
-
I did all the VD things for my Quest Pro and loved the graphics, however I could not get either sound or mics working correctly in SRS. Sometimes one or the other and most times I had to go into settings and play with the default sound/mic outputs. Then in DCS muck about with sound/mic inputs/outputs there. Real faff where with link cable it just works.
-
Right click desktop icon Correction is in: Properties -> Compatibility -> High DPI Settings -> Override scaling behavior performed by System.
-
DCS Super Hercules mod by Anubis
Mordants replied to Eight Ball's topic in Flyable/Drivable Mods for DCS World
https://www.mediafire.com/file/y5qov91ds5gvofv/Hercules_ver_6.8.2.zip/file -
Apologies I wasn't aware default is 200.
-
I had to bring mine down to 250 to stop the audio cut outs.
-
My system is almost identical to yours apart from I have a 4090 graphics card and with a quest 2 my system coped reasonably well with DCS 2.8. I was however always tinkering with various settings. I subsequently got a Quest Pro three weeks ago (I prefered it to the Q3) and with DCS 2.9 had to start tinkering again, it's took three weeks so far and I now have a reasonable picture. This though with DLSS turned off, shadows turned off and others turned down. FPS in single player gusts between high 70's and high 80's. Multiplayer fluctuates between 30's and 50's, mostly around 45 and 50 on Rotorheads. Grapics for me are quite resonable now apart from shimmering on multiplayer, and OK on single player. I hope you find your ideal settings swifter than I did, but then again I'm not so bright lol.
-
I think if I remember correctly even with 500mb encoding I still had some audio stutter/stutters. I'll have to try it again. I had to down to 200 to achieve a stutter free esperience
-
Quest 3 & Virtual Desktop Crash- OpenXR Call Failed, Error Code: -2
Mordants replied to Slvrsurfer's topic in VR Bugs
Hey thanks for the reply, It's updated itself so all good. Cheers for instructions. -
Quest 3 & Virtual Desktop Crash- OpenXR Call Failed, Error Code: -2
Mordants replied to Slvrsurfer's topic in VR Bugs
Hi I can't seem to get the update. I click on it and the box says purchased but then nothing, any ideas? -
The new version is great,thanks for the update. I seem to have lost the mouse zoom function though, was this intentional or do I have a snag?
-
Option to export lat/long co-ordinates to knee board
Mordants replied to tempusmurphy's topic in DCS Core Wish List
A great alternative whilst you wait is Scratchpad.- 1 reply
-
- 2
-
-
Hi I think this post is more suited to this topic since my problem only occured after the FM update. I seem to have a unique problem with my Stream Deck and the new SA342 Gazelle module. Before the update my SA342 profiles all worked as advertised with the different variants. The settings for the Stream Deck are all ok because all other DCS modules work, both fixed wing and rotary wing. There are the latest SA342 profiles in the saved games export module folder. The SA342 2.0 stream Deck profile version found in this forum is available on my Stream Deck The export.log shows as no module found on line 4 with a subsequent Huey loaded up correctly from line 5. Stream Deck comms output is inconsistent though with global connection showing activity and then next time not Config.lua looks to be ok too, which I expected because other modules are fine. I’m not sure what else to try having made numerous small alterations for the naming of each lua file just in case there was a syntax error but nothing seems to work. I am open to any ideas to try and solve this and hope there is someone here who can help. Please see attached logs and pictures which might help. Export.log Config.lua