Mud

I just realised this question would probably have been better posted in the Mods section, than the Mission Editor one. So if a Mod would be so kind to move it. Thank you.

Can anyone tell me how to properly add a custom squadron and with patch to the logbook in 2.7. I got it working in 2.5.x in the DCS installation folder. It appears that "DCS World\Scripts\Database\Troops\" has been moved / replaced. Also, since everything is being moved to Saved Games as to not pollute the installation folder, I wonder what the proper method is now. Mud

I still use a GTX1070 as well and actually have pretty good frame rates in VR with most stuff and shadows set to high (terrain shadows flat). The only place where my system struggles is on the super carrier. Mind you, I have not flown in MP on busy servers. Spec can be seen in my sig. Mud

Mine is bound to the Warthog throttle base slider as well, and during my test flight yesterday (cold start) the flaps lever in the cockpit was also not moving. The actual flaps themselves are.

Wow, splendid job on this one, ED!! My hat off to you guys! Thanks! Mud

When flying at the engine settings specified by the real P-51D manual for minimum fuel consumption, I noticed that I start losing power after some time just like with the Bf109. I assume this is the modeled spark plug fouling. Example: 5000ft at 1600rpm and 30MP However, the manual states that this setting, just as with max cont. and max cruise, can be used continues.

I'm glad I found this thread. I was doing a long distance cruise flight today 10 degrees C, no wind at an altitude of 5000ft. Engine settings were 1.15 ATA at 2000rpm. I noticed my speed gradually diminishing from approximately 270kn to 220kn TAS, and me being forced to change the prop pitch to maintain 2000rpm over the course of about 1 hour of flying. I just couldn't figure out what was going on, but I assume it was the spark plug fouling then. Mud

I just tried, but couldn't get it to work properly. Perhaps @ams999 can help out as he made the lua modification in this thread. I just packaged it into a file to be used with OVGME. Certain things I manage to do with the lua keybindings and switches, but others and try and fail miserably Mud

I think I found the reason, and solution. At least I'm able to reproduce it on my end. When you open the kneeboard, it will also bring up that radio mouse cursor. If you then close the kneeboard while the mouse is at the edge of the kneeboard (like showing to increase/decrease the size of the window), then the pointer will not disappear or at least reappear once your main crosshair cursor disappears. To solve it, open the kneeboard again and make sure the mouse is not at the edges when closing it again.

I should have put a marker in my screenshots. In the first picture the pointer is just above the right eyebrow of the canopy. In the second picture it's on the right side of the HUD.

You cannot declare the off position for a 2-way switch on the Warthog Hotas. In my case I'm trying to bind the auto-slave to the RDR ALTM switch. It's an ON or OFF switch, so only the ON can be mapped in the bindings in DCS.

No, I want it to work with a toggle switch: Toggle up turns on auto-slave, toggle down turns it off. Currently, up turns it on, but to turn it off I have to flick the switch down and then up again.

That one behaves the same as mine. What I don't get is that both mine have the up and down value set, yet it only works for the auto-collective and not the auto-slave.

Hey folks, I changed the default.lua for auto-collective in autopilot to the following so that I can use the EAC toggle switch on my Warthog to turn it on and off: {down = device_commands.Button_18, up = device_commands.Button_18, cockpit_device_id = devices.AUTOPILOT, value_down = 1, value_up = 0, name = _('Mud Auto-Collective Toggle'), category = _('SA342 Autopilot')}, That one works fine. Looking at the Auto-Slaved toggle, it looks like it's already set up in that way in the default.lua. However, there I have to flick the switch up to turn it on, and the down and up again to turn it off. So it's not behaving the desired way. {down = device_commands.Button_12, up = device_commands.Button_12, cockpit_device_id = devices.AUTOPILOT, value_down = 1, value_up = 0, name = _('SA342 Auto-Slaved Toggle'), category = _('SA342 Pilot Stick')}, Anybody have an idea why? Mud

Do they appear if you set those units to hidden in the mission editor?

Most likely this, Faviou2: Source: installation help on the A-4 Discord channel: The module is installed correctly, but I am unable to take control of the aircraft. Ensure you have installed Microsoft's Visual Studio 2015, 2017 and 2019 Redistributable libraries. Windows users running DCS world are typically running x64, so you will want to download and install vc_redist.x64.exe (~15 MB) from the following page, install the library, and then restart your computer: https://support.microsoft.com/en-us/topic/the-latest-supported-visual-c-downloads-2647da03-1eea-4433-9aff-95f26a218cc0

From military.wikia.org: Although the A-4's use as a training and adversary aircraft would continue well into the 1990s, the Navy began removing the aircraft from its front line attack squadrons in 1967, with the last ones (Super Foxes of VA-55/212/164) being retired in 1976.

When you install the 2.0 beta you have to indeed delete your previous A-4 key binds. So you lose those, but not for any other DCS aircraft.

Here are two screenshots which show the issue. As you can see the radio menu is not visible at the moment. Moving the mouse brings up the cyan cross curser and makes the dot vanish, until the cyan cursor dissapears after x time of inactivity (as it should) Mud

Okay well, I have not been able to reproduce it so far. In VR: You have the cyan cross when moving the mouse. Once you open the radio menu, you get the while dot. The problem was the white dot staying around even when the radio menu closed. I though SRS could have been a factor and I have tried with both it off and on now. But all is well. I will pay attention to it and if it happens again try to figure out what exactly I did to make it happen.

I fly in VR. I did a few more flights the other night where I could not replicate the issue. Tonight I will do a few more tests and I will report back if I am able to replicate it.

I can indeed confirm from my end that this was in VR. Oculus Rift CV1

You can find it here, under the 3rd party developers: https://forums.eagle.ru/forum/145-ugra-media/

I have seen this in the Syria map as well.

I have noticed the same since a while ago. Definitely since before today's patch. It seems to happen after you have used the radio menu once.