Diplocaulus

Much appreciated uboats! :thumbup:

LOL! My MiG does have that balsa wood glider look. ;) I have a few mods running, all installed via (the awesome!) JSGME. They are: Airbrake Beep Devrim_C101 Aviojet EnglishCockpitMod_v0.0c Su-25T English Cockpit B-29 13Mar

I've got a GeForce GTX 780 with 3 GB VRAM, though I don't know what the VRAM usage was when this happened.

I was flying the MiG-15bis in a single user mission I created myself to intercept the beautiful AI B-29 available on this forum. (This is my first attempt at building my own mission and going at the B-29.) As I was at altitude and turning to get an angle on the B-29, suddenly my aircraft stopped responding to inputs and my cockpit turned into a fun house mirror! It became unflyable. Going to an external view I see that my MiG-15 has flattened out, no engine sound, though the rest of the DCS World appears normal. Never seen that before. Maybe I pulled too many Gs? :joystick:

Love it! :thumbup:

That explains a lot. Thanks!

Loaded question.

While I'm very excited by the prospects of DCS World 2 (the video previews are blowing my mind), I'm sticking to what I have--because it's what I have now.

Thank you Charly. :thumbup:

As a general observation after spending several months with the X-52 Pro and DCS World I've learned the following: With the exception of Axis commands, whenever possible Map keyboard commands to the X-52 Pro using Saitek's Mad Catz dedicated configuration editor (rather than mapping commands via X-52 Pro column in DCS's OPTIONS/CONTROLS interface.) You'll thank yourself--repeatedly--later. As others here have suggested, start simple by mapping and then testing some basic commands first (you can't get to second base without passing first). I found it best to build a configuration from the ground up based upon my (ever growing) needs rather than employing some of the highly-detailed pre-configurations available here and elsewhere (too complicated for my tiny brain for now). Create custom X-52 Pro profiles for each module as required. As others have suggested, disable the clutch system and bind useful keyboard commands to it. In my case I didn't move on to using the pinkie switch until I'd maxed out the first level mapping (I haven't even moved on to modes yet, but then when I'm not buzzing around in the Huey I'm still working with WWII and 1950s era aircraft). Regarding the pinkie switch, clicking it while in Saitek's editor tends to make the editor crash (for me at least). Another thing that can make the editor seem wompy is if the throttle's "Precision Slide" isn't centered while editing. I've never been able to get the two rotatory knobs to work in DCS World (though they work fine for X-Plane as prop and fuel mixture controls); I don't use them. While others may tell you different, I find it useful to map gear and flap controls to the keyboard instead of the HOTAS as they are typically used only at the beginning and end of each flight (assuming you don't eject first). Most importantly: Like battle itself, flight sim configurations are highly fluid; I'm tweaking mine just about every day, changing my mind about this and that, and forever trying new techniques and combinations. It's like learning a musical instrument: if you're doing it right, you never stop learning.

Convenience, and even then it's like learning a musical instrument. And how things are mapped is forever an ongoing process, for me at least.

Flight simming is like riding a bicycle--makes me feel like a kid again. :balloon:

I've been air combat simming since Gilman Louie's "Falcon" appeared on the Macintosh. (You do the math.) :smilewink:

Thanks SkateZilla. That makes sense. And if the appropriate CoreMods folder doesn't exist, then I need to create it, e.g., \CoreMods\aircraft\MiG-15bis\Liveries\MiG-15bis. That should fix the missing skins. Still curious as to why some skins need to be installed in CoreMods versus Bazar.

I'm really loving the repaints available for so many of the DCS World modules. The work is fantastic! Question, and I apologize if this has been asked a zillion times before: What's the difference between repaints that go into the CoreMods folder versus those that go into the Bazar folder? I frequently find that the skins destined for CoreMods don't show up in the Mission Editor, regardless of whether I put them in CoreMods or Bazar. Whereas skins specified for Bazar tend to show properly, at least for me. Any info would be helpful. Thanks!

Worth every penny! :thumbup:

There's also not much consistency in what various functions are called from one mod to the next. That said, it would be nice if view and kneeboard functions could be managed across all mods as those appear consistent.

Fantastic guide Charly. Thank you! I vote MiG-21.

I noticed the same thing from the Mustang. Request an azimuth and you get weird, sometimes contradictory vectors. I wasn't sure if this was a bug or approach was trying to vector me into a specific approach pattern.

Thanks Sliver Dragon! :)

"ASM level?" What's that?

I'm wondering if in-flight icing, i.e., carburetor icing, jet inlet icing, wing icing, pitot-static sensor icing, is modeled in any of the ED or licensed third-party aircraft? Coming from a background of general aviation flight sims (MS Flight Simulator, X-Plane), nearly all checklists for example remind the pilot to turn on pitot heat, though I don't see pitot heat referenced much in the DCS World aircraft checklists. I understand that DCS World is first and foremost a sim dedicated to the military applications of aircraft, but alas the extraordinary detail given to their products only makes me hunger for more. :)

I don't know how much of a role radio navigation played during WWII (there was of course Oboe and Gee, but I think that was more about ground operators verbally transmitting vectors to allied aircraft), but it would be awesome if at least some realistic radio features were implemented in ED's upcoming Normandy 1944. I don't know, did WWII fighter pilots rely mostly upon dead reckoning?

The Kneeboard current position mark point command does indeed work for me, but I still rely upon the Theater Map to see where I am, though I find it a little awkward to use, especially while flying, and the NATO aircraft symbol unfortunately doesn't display the orientation (NSEW) of your aircraft. I come to DCS World with much general aviation sim experience via Microsoft Flight Simulator, and Now X-Plane 10. In these largely GA sims navigation is everything, especially via radio beacons (VORs, DMEs, NDBs, though TACANs are not modeled in either). On the other hand, navigation in DCS World is a harder nut to crack, for me at least. As I'm still just a newbie on the learning curve, it appears that in some cases, e.g., the F-86 Sabre, navigation and ATC frequencies must be pre-programmed via the Mission Editor, while in other modules, e.g., the P-51D Mustang, radio navigation isn't modeled at all. I'm presuming this lack of navigation fidelity in DCS World is due to it being largely a military flight sim with a focus on planes as they relate to combat and less so navigation, while sims like X-Plane are primarily concerned with modeling general aviation and less so military applications. Also, when it comes to DCS World, I'm more interested (at this time at least) in the vintage aircraft, as I've already spent a lot of years flying Gilman Louie's F-16 and MiG-29 in the Falcon series from the 90s.

Thanks for the info.