LeCuvier

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".

I ran a dogfight mission (guns only) F/A-18 vs SU-27 AI and saved the track. I replayed it twice, and both replays evolved exactly like the original mission. I attach the track, and Tacview files of the mission plus the two replays. Everything is exactly the same. A huge difference compared to the WWII replays I've seen. In the WWII replays it seems that the AI bandit makes different decisions evry tim you run the replay. With the jets the AI repeats the samer turns every time. Maybe this is why some people say that the tracks work just fine? FA-18 contra SU-27 Mission.trk Tacview-20250908-FA-18 vs SU-27 Mission.zip.acmi Tacview-20250908-FA-18 vs SU-27 Replay 1.zip.acmi Tacview-20250908-FA-18 vs SU-27 Replay 2.zip.acmi

These look ok. We need to see the bindings of @drspankle.

I've been following this for a long time, flying mostly Bf-109 and FW-190. These missions are generally dogfights with a substantial amount of turning. Each time I looked at the track, I found it went "off-track" after a few turns. On the other hand I flew a mission with the Hornet yesterday, and the track was absolutely fine. Seeing all these posts today, I decided to produce a track. I flew a mission with the Bf-109 vs a Mosquito. I killed the Mosquito and saved the track. When I viewed the track, I found myself shooting into the blue sky turning around aimlessly and in the end was shot up by the Mosquito. I then replayed the same track again, and the action turned out very similarly, but somewhat different. And if you replay the track you will probably see something different again. The duration of the replay is always exactly the same as that of the original mission, so the tracks are truncated at different points in the action. I attach the track, plus Tacview recordings of the original mission and of the two replays. Tacview shows clearly the differences in the course of action, between actual mission and replays. Bf-109 contra Mosquito.trk Tacview-20250906-Mission 2 Replay 2.zip.acmi Tacview-20250906-Actual Mission 2.zip.acmi Tacview-20250906-Mission 2 Replay 1.zip.acmi

ED has still not provided bindings for a 3-position A/P Pitch switch. I added this myself into the LUA file. If you don't want to make the LUA edit, you need to use the pushbutton bindings. You may have missed one of the necessary bindings. Can you post a screen shot of your bindings?

Cannot confirm. Tried again yesterday with a dogfight I won. After a few turn "I" started firing into the blue sky, and very soon the bandit was behind me and killed me.

I remember a time when tracks were working. Can't tell how many years ago, must be a long time.

The answer is "No". But it's possible to modify Lua code so you get two successive commands with a single button press/release sequence. Are you sure your "default.lua" is not modified?

I agree. With little or no wind she handles very nicely. When I first saw postings about ground handling issues, I wondered if my plane was somehow different. But by adding wind to my test missions I was brutally corrrected. Somebody says that the tail wheel is broken from spawn. I believe that would make landing difficult past touchdown. But landing is a pleasure as long as no wind is concerned.

Thanks for responding!

I have tried the ground steering/differential braking again, and I'm totally happy. Version: 2.9.19,13478 MT Terrain: Caucasus on runway (not carrier) Air base: Kutaisi Controls bindings: - Rudder pedals to axis "Rudder" - Gear Brakes left and right to axes "Gear brake left" & "Gear brake right" 1. No wind Observations: 1.1 Taxying, Steering without Gear Brakes (Tail Wheel" unlocked): Without touching the brakes, I can steer her gently left and right, feels a bit like in the Mustang. I suspect that's the effect of the propeller air stream hitting the rudder. 1.2 Sharp turns: I combine pedals with gentle differential braking. This works very nicely. I love it. Compared with other warbirds it's a piece of cake. So far, but... 2.1 Wind 5 m/s from 0 Deg (North): Quite manageable 2.2 Wind 10m/s from 0 Deg: Becoming unmanageable. She wants to turn into the wind 2.3 Wind 20 m/s from 0 DEG: Totally unmanageable. I think she wants to turn into the wind, like a big weather vane. Looks like the wind effect on the rudder is overdone. Edit: Takeoff and landing from Kutaisi was real fun with wind at 10 m/s from 0 DEG as the runway is roughly East-West. Takeoff seemed manageable going to high speed quickly. But the landing approach (from the East) was in crabbing mode and I was really surprised I didn't kill myself. However, taxying to parking position involved a right turn and that was impossible. I have never tried aircraft carrier but that should be a bit easier as the boat will turn into the wind for takeoff and landing.

The engine management has obviously become more complex, and the early access guide does not provide good guidance on this subject. The "Enable Water Injection" switch is working now, but again, no guidance. I'm not flying the Corsair in air combat for now, as I have no clue how to keep the engine from just going on strike, and I'm a bit spoiled from flying the German birds.. However, I have no problem with turning left or right on the deck. I use the axis bindings for left and right wheel brakes, but I also tried with pushbutton commands. No problem here. I just tried again to be sure. If you can't left-turn with the brakes, that means you will do a pirouette like an ice skater when you hit the brakes after touchdown. Is that so? Do you use axis or button bindings for brakes?

Yes I can see the effect when I'm at higher altitude. Expected something like MW50 in the German birds, but it's quite different. I would appreciate a comprehensive guide for its use. The bits and pieces in the posts don't help me.

According to today's change log, the WEP switch has been added. I suppose it's the "Enable Water Injection" switch. I see no effect though.

I have set up a mission for practicing with the BAT bomb. There are 4 large ships (easy targets) and I have 3 wingmen, each carrying a BAT bomb. I hit the ship I locked on to every time. I'm actually surprised how easy it is to destroy a ship with this weapon. But the wingmen always drop them in the water, far from the ships. It looks as if they handled the BAT bombs like standard AN-MXX GP bombs.