Diplocaulus

How do you tune in NDBs or any homing beacons from the Mustang? The manual doesn't seem to cover this very well, and no mention of NDBs. Thanks.

Thanks! I'll give it a try.

I'm still a DCS World noob working to get up to speed with these fantastic products and one thing I haven't been able to figure is what the Kneeboard current position mark point command does. Can anybody help? Thanks.

Thanks!

Is there a pitot heat switch on the MiG-15bis? Does it need one? (I haven't had any airspeed indicator issues yet.) Just curious. Thanks.

When flying a mission I'd love to be able to open the Theater Map and center it on my aircraft with one or two HOTAS or keyboard clicks. Unfortunately, while F10 opens the map, the only other keyboard option I'm aware of is Alt+F10 which both centers the map on my aircraft and zooms way in on it. The zooming part is unhelpful as it zooms in so close it eliminates the useful context of the rest of the map. Keyboard zoom controls don't seem to work with the Theater Map view, so I can't zoom out via the keyboard. Any way I can better manage the Theater Map options without having to mouse over to them and click (inconvenient during flight)? Thanks.

It's tricky at first. What works for me (most times) is hold the rudder in the direction you wish to turn and then pump the brakes in order to get the plane to respond as desired. With the Sabre you simply hold down the S key and manipulate the rudder. With the prop planes it's L/R differential braking. The MiG-15bis demands a little more coordination, at least for me.

Thanks for the suggestion, ivo. Unfortunately I've already mapped num5 to the kneeboard. May I ask what you have num5 mapped to? I did try mapping num5 to Center Camera View, but still no joy. Again, Center Camera View is what works for all the other modules I have installed; the MiG-15bis is the only module where this doesn't work (even though the the MiG-15bis' default mapping for Center Camera View is RShift+num5). UPDATE: I got it to work by mapping RShift+num5 to View Center. :) And I got the HUD view to work by mapping to "F1 HUD Only View Switch" :thumbup:

I'm experiencing an intermittent issue with the MiG-15bis. When I select and start a MiG-15bis mission from the main DSC World interface, the interface disappears and DCS.exe executes, but instead of the loading screen I'm either returned to the desktop or a black screen appears, but nothing else happens, no matter how long I wait. If I then start Windows Task Manager (CTRL+ALT+DEL), I can see DCS.exe running in the applications window, but again no other visible sign that it's running. If I then shut DCS.exe down from the task manager, then DCS.exe disappears from the Task Manager but then my screen displays the DCS World end of mission summary for the MiG-15bis. I have Belsimtek's other beautiful modules (F-86, UH-1H Huey, & Mi-8MTV2) and they all work just fine. This issue seems peculiar to the MiG-15bis. I ran the DCS World repair feature twice, but the issue remains. Any suggestions? Thanks. UPDATE: Okay, I'd delete this thread if I could because I can no longer reproduce the problem. Belsimtek's MiG-15bis is one sweet ride! :thumbup: ******************** SYSTEM SPECS ******************** Windows 7 Home Premium SP1 64bit Intel Core i7-960 Bloomfield 3.2GHz GeForce GTX 780 v347.09 Primary monitor: Dell UltraSharp 27 QHD U2715H 2560x1440 Secondary monitor: NEC 90GX2 1280X1024 12GB (3 x 4GB) 240-Pin DDR3 SDRAM 1600 RAM Realtek High Definition Audio. 750w Power Supply G602 Logitech Wireless Gaming Mouse Logitech G510 USB Wired Gaming Keyboard Saitek X52 Pro Flight System HOTAS (throttle & joystick) ******************************************************

I can't get the Center Camera View (RShift+Num5) command to work. Panning around the cockpit works fine, but neither a RShift+Num5 keyboard press nor assigning that option to a joystick function results in the camera re-centering. Also, is there a "HUD view", i.e., a view sans cockpit? I use this option regularly with other modules but can't find it in the MiG 15bis. And I have Belsimtek's other beautiful modules (F-86, UH-1H Huey, & Mi-8MTV2) and they all work just fine. This issue seems peculiar to the MiG-15bis. Thanks.

Thank you for your reply. Nothing assigned to the "Engine Stop" axis, but after shutting down DCS World entirely and restarting the mission the autostart worked fine. Not sure what happened, prior to the mission I went into the mission editor and changed the season and time of day.

I can't get it started either. After several tries with the manual procedure I hit LWin+Home to autostart, but at the end of the auto start process it reports "Engine RPM Failure." I reloaded the mission several times and tried again, but I get the same result with the autostart: ENGINE RPM FAILURE AUTOSTART STOPPED

That works! Thanks! :)

For my DCS World aircraft I use Enable Exploration Mode to allow me to mouse view around the cockpit for switches etc. Unfortunately I can't find this option in the MiG-21 settings. Did I miss it? Or is there another way to enable this? Thanks.

Thanks. I probably messed something up when I ALT-Tab'd out of the sim.

LOL! That explains a lot. Thanks! :doh:

No screenshot. I was hoping at the end of the mission there would be a mission summary that would give me some clue, but there was none, but maybe that's because this is a training mission? FYI, when I first tuned the TACAN as instructed (to 44x I think it was) it showed the distance to be 6 miles. I didn't get the strange mileage until I tuned the TACAN and VOR to Tbilisi (as instructed). I should note that the altitude indicator and VSI didn't freeze until after I ALT+TAB'd out of the game to make a quick edit to my Saitek X52 Pro HOTAS profile via the Saitek editor.

I just flew the navigation training mission. Nice work uboats! Much appreciated! :) However, once the training part was over and I began flying the mission, I experienced some strange things. Firstly, when I tuned the TACAN to Tbilisi, the HSI showed the distance to be about 980 miles (from Kutaisi). As I flew toward Tbilisi at about 200 KIAS the "miles" clicked down like I was flying mach 3. It did this all the way to Tbilisi. Did I somehow change the distance units? A map shows Kutaisi and Tbilisi to be about 110 miles apart. Secondly, as I was climbing past 18,000 the altimeter and VSI suddenly froze, the VSI at zero fpm, and stayed frozen for the rest of the flight. As the air speed indicator continued working I was able to continue my flight and land at Tbilisi just fine. Was a failure programmed into the mission? Thanks.

You really have to be prepared to power up and do a go-around as soon as something doesn't look right.

Thanks!

Does DCS World automatically update aircraft on the client installation as updated versions are released? I've always wondered this. If yes, does this also include aircraft from licensed third party projects like Leatherneck Simulations and AvioDev? Thanks.

This works for me: - Engine governor (prop rpm) manual, set to 12:00. - Trim full nose down (+2) - Tail wheel locked. - Full right rudder and then throttle. Ease off right rudder as soon as plane starts to move right. - Throttle full, hand on joystick (pay attention and pray) - It leaps into the air fairly quickly. Watch out for a sudden roll. - Wheels up, and Engine governor (prop rpm) to automatic (otherwise the engine will die)

Yep, throwing the Governor Automation to manual right after takeoff will kill the engine, but at least the 109 glides well enough for a safe belly landing. :)

Thanks everyone. I'll give it a try. UPDATE: Yep! Works like a charm. :thumbup:

It's annoying, but I assume it's by design to model that era's technology.