Ornithopter

As was noted in another, much older thread, the problem has everything to do with the new 'viewAngleVertical' parameter that got added at some point. It defaults to 0 for every aircraft, and this apparently causes the game to basically ignore all the custom view settings. It was broken before, but there was previously a workaround which apparently stopped working. To fix this problem, I had to first recreate my default view/horizontal FOV in one plane with the ingame controls and Alt Num0, using an old screenshot as reference. Once I got that set in the Snapview file for one aircraft, I just took the Horizontal Field of View (close, but not exact to what I had before), and the new Vertical Field of View (the game calculated it, I guess based on my screen aspect ratio and in-game zoom?), I just manually pasted that into section [13] for every single airplane. Fortunately, I prefer the same default FOV for almost every airplane, so that method was viable. None of the angles were changed, so I've basically restored all my custom view settings, with the FOVs within a degree of where they were before. It would have been hell if I had literally had to load every airplane up and recreate all of my cockpit views again by eye. I realize that this is an "open beta", but how something so fundamental to the viewing system can actually slip through and get published baffles me. I was going to fly today, after an extended break, but instead I spent the afternoon looking for a solution, and fooling around with text files..... edit--The good news is that once you get that sorted out, everything works as it apparently should. No "Right Control + Num0" workaround required.

Well, yes...I think most people would agree that they should fix bugs.

Just got bitten by this bug, for the first time tonight, after not playing DCS for a few weeks. Sucked when I realized that the "Zoom Normal" control, to take me back to my default zoom didn't work, and I really do like my custom zoom level. I noticed in multicrew aircraft that switching to the "second seat" and resetting to default zoom worked, and then it would work when you switched back to the main cockpit. In single pilot aircraft, there is nothing to switch to, and the Zoom Normal control just doesn't work.

And not in the hot fix either

This isn't a question about aerodynamic traits. This is a systems question about how the cyclic trim interacts with the Autopilot. Either the cyclic trim is supposed to work as a single click at the desired attitude, like the Mi-8, or else, you're supposed to hold the trim in while you are changing from your present attitude to your desired one like the in the Shark. Right now, a quick click on/click off of trim, as you would do in the Mi-8, interacts with the autopilot enough to cause an annoying oscillation. This is a fact. The only way to properly trim the Hind at present is to operate the trim exactly like you would in the Shark, which is surprising to a lot of us, because in the absence of any other information, one would naturally assume that it would behave more like the Mi-8. That assumption could be wrong, and obviously if that's how it operates in real life, then so it shall be, but I haven't read anything thus far that provides an answer to how it is supposed to work.

Same here. By comparison, clicking the trim button in the Mi-8 doesn't temporarily disable the yaw and pitch channels, so you click it once, the virtual stick gets centered in the new position, and it stays there, just as if you were holding it manually. No attitude changes after button release. From what I can tell, in the Mi-8 there is no interaction between the trim and the autopilot at all, and if you want to change what the ap is biased for, you have to turn the knobs. In the Mi-24, its temporarily disabling the ap channels, even if just for a split second, and as soon as they come back on, they screw up the trim you just thought you had set. Different behavior than what we see in Mi-8. Maybe the real life helicopters are just different in that regard, but If they are supposed to trim the same, then one of them is definitely modelled wrong. I really wish somebody that actually knew could give an answer to this question: Do you need to depress and hold the trim button in the real Hind, or not? Seems like a simple question with a simple answer!

Ok, so I've done like everyone else and started disconnecting and re-plugging controllers. Succesful load! What I'm seeing here is that there appears to now be a hard limit on the number of controller devices. More than 6 devices appears to be the problem. On my end, it doesn't matter which controllers are connected, even the virtual device, just that 7 or more will cause it to hang at the loading screen. Great job, Flappie, and everyone else zeroing in on things like this! Should we just wait for a hotfix now?

CCP stands for Custom Control Panel, and it is an Ipad App that creates a virtual touchscreen controller for the PC. In the meantime, I'll see what happens when I start disconnecting things.

Here are the relavent lines. I think we have exactly the same file. I deleted the file, cleaned and repaired to rebuild the file. Same file as before, same log, still hanging on load.

Thanks for continuing to follow up on this, Flappie! And hi, Mustang, both sorry to hear you're having the same problem, but also a little relieved I'm not the only guy having that particular one. Ok, I tried that, and it rebuilt the entire DCS.openbeta folder in Saved Games, but unfortunately no joy. Same error as before in the .log. (last few lines of log below) 2020-12-20 18:57:29.282 INFO SOUND: Channel layout: FrontLeft FrontRight FrontCenter LowFrequency BackLeft BackRight SideLeft SideRight 2020-12-20 18:57:29.389 INFO DCS: gDescription: "NVIDIA GeForce GTX 1070" gVendorId: 4318 gDeviceId: 7041 gMemory: 7998 MB 2020-12-20 18:57:29.399 ERROR EDOBJECTS: Destruction shape not found AVIASHTAB_CRASH 2020-12-20 18:57:29.401 ERROR EDOBJECTS: Object HB_F14_EXT_PHX_ALU with id=320 already declared in table MissileTable 2020-12-20 18:57:29.498 ERROR WEAPONSBASE: invalid cx data <weapons.missiles.MBDA_Mistral><./CoreMods/aircraft/SA342/SA342_Weapons.lua> 2020-12-20 18:57:30.268 WARNING LOG: 1 duplicate message(s) skipped. 2020-12-20 18:57:30.268 INFO DX11BACKEND: DX11ShaderBinaries::loadCache ./Mods/aircraft/F14/fxo 2020-12-20 18:57:30.270 INFO DX11BACKEND: DX11ShaderBinaries::loadCache done. Loaded 0/0. 2020-12-20 18:57:30.322 INFO EDCORE: (dDispatcher)enterToState_:1 2020-12-20 18:57:31.702 INFO UIBASERENDERER: Cannot load font [E:\Program Files\Eagle Dynamics\DCS World OpenBeta\dxgui\skins\fonts\]! 2020-12-20 18:57:33.229 ALERT Dispatcher: Error starting Game GUI: [string "./MissionEditor/MissionEditor.lua"]:86: invalid order function for sorting 2020-12-20 18:57:33.229 INFO EDCORE: (dDispatcher)enterToState_:2 No Mods installed on my end, and did another Repair and Cleanup, just to be sure. As far as I can tell, my installation is completely clean.

I tried this and the GUI continues to hang. I'm not sure now if I'm in the correct thread, and will start another if that would help you sort one person's issue at a time. For now though, the error in my log file is still exactly the same as the cut/paste above (MissionEditor.lua problem), despite rebuilding the MissionEditor directory in both Saved Games, as you suggested, and DCS root as well, via a Repair. I'm not completely familiar with the term "Shadow PC" as it pertains here, so apologies if I'm posting my initialization problems in the wrong thread.

I seem to be experiencing the same or similar error after the 12/17 update. After the login screen, the initial loading screen hangs at 100% forever. Here is dcs.log dcs.log

This might literally be one of the most absurd and ridiculous "suggestions" I have seen all year long.

I think EVERYTHING should be bindable. This is the standard of all the good ED planes. For instance, on the Hornet, you can bind everything. Everything that can be controlled in the aircraft by the mouse should also be assignable to either a keyboard combo or joystick button. This is what you can do on most other airplanes in DCS World, and the JF-17 should be no exception. Some of us have home cockpits, and really don't want to be mousing over things. Like everyone else, first thing I do when I get a new plane is start binding things. This aircraft is all about MFD's, and being able to bind them to keys is greyed out??? Really hope this changes, and very soon.

To me, it isn't a choice between which one, it's only a choice of which I want to learn first. It would be a sin to not have both the F/A-18 and the F-14! That said, one of the things I'm really liking about F-14, as already mentioned, is the lessened workload on the pilot. Sometimes planes in DCS can be pretty mouse-click or keyboard intensive, which at times can be awkward and distracting especially if you are trying to really get good technique down. It isn't a big deal, but as someone very much in the learning process of carrier ops and operating within a squadron, being able to concentrate on just the flying and fundamental technique while either a human or Jester handles certain aspects goes a long way towards easing the learning curve for me. I'll get to learning the F/A-18, in depth, in time, but I think that for someone like me who is very new to the proper operation of carrier jets, the F-14 was the right choice for me to do first. With the F-14, more than a RIO that helps us fight the bandits, we can literally have an experienced human instructor in the back seat. At my noob level of knowledge, I think choosing the F-14 to start with will make me a better virtual naval aviator in the long run.

When you are talking 3mm here and 3mm there, you are talking The Force. I guess that's why not everyone could qualify as a military aviator in real life.:)

I wasn't able to catch the drogue with any plane until I watched a video where the guy says it's like 90% mental, and that the key is relaxing your muscles for precision control. It's the death-grip that ruins the process. Didn't make a note of who made the video, but whoever it was, thanks-Keep making them, because you're definitely helping.

I'm relatively new to aerial refueling, but no way is this "the worst throttle in the game". No way. It just takes practice, like everything else. I can't advise you on your view problems, because I've never fueled from an S3 in the Tomcat. I think Track IR would help, not hinder, but I guess that is your call. Here is some advice that was passed on to me. Sweep your wings into Bomb Mode. The real recommendation is for 40 degrees manual sweep, but control of the aircraft is even easier when the wings are swept past 50. Back that far, the automatic operation of the slats and manuever flaps is inhibited, and your trim will be more constant. And since your wings are well aft of where the wings would be if in Auto mode, there isn't going to be any automated movement of them, either.

First off, I would like to say, I haven't had as much fun with a DCS module in a long time! In fact, this might be the best, ever. Absolutely superb. However, I've gotten used to doing things a certain way when it comes to controls, and I really wish to see a more complete set of keybindings available. I've probably missed a few, but these are the ones that I would like to be able to map to home cockpit controls or keyboard commands, especially the first 5: HSD CRS +/- HSD HDG +/- Baro Alt +/- Radar Alt +/- Speed Bug +/- Spoiler overrides Generator switches Air Condition/Air Source Switches Inlet Ramp Controls Engine Mode Select Air Start Hud Trim Hud Brightness VDI Trim Would All of those are just in the front seat, and I haven't spent too much time in the back seat, but I think it would be nice if we could have a complete set of control keybindings there too. I know that you've been adding controls with each update. Keep up the good work, Heatblur!

:beer:

I don't know what Kindergarten you went to, but in my Kindergarten they said "Don't talk to strangers" :)

Unable to switch to Cold Mic or Hot Mic via keybinding. Functions are mappable but do not work.

+1 on hoping that Heatblur adds a bunch more keybinds. There are a couple of modules in DCS (Hornet, for instance) that have keybinds for -everything- and I'd like to see this for F-14 as well.

I guess if that works for you, then it works, but it shouldn't be necessary. I use central position trimmer mode, and trim it with a click, just like I would with a UH-1. You don't have to hold the trim down to temporarily disable the autopilot on the Mi-8 because use of the trim isn't "programming" the autopilot in the same way as it is with Ka-50. The Flight Engineers knobs are what accomplishes that. For about a month now, following the practices of a more experienced pilot, I started flying the Ka-50 with Flight Director ON. For me, this makes the Ka-50 fly more like the Mi-8, specifically in that I don't have to hold the trimmer down while manuevering. The only catch is that when I want to autohover, I click FD mode Off right before hitting the Autohover button, since if the FD is On, you wouldn't be able to Autoturn to target or stuff like that. And then of course, I turn FD back on again when I want to move on. As with anything, Your Mileage May Vary.

I'm loving this plane from the start, but as I'm starting the task of mapping the controls, I notice there are a lot of things that cannot be bound to keys or buttons. For example, I definitely want to see keybindings for Increase/Decrease of things like Altimeter Baro, Heading bugs, Course needles, etc. There are a lot of other things too, with engines, and electrics that simply don't have the ability to bind. I haven't gotten to the back seat yet. Basically, I hope that eventually we can have it be like most of the in-house ED planes, where everything that can be clicked or rotated with the mouse, can also be mapped to a controller or keypress. (I know this is still Open Beta)