fullcoupe

Fixed after update to OB 2.9.1.48 (which I assume cleared/reset a bunch of files to defaults). Disabled/enabled mods in OVGME and controls are back.

I'm on OB 2.9 and having the same issue, it seems to have happened after upgrading to 2.2.3 via OVGME. My controls list for F/A-18C are completely blank (other than three entries) with the mod enabled. If I disable the mod via OVGME, the controls list returns.

I noticed with the position lights in the OFF position, the position lights remain ON as long as the anti-collision lights are ON. The position lights only turn OFF when the anti-collision lights are OFF. I imagine they aren't paired this way IRL? Already a known issue? Something only on my end? I did a brief search and didn't find any prior posts.

My take: It lands pretty much like a 172, minus the high flare and speed brake after touchdown. Aim for the touchdown point, power down over the numbers (or before the numbers if I get fancy), speed brake out just after touchdown and hold the flare until at a reasonable speed. Simple as that for me. If I'm fast the jet bounces and settles appropriately. If I get slow it stalls out quick but I suppose that is expected for something that heavy. The brakes feel right to me. In short bursts they do a reasonable job at getting the AC back to taxi speed, as long as I bleed enough speed initially after touchdown. I also like that the jet tracks nice and straight when I apply both brakes - very predictable and solid feel. My only challenge has been the engine bottom-end spool up time feels extremely slow...much slower than I'm used to with the Hornet or Viper. There's no quick "bumping" the throttle a bit on final if the engines are already back at idle. It may be characteristic of the F100s but it is an adjustment for sure.

Figured this out. I had an old "flyable F-15E" mod that was using the FC3 F-15C key bindings. I removed the mod, the list of key bindings got much longer, as expected. Doh! I can now jump into the back seat no problem.

Bringing this thread back up as I am having the same issue. Cold/dark start from a scratch mission. Here's where I'm confused... In the keybinds for F-15E_WSO, I have "Occupy Pilot Seat" and "Occupy WSO Seat", set to 1 and 2 respectively. In my keybinds for F-15E, however, these two keybinds are missing. Nothing even related to WSO when I search all fields. I've confirmed the solo flight and disable multicrew boxes are unchecked in the mission editor. Any clues here?

This fixed the problem. Guess I will gradually work backwards to find out what was causing it. Thanks for the tip!

Did both of these already with no success.

I don't use any AV, other than whatever Windows 10 provides. But it was never an issue before and I've been running the same DCS install for several years. Couldn't find any other info on the "Invalid Unit Module" around the forums. Maybe it's time for a fresh install...

I do have FC3, so I should leave it disabled correct?

Performed a repair/clean and still getting the same result. F-15C module is disabled in the module manager. I attached a log. The error seems to be: 2021-04-16 15:29:18.822 ERROR DCS: Invalid Unit Module: "F-15C" I will try removing mods next... dcs.log

I noticed after updating to 2.7, with a new mission in the ME, I set 1x F-15C to PLAYER & ramp start, it starts me as a spectator (F10 view) instead of in control. Checked the module manager, FC3 is still activated. EDIT: What's strange is other FC3 birds are fine (tried the Su-27 and Su-33). The problem occurs in any F-15C mission - training, instant action, etc. Anyone else having this issue?

Welcome IndiaFoxtEcho! I flew all your freeware birds in FSX and P3D, it's been ages since I've been in either of those sims but I remember your work was always top notch (and still is!) It might be starting from scratch at this point, but would love to see your S-3B and T-45C revamped for DCS someday!

I'm still seeing this on the current OB, when zoomed out in external view...couldn't find any other threads on it.

As a RL private pilot, ATC and AI improvements are at the top of my list. I'm hoping at least some basic VFR framework is being planned. Getting wacky altimeter settings, being directed to runway 3 at Nellis (3L or 3R?! argh!), no traffic pattern legs? All pretty essential stuff for even simple flights in both the SP and MP arenas. We have plenty of toys. As many have said the DCS core needs more love! That said, this post is much appreciated. And I'm extremely grateful for the toys that we do have, and the work that continues to be done! I'm here for the long haul!

Center stick. Always.

Would be nice to have a toggle for it like the Harrier.

I am using the Warthog HOTAS - default settings and axis tuning. Saturation for both pitch/roll axis is 100, deadzone 3, no curvature. I find it challenging to do any kind of aggressive maneuvering, and fine adjustments require a lot of input. I can't snap roll or do a quick/tight turn like I can with the Hornet. I realize this may be due to the force-sensing stick...but I don't physically have a force-sensing stick, and I can't increase the saturation any higher... It is extremely noticeable for me when on final with gear down, I can go full aft stick (airspeed 190ish) and the thing moves like molasses. Same with forward stick. Is anyone else noticing the same thing?

I am seeing this as well.

So I fly in VR most of the time, but when I'm creating/testing missions I don't bother using the headset, it is just easier to do all of it on the ol' 2D. While testing, I usually use one of the hat switches to manipulate views. Anyways, I noticed today when I entered the RIO seat (via F1 view, and then pressing 2) I cannot use the hat switch to look around. In the pilot seat, it works just fine. I also noticed that when I enter the RIO seat and then jump to the F2 view, the hat still doesn't work. You have to go back to F1 view, pilot seat, and then back to F2 and then the hat works again. I don't see any view controls specific to the rear seat, and I have the hat bound to 'View up slow, view down slow' etc. This isn't a huge problem, I'm just curious why this is and if there's something I might be overlooking?

Yes...more dirty/weathered birds :D

There are training versions of many other weapons in DCS, so why come up short? I agree it's not a huge priority but I think it's worth having as part of the final product.

I like to watch my Harrier VLs from a ground perspective, so after a landing I'll watch the track. Mostly for amusement, but also to see my mistakes. Done it many times before without issue. So today I reviewed my tracks and they weren't even close to resembling the actual flight. First replay had me nearly doing a backflip before falling flat out of the sky...played the same one again and it starts flying past the landing, climbing out and then eventually crashing way past the end of the runway. :lol: I got a chuckle out of it but a fix would be appreciated. TBH if I wanted to see a comical landing I'd send a heavy AI RTB and grab some popcorn...

+1, with accurate sounds please so I can do this all day:

AI is a big one for me since I fly mostly SP. On that same note, improved comms and ATC logic are a close second. But as we know that is in the pipeline... And the A-10C refresh. :smilewink: