bekay

VIACOM PRO allows disabling the menus (Preferences Tab -> Disable Menues), that includes the F10 options - so you better know what you do :)

using WIN10 I can run every executable as "admin", just right click on the icon and select "run as administrator".

I opened the archive and executed the steps in the "Message & Radio Font Size.README.txt" using notepad++ (the editor). ---- as quoted from the readme file ---- TO ADJUST THE SIZE OF THE "RADIO" TEXT: --------------------------------------- Edit the file: \Scripts\UI\RadioCommandDialogPanel\CommandMenu.lua At about line 46-47 you will see these lines that you can change: local fontSize = 16 local fontSizeCaption = 18

try to start your editor using root / admin permissions, that might do the job.

the size is mainly determined by the installed maps, size of "mods\terrains" since yesterday night (open beta update) is now 91GB.

I am not using any Windows-"scaling" and I checked the ScaleGUI option since it was introduced because my old eyes don't like to be stressed by small fonts. I didn't change any graphics option nor graphics card drivers of my system just applied the latest DCS-update and got the described problem, my DCS-stable release works just fine, so the OS and its components/settings are definitely not the root cause. Scaling of the fonts works the developer only forgot to get the proper relation between the mouse readings and the "clickable" areas established.

using a single monitor with QHD resolution (2560x1440) with scaleGUI=true the mouse has an offset of about 200-300pix, to LOG OUT the mouse needs to point to the MODULE MANAGER icon, the offset is horizontally as well as vertically, to exit from the GUI your mouse pointer should be left and above the "EXIT" by about 200-300 pix. without ScaleGUI activated everything is as usual (as before the update).

strange! and in such case, I would temporarily disable the firewall and the virus scanner.

see post #666, B.K.

I'm using the X55 and my advice would be more general, don't use the device SW at all to assign buttons and switches, get familiar with the possibilities to define DCS modifiers, those a quite handy to use your X52 mode switches - each mode is activating a different user defined modifier and so a different layer of controls 1.) take a drawing or photo imaging SW of your choice, create one file for the stick, another for the throttle and import a good picture of your devices. 2.) identify the functions you need to have quickly accessible like the functions related to sensor, weapons, countermeasures and assign them inside the DCS option as you like them to the first layer. 3.) identify the aircraft operating functions like trimming, gear and flaps control, autopilot ... and assign them to a second layer. 4.) Identify emergency functions and assign to a third layer/mode. Document your assignments in the picture/drawing, export those to PNG format and copy to your kneeboard files so you have them handy inside the cockpit. This approach takes a little more time and thinking - your first try will also not be the final, but let you develop the skills needed and the flexibility for the future adaptations. B.K.

unfortunate the script is looking at %userdata%....\temp\... to gather mission information, the "temp" folder used by DCS should be referenced by the %temp% variable. I don't like to use my user data folder loaded with all this temporary data and relocated it to another drive - resulting in permanent "cannot find file ..." messages from the "fetch data script". After the appropriate script modifications and the "international keyboard corrections", everything is working fine. B.K.

Beyerdynamic MMX2, aber man muss geschlossene Systeme schon mögen, hat jedoch den Vorteil, dass andere Personen im Raum nicht gestört werden, der USB Adapter wird via Klinkenstecker mit dem Head Set verbunden, somit kann das Teil ggf. Auch direkt via Klinke genutzt werden. Das Mikrofon ist sehr gut, der Tragekomfort ist auch nach zwei, drei Stunden noch angenehm - für meinen Kopf, und darin liegt eventuell das individuelle Problem, wenn möglich ausleihen und ausprobieren, B.K. Gesendet von meinem SM-T800 mit Tapatalk

das das VRAM deiner GTX960 zu 100% genutzt wird, ist ganz normal, ist bei meiner GTX760 ebenso der fall, also weiter suchen :) B.K.

es gibt Beleuchtungssituationen, die auch für den Einsatz von IR-Dioden nicht perfekt sind, Alternativen - wie hier gefragt - gibt es. Notwendig dazu sind Kenntnisse zur Arduino-Programmierung und minimale Lötarbeiten zur Verbindung eines z.B. Arduino Nano mit einem so genannten 9 DOF Sensor ( wie GY-85). Ein GY85 Sensorboard ist etwa so gross wie eine 1-Euro Münze und kann gut zentral auf dem Bügel eines Headset montiert werden. Die Software des Arduino liest die 3 Einzelsensoren auf einem GY85 Board aus, erledigt einige Kalkulationen und sendet die resultierenden Daten via USB an den PC. Sowohl für Opentrack als auch FTNoIR gibt es ein Plugin, das diese Daten dann filtert und via TrackIR-Protokoll an DCS weiterleitet. Als Einstiegspunkt: https://sourceforge.net/projects/gy80facetrack/ B.K.