Tabasc0

Hey pilots, can u confirm that Virtual Desktop works better than cablelink ? Isn't it weird ? I've read that this is a codec thing.

Thanks for your answers. I've bought Virtual Desktop, but (after a short try on DCS) it is stuttering. Looking now for some advice, setting up Virtual Desktop.

Hello people. I have a quite bad experience in VR with DCS. (On a screen, it runs smooth on high/ultra settings). My specs: Ryzen 5700X3D, DCS on a M2 disk, 3070 rtx, 64 Gb ram. I use oculus tray tool, debug tool, .... But i think my config is simply too short. I think this can be due to 8Gb VRAM. Do u think it can be useful to switch to a Radeon 7800XT for example ? Looking for that one, quite cheap.

Hello @ll ! My computer is a Ryzen 7 5700X3D (AM4), 64 Gb ram, RTX 3070 8Gb, and DCS is installed on a M2 HD. Works really well on my 38'' screen (nearly all to ultra), but what about VR using my Quest 3 ? It works with some concessions, but i want to improve the results. I already use Oculus tray tool to modify FOV and it works great to improve performance, but globally i think i reach the limit with my hardware. What if i upgrade something ? Is it useful to upgrade CPU to a 5950x ? Or maybe the RTX to a 3080ti or a 4060to with 16Gb ram ? Using DCS, i see in the perfs that my GPU is at 100% all the time. The bottleneck calculator (online) says i have about 26% bottleneck due to my CPU. So what can i do to improve perfs in VR ? Cpu upgrading (AM4 socket) or GPU upgrading ?

Bien le bonjour ! Je suis sur DCS depuis 7 ans maintenant, et j'ai une machine qui me permet de le faire tourner très bien sur mon écran 38 pouces. MSI B550 Gaming Plus RTX 3070 8Go Vram 64 Gb RAM 4000 Ryzen 7 5700X3D Depuis quelques mois, je possède le Quest 3. J'ai donc très logiquement testé DCS et je trouve le rendu globalement décevant. J'ai pu progressivement obtenir des performances correctes en jouant sur les paramètres du PC, les réglages graphiques NVIDIA et dans DCS, et le FOV avec Oculus Tray Tool. Mais je rencontre 2 soucis : le cockpit n'est pas très lisible (cadrans, chiffres assez flous, il faut que je rapproche pour voir bien), et l'extérieur du cockpit semble aussi peu clair. J'ai pourtant 72 FPS et en survolant une forêt par exemple, c'est bien. Ca baisse quand il y a du trafic et du détail au sol. Mais si je dois identifier des unités au sol par exemple, ou identifier un appareil en vol ami ou ennemi, c'est impossible tant c'est moche. J'ai parcouru en long et en large les tutos YT pour optimiser le Quest 3 et je crois que je m'en sors pas mal, mais : Ne serait-il pas opportun de procéder à un upgrade matériel ? Je pense à passer à une 3080Ti (une occasion se présente en ce moment chez qqn qui passe à la gamme 4000), ou à upgrader le CPU. Quel est selon vous le facteur limitant ? De mon côté, je dirais la CG parce que sur DCS elle est toujours à 100% (même sur écran où tout va très bien elle affiche 100% d'utilisation). Par contre, j'ai vu sur que j'aurais un bottleneck dû à mon CPU. Je lis aussi par ailleurs qu'il ne faut pas s'y fier... Donc je suis un peu perdu. Est-ce que maintient la config actuelle en essayant d'optimiser encore l'ensemble ? Est-ce que j'upgrade le CPU (si oui, pour lequel en AM4) ? Est-ce que passe à la 3080 Ti que j'ai vu en seconde main (pour 470€) ? Sachant que mon budget est grand max à ce montant de 470€. Merci d'avance !

I wait yes, thank you for the idea. Maybe my Viggen was damaged enough to be unable to use RB75 anymore ?

Hello Viggen boys ! In multiplayer i have encountered a bug : after a mission with some RB 75s, i land back on the home base, reload some RB75s again, but then they don't work anymore. I remember it was an old bug. Does this bug come back now ?

Hello. Same issue here. A black square around the point. Not a problem for navigation, but a problem for JDAMs.

Hello everybody. I've just received an HTC Cosmos Elite. Of course, i immediately tried to run DCS MT. It is impossible to run it. DCS non MT runs perfectly. Does anybody have the same issue ? Is it a known bug ED ? I hope this will be fixed in the next update. My specs : X5 5600, 32 Gb RAM, RTX 3070. Thanks a lot in advance !

Baldrick 33, you are my hero After renaming the HOTAS in each folder of the modules, everything is ok. Maybe it was due to the different driver. I was sure I 've downloaded it on the official website, as usual.

I've tried the bindings on the Viggen and the Harrier.

Hello Flappie. You can find here the input folder, and the dcs.log file. Many thanks in advance ! dcs.zip Input.zip

Hello Flappie ! Many thanks for your answer. I understand the "codenames" idea. I have copied-pasted the codes of my HOTAS (Stick, Rudder pedals and Throttle) in a module folder. It seems that only the stick is correctly binded after that. Throttle and Rudder pedals are not. Same for my second attempt in another module folder. How can we explain this ?

Hello dear pilots. I have changed my motherboard. So I had to move DCS to another disk, then move it back to c : . I have launched DCS repair tool to make my DCS working again. Everything is ok except my HOTAS key bindings. I guess everything has moved due to changes to USB ports (new motherboard). Is it possible to bring all the bindings back ? I have moved the "Saved games/DCS" folder, i find all my *.dif.lua bindings but they are not assigned to the correct buttons. Don't tell me I have to manually bind all the commands for all my modules. Please.

Thanks for your answers, but as i've written above, the afterburners are not on, and (so) i am lower of 1300km/h.