mkel2010

Please let us know when they fix it.

I just checked and I get the same message. It's likely because the grip doesn't need to update and having it connected while the base updates would likely corrupt the grip's firmware. Best bet is to disconnect everything but the base, keyboard and mouse to run the update.

Take a look at the DCS Community Keybinds, linked below. Installing it (and the Quaggles Command Injector) gives you a series of Custom key binds, which include Fast and Slow trim adjustments. There is a link to the Quaggles Command Injector on the page linked below. For me, the trim changes happened too fast for my liking and using these key binds have allowed me to slow the trim changes way down so no reason to believe they won't do the opposite for you. https://github.com/Munkwolf/dcs-community-keybinds

I went ahead and disconnected a couple of USB drives and the hub and updated my rudder pedals and throttle. Everything went well and force feedback actually works now with the throttle handle in DCS.

SimApp Pro warns that ALL other USB devices need to be disconnected (including USB hubs) before updating firmware on Winwing controllers. Has anyone done these updates WITHOUT disconnecting every other USB device in the system?

I feel your pain. It's much more noticeable when pushing above 50 inches of manifold pressure on a dirt runway as with some of the Normandy airfields. I would make sure you set the 6 degrees of right rudder and two degrees nose heavy pitch trim and try some take offs at around 50 inches of MP. You'll want to do this from an airfield with a long, wide hard surfaced runway like Manston. What has helped me (definitely not perfected yet) is to make sure you hit LCtrl + Enter to turn on the graphic for your control positions. Make sure to keep the stick aft of center until you get to 100 MPH and then just relax it to neutral; lift off about 120 MPH. Keep increasing the MP by 5 inches or so as you improve until you can take off without issue at 61 inches of MP. This is definitely a work in progress for me.

Not sure if this is a bug or I'm just doing something wrong. If I set rockets to single, I can fire them all day long (with unlimited Ammo setting on.) However, when I change the rocket setting to Auto and have the Rockets To Be Fired set to 2 or more, the rockets stop responding after the first salvo. I have to exit the mission and restart to get any rocket setting to work.

Yes, that was the solution to the issue.

I installed Open Mod Manager today to replace OVGME. I got everything set up and then tested DCS to see if I was able to get the community Keybinds back again (they'd previously stopped showing up.) On opening DCS, all the Custom keybinds were there. I shut down both DCS and OMM and then deleted the OVGME application. Came back a little later to fly in DCS and when I got into the settings, the Custom keybinds were gone. I went back into OMM and when i tried to load the hub I had created for the main DCS World folder, I received a Target Directory Access Error basically saying there was a permissions issue with the main DCS World folder. I tried recreating the hubs and had no issue with the hub I created for the Saved Games folder but still got the Target Directory Error for the main folder. The DCS World folder is marked as Read Only by Windows 11 and cannot be changed. I'm not sure that's the issue as it apparently worked correctly the first time. I was able to manually install the Quaggles Input injector in the main DCS World folder and everything works, but I'd like to hopefully figure out what the issue is. @sedenion EDIT: The solution is to run OMM as administrator.

Thank you.

I couldn't find the "uncontrolled" menu item you referred to. However, placing static planes seems to have worked. I haven't actually been able to hit any of them yet (hence the practice nature of the mission) so I don' know if I can actually blow them up.

"Bound" I'd make sure you haven't got it bound to a different, conflicting action either in the game or with Windows. I haven't had that issue, although I have had an issue with DCS randomly loosing other keybinds on my joystick.

Three places to "fiddle" with things: The Beam Eye Tracker settings (they each have a tool tip to let you know what they do.) Second, the Mapping and Accela Filters in Opentrack. And finally the in-game TrackIR settings for each axis (Filter Axis commands only, then look at the settings for Pitch, Yaw and Roll first.) Best way to do this is to get everything running in the game and then adjust each setting and check the results (Alt-Tab to get to Opentrack; once that's open over DCS, you can access Beam Eye from the Windows task bar to get to Beam Eye.) You can set dead zones in Mapping on Opentrack as well as turning distances for your head vs. in-game. With the in-game settings, you want to play with Dead Zones, Saturation and Curves (negative curves seems to work the best for me.) Also, don't forget to configure a Center Keybind in Beam Eye. I have it mapped to a button on my joystick. If the view your seeing starts to get out of control, a quick push of the button will center everything up.

I created a mission on the Normandy 2.0 Map to practice ground attack. I placed a number of ground units at an airport along with several Bf-109s at what the map identifies as parking areas. However, when I fly the mission, the 109's end up at a different airfield roughly 4 miles away and on the opposite end of that airfield from where they were placed. I gave these aircraft nothing to do, no triggers or anything else. I just wanted ground targets. Whenever I go back into the Mission Editor, the 109s are right where i put them, but actually flying the mission they aren't. Admittedly, I'm new at this so I might have done something wrong but this certainly seems like a bug to me.

I am having issues saving some, not all, new snap views. Deleting the snapview.lua file helped somewhat, but I finally had to resort to trial and error editing of the snapview.lua to get one view the way I wanted it. My issue is particular to the P-51D, specifically trying to get a (visible) snap view of the fuselage fuel gauge. (The "stock" snap view for the fuel gauge has the gauge mostly hidden.) Manually setting the camera with the view I wanted, going briefly to the snap view I wanted to save it in and then using RAlt+Num0 resulted in returning to the original view with no changes no matter how many times I tried. Even tried it with a different snap view slot with the same (lack of) results. I didn't have any issues saving other snap views after deleting the original snapview.lua. I was eventually able to configure the view I wanted after about an hour of editing the snapview.lua.

One thing I've noticed is that Beam Eye takes control of the camera so you won't see an image any more with Opentrack's interface. It also means that you'll need to shut down Beam Eye to turn off the camera. Previously with Opentrack by itself stopping tracking also shut off the camera. With Beam Eye, you'll also have the option of different resolutions from your camera, depending on the camera. It's another setting to be aware of if you have issues.

I started playing DCS a short time ago and began with Opentrack and it's built in Neuralnet tracker. I wasn't happy with all the jumping around I got with the video using it. Yesterday I found out about Beam Eye and after watching a couple videos purchased the standalone version. I'm still playing with the configuration but I will say it's much more stable than the Neuralnet tracker.

First of all, I'm not sure if this is the correct sub to put this in or not. I've created several simple missions to practice dead reckoning and pilotage in a P-51D on the Normandy 2.0 Map. When flying the mission, I use Ctrl+K to mark my position on the kneeboard map. This works well - for the first two map pages usually up to the halfway point between the second and third waypoints (page two of the generated maps.) As soon as I get to the third page, the marking stops on the third page but does continue on the fourth and fifth map pages, which are zoomed out views. The mission generates the first three or so zoomed in pages, up to about the fourth waypoint, and the switches to zoomed out map pages of the overall mission routes. The Ctrl+K marking continues to work on these zoomed out pages, which are next to worthless for any kind of navigation. Am I doing something wrong in creating the missions? is there a way to correct this kneeboard map issue.

PM Sent.