II.JG1_Vonrd

Are these needed?

How do you request control? And, how to unpark the cyclic? As with most modules there are so many strangely named controls that I'm not sure what they are specifically called in the controls menu.

That's affirmative... it's checked. I've tried it in hover as well as normal fwd flight... about 150 kph and constant altitude. As soon as I'm in the fwd cockpit it dives and rolls into the ground. Does Autopilot Hover or Route need to be engaged? If so, for route, that makes it useless for attack unless you have pre planned waypoints... and who has that in the shitstorm? I'm sure that there is something that I'm missing or there is an actual bug.

In Wags' video on the Schturms he switches into the front cockpit to work the missiles using Petrovitch to fly. When I attempt it the heli goes out of control and crashes. What am I doing wrong? I have Petrovitch activated before I switch positions.

Thank you so much! Now things begin to make some sort of sense. I give you an "A" for technical writing while the writers of the manual remain at "D+"...

Yes, I know but I would prefer to use hat switch. I guess that there's no way to adjust speed of cursor in this mode. Is there a way to edit in lua? Where would this control be packaged in lua?

Apologies for the following but I'm getting frustrated and need to vent: This is regarding the Mirage 200 but it relates to pretty much all of the DCS modules. Can someone tell me what HOTAS control bindings I need and what it is that they actually do? Yes, I've read Chuck's and the official manual and looked at lots of tubes but I'm still confused. For example, Regarding the Magic there are these in the controls menu: CNM Magic (I have this bound but I don't know what it actually does. It seems to have no effect in game). MAG PREP: MAGIC II Standby Toggle. (WTF is it?) MAG SELECT, else PCA Select (is there any use for this? What does it do?) Magic Slave/AG Designate/INS Position Update (I read somewhere that this is needed in order for the missle to fire and I have bound it... but it eludes me as to whether it works... I usually get one Magic off but after that... nothing). NAV Update/MAGIC unlock Oookaay... again, WTF is this? These are just a few examples. Another thing that's driving me bats**t crazy is that the text when you hover the mouse over a switch / control in the cockpit doesn't relate to the wording in the controls menu (and this is common throughout all of the DCS modules). Why not have them the same so that we can see what we are binding and maybe be able to relate to the tutorials as to what we need to bind. The tutorials often explain which switch to activate with the "box" over the switch but since as noted above, the wording doesn't match and who knows what it actually is in the menu. Guys, it doesn't need to be this dense in setting up our controls. The DCS modules are wonderfully detailed and challenging enough. Don't make it so damn convoluted and confusing just to get our controls set up. At least post an explanation of what the different controls do in the settings menu with perhaps a footnote to the relevant page in the official manual... and even then there are items in the menu that I can find no reference to in the manuals. There's just gotta be a better way. With the FTP going on now, what happens when a fresh Noob get's one of the modules and tries to set up controls... they go back to War Thunder or whatever.

Is there any way to tone down the speed of the TDC caret when using a hat switch? It's too fast and coarse to get it right over the target.

Bumping this year old+ thread. Has there been any bites from the Devs? Anyone got a workaround to smoothen the AI entry into maneuvers?

So far fixed for me also, 2nd mission and esc. About 10 mission cycles. Thank you!

Rgr... will do!

Now I'm getting this crash occasionally as well as the 2nd mission crash. I'll just keep sending the logs in through the crash tool. (They must be inundated with crash files by now... should I hold off?).

Thanks for the replies Flappie! I changed KNEEBOARD to KNEEBOARD_Backup but it then just brought up only the kneeboard border. Changed it back to KNEEBOARD and it still shows all of the extra files. There are numerous lua files in KNEEBOARD as well as device and indicator. Do I need to edit one (or more) of them and, if so, how?

I don't have the Openbata Server app installed since have I never yet hosted.

I have a somewhat related issue but not the same. I've made a kneeboard with only the information that I want to see... basically the channels for radio, rsbn and arc along with an image of my HOTAS button mapping. I've placed it in C:\Users\Rick\Saved Games\DCS.openbeta\Kneeboard\MiG-21Bis. When I open the kneeboard, I DO see the pages that I want but as I keep scrolling I see all of the default pages... airport charts, etc. What do I need to do to make the game see only the pages in my custom kneeboard? It seems like there are Kneeboard folders / files all over the place... In C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\MiG-21BIS\Cockpit\KNEEBOARD, (and note that this folder has the Bis as all uppercase), C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MIG-21bis\Cockpit\KNEEBOARD, ... etc. Not at all intuitive. I also have the Kneeboard Builder app and tried saving through it but I still see the default crap. Is there a lua that I need to edit?

Same for me. Only the 2nd mission crash. I'm not going to make any changes until the Devs have a fix. BTW, the solution posted WAAY back in this thread to exit the mission and / or mission editor, opening settings then hit "OK" seems to work for me almost every time. I have not run any Windows compatibility modes or any of the other temporary fixes other than emptying the FXO folder in Saved Games regularly.

Yep, that was it... Thanks!

Whenever I start a mission (no matter what type... from ME, Quick, single, campaign) with engine running or in flight, when I press fly and spawn in the controls are hard over to the left. Not so big a deal when airspawn but very problematic when starting on ground in a helicopter. I have to be really quick on collective and cyclic to prevent a rotor strike. How can I fix?

This does seem to work with ME missions but what about plain vanilla missions / quick missions? I still get the 2nd mission crash (but closing 1st mission, clicking settings then "OK" does seem to work). It's an annoying bug but not worthy of seppuku IMHO. A garlic necklace doesn't seem like a bad idea though.

Thanks, I just did updates of Windows and any drivers that windows detected.

Hi Flappie Here are the two most recent from yesterday as well as one from before I reinstalled LotAtc and OvGME. dcs.log-20210514-032514.zip dcs.log-20210513-235356.zip dcs.log-20210511-213055.zip

Nope... got a second mission crash after appx 15 mission loads and 1 computer restarts (I shut it down each night). Guess that wasn't it. I'm not going to go the Win 8 route. I'll wait for a fix from the Devs.

Well, I think I've found my issue but I don't think it may be helpful for everyone else... I had recently installed a second SSD in order to relieve my C drive which was getting full. I moved LotAtc and OvGME to the new drive. Unfortunately, there were remnants in DCS still looking for those programs. I removed and did a new install of both of those programs completely into the new SSD drive. I know that many of you have said that you have removed any mods that you have. Maybe make sure that ANY programs associated with DCS like those mentioned above as well as others such as SRS, Kneeboard Builder, etc. are removed, check for crash and reinstall each one at a time checking for crash each time. Numerous reload of missions now have no crashes. Fingers crossed. EDIT: I just saw captain_dalan's post above where he had removed pretty much everything but it crashed at 8th time. It's late for me but I'll check again tomorrow. Again... fingers crossed. It was strange that my crashes were exactly as noted in this thread... immediately upon loading a second mission.

Sorry if I sounded accusatory. I read your post as possibly saying that the issue was a figment of our collected imagination. I completely agree that it is probably a vexing problem for the Devs to find the cause of it and I remain confident that they will eventually find the culprit. I am certainly not "demanding" an immediate fix.

Even so... it isn't an imagined problem as I can attest and there are numerous others with the identical issue. Not every bug is found in Beta test as you should be well aware of if you've been in sims for any length of time.