LeCuvier

This is really weird! Yesterday I was agreeably surprised when I could control the F10 zoom with the mouse wheel without having touched any setting. But today, alas, it didn't work any more. @NineLine: is this a new feature for which I cannot find the option to change?

Thanks for your feedback, but this did not work for me.

I question this statement, as far as the sim is concerned (I don't know about the real Hornet). I have created the 2-position command for the fuel dump switch a long time ago. And as I verified today, the switch in the sim does not go to OFF when the fuel quantity goes below bingo level, and the dumping continues. So nothing goes "out of sync.

I have re-installed DCS World on my new computer under Windows 11 Pro. I'm almost completely up and running. However I can no longer change the zoom level of the F10 view by scrolling the mouse wheel. I have checked the mouse settings under Windows, and I have reviewed all settings under "Options", but I cannot find any setting that would affect the use of the mouse wheel in the F10 view. I'd be grateful for a helpful suggestion.

It was the texture settings. As I had just installed the software on my new PC, I hadn't reviewed all Options settings. The other modules I tried were not blurred at all. It seems strange that the black shark needs a higher texture setting. All fine now, thanks to all who have responded!

The problem is that somehow the TrackIR is switched back to the "Default" profile when I run DCS World. I saw this after exited from the game. And I think I have found out how to prevent this: I ticked the "Exclusive" checkbox in TrackIR. Tried with two different modules and it works as before now.

I have started using my new gaming computer, and almost everything is working fine now. I have copied my TrackIR profile from the old to the new machine, but it's not working as before. The hotkeys I've defined work fine in TrackIR itself. But as soon as I run DCS World, my hotkeys are overridden by the ones in the TrackIR "Default" profile. Example: I used the "-" (minus) key on the numpad to center the view. I know that this key is bound in some of the DCS modules, and I removed these bindings. But still, the "-" key does nothing. Instead, I have to use "F12" which normally is used in the communication menus. I'd be grateful for a hint how to fix this.

I use the English cockpit, but I think the Russian one has the same problem. The labels of the various instruments and buttons are so blurred that it makes little difference whether I use the English or Russian cockpit. Strangely, I have just switched to a far more powerful PC hardware, and I did not notice this earlier. I tried some other modules, and their cockpits are all crisp and clear. Is this a bug or some setting I've overlooked. Screenshot attached.

I have migrated to a new computer and trying to get everything to work as before. I ran into one problem which probably has a simple solution but I cannot find it. In the F10 map view I used to zoom in and out using the mouse scroll wheel. As things stand, there is no reponse to the scroll wheel in my new install. What am I missing?

I have observed this too, although it doesn't happen every time now. When it happens, I can lock the target with the "Undesignate/NWS/ACM" button. @NineLine : Interestingly, there is this line in the most recent change log: "Fixed: Odd target designation/undesignation behavior due to MSI." If "MSI" refers to the graphics card, I have to state that my graphics card is NVIDIA GeForce GTX 1080. So MSI might not be the (only) culprit, and the bug is at least not completely fixed. Edit: I hadn't realized that MSI integrates NVIDIA chipsets. My graphics card is a MSI GeForce GTX 1080 GAMING X 8G Edit: This might be useful: Before the last update, I had to use the "Undesignate/NWS/ACM" button all the time to designate the target. Since the update, the "TDC Depress" works about half the time.

No problem here. I switched the Data.lua to the new one (modified versions of course) and it works just fine. Also, I compared the new Data.lua by Quaggles with his new one, and the changes are only in the part provided by ED. The modded part has not changed. Your issues might be caused by something else, or the way you've installed it. Actually your issues are similar to what I've seen when I had edited the "default.lua" and omitted a comma at the end of line...

If there is a dedicated .lua file for one of your game controllers (in your case the Warthog Throttle) then that game controller can only use the lines defined in that dedicated file. Good decision!

It seems that this line was omitted in the French version of the file "Throttle - HOTAS Warthog.lua". The best solution would be for the person who creates this French file to add the missing line. You can add it yourself but you will have to re-add it after each update. The missing line is this: {combos = {{key = 'JOY_BTN24'}} , down = iCommandPlane_EAC_ARM , up = iCommandPlane_EAC_OFF , name = _('EAC 2-pos Switch : ARM<>OFF') , category = { _("Special For Joystick"), _('LASTE Control Panel')}}, PS: this kind of problem is why I don't use the German localization of DCS World or any other software, if I can help it. La VO est toujours la meilleure version!

The line you need to use is under the category "Special For Joystick" (Whatever that may be in French).

The commands you have highlighted are for the mouse only. For your throttle you need to bind "HOTAS Slew Horizontal" and "HOTAS Slew Vertical".