Diplocaulus

Fantastic aircraft! I'm really loving it! Thank you! Minor quibble: When I switch to full-screen HUD view the reading from the digital fuel flow gauge from the front cockpit continues to display. Any way to make it go away? Thanks again!

I'm really loving the the NS430. This is a great addition! I have been trying to set up my Saitek X52 Pro to control some features of the NS430 pop-up, in particular the NS430's rotary knobs. Unfortunately, while I can control the knobs from the X52 throttle via its pair of rotary knobs (#32 and 39 on the X52 control panel), the signal from the X52 is too coarse to be useful, i.e., one roll click of the X52's knob = two to three "clicks" of the NS430, making ICAO codes impossible to enter. I also tried mapping the NS430's knobs to the X52's joystick toggles (#9-14 on the X52 control panel), but in that case engaging the X52's toggle causes the NS430's knobs to spin too fast to be useful. Is there any way to tweak the resolution of these inputs between the X52 and NS430? Thanks.

For what it's worth I have the Saitek X52 Pro and it's working fine with the Yak-52.

Never mind. After some poking around I see that the autopilot display has been moved to the kneeboard. Now that I can see what's going on it's not so mysterious. Suggestion to Belsimtek: Please update your manual.

I am trying to implement the Huey autopilot from the pilot's position (yes, I know the autopilot is a "cheat") in a custom free flight mission, however the only keyboard combination that appears to do anything is LWin+A, but it is inconsistent--sometimes it holds my heading, other times it puts me into a hover. The other key combinations--for Atitude Hold, Level Flight, and Orbit, do not appear to do anything except switch the autopilot off if it has already been enabled via LWin+A. Also, I am not seeing the autopilot mode window that the manual shows; how do I display it? I have reviewed the manual but it has little to say about the autopilot. Obviously I'm missing something. Can anybody help? Thanks.

Yep, MSAA was set to 8xQ. Switching it to 16x and restarting DCS World fixed the problem. Now all is well. Thanks! :thumbup:

I just updated the Alpha (Nevada) to version 2.0.5.1648 and now both the interface and game are very dim. It's as though my monitor brightness has been turned down by 75%, but the problem is only with DCS World Alpha. This is not an issue with the latest version of DCS World beta which is looking fine. I ran the DCS World repair tool on the Alpha v2.0.5.1648, but the problem still remains: dim, dull and low contrast. Latest video drivers installed, no DCS World mods or addons (other than skins and missions). It's unplayable like this. Any suggestions? Thanks. **************** SYSTEM SPECS **************** Windows 10 Home 64 bit Build 14393.693 Intel Core i7-5820K Haswell-E 6-Core 4.2 GHz ASUS X99-A Motherboard 32GB (4 x 8GB) 288-Pin DDR4 SDRAM DDR4 2400 (PC4 19200) 850w Power Supply GeForce GTX 780 driver version 378.49 Monitor: Dell UltraSharp 27 QHD U2715H Resolution: 2560x1440 (monitor native) Logitech G602 Wireless Gaming Mouse Logitech G510 USB Wired Gaming Keyboard Logitech G633 Artemis Spectrum Gaming Headset Saitek X52 Pro Flight System (throttle & joystick) Track IR v5 Razer Tartarus Gaming Keypad ***********************************************

Thank you for the info and links ricktoberfest & droopy114!

I'm trying to customize my views (default FOV, snap views) for aircraft in both versions 1.5.3 and 2.0.2, but unfortunately my efforts appear to yield unreliable results. In most cases I'm attempting to modify the *.lua view files directly, which leads me to this topic: What's the difference between View.lua and SnapView.lua in the Saved Games folder? Do settings in one override the other? Related question: What's the difference between the view *.lua files in the Saved Games folder and the main installation folder? Again, do settings in one override the other? Is there a hierarchy of view settings that DCS World scans before applying those settings to the aircraft? If yes, then what's the order of that hierarchy? Or do I need to adjust values concurrently in all view files? I'm comfortable editing the *.lua files directly using Notepad++, but there appear to be some fundamentals to how views work in DCS World that I'm still not understanding. Any help would be appreciated. Thanks.

I can't get snap views to work for the Gazelle in versions 1.5.3 beta nor 2.0.2 beta. What happens for me is when I create a snap view, that snap view then (somehow) automatically becomes the default view. Can't switch it back, can't figure it out. I tried deleting the snap views from SnapView.lua and starting fresh, but no joy. Here's a snippet from SnapView.lua where I assigned a snap view to Num4 (which has now become my default view): SnapViews["SA342M"] = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 65.000000,--FOV hAngle = 0.000000, vAngle = -30.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [2] = {--LWin + Num1 : Snap View 1 viewAngle = 84.000000,--FOV hAngle = 105.000000, vAngle = -8.500000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [3] = {--LWin + Num2 : Snap View 2 viewAngle = 65.000000,--FOV hAngle = 0.000000, vAngle = -45.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [4] = {--LWin + Num3 : Snap View 3 viewAngle = 84.000000,--FOV hAngle = -135.000000, vAngle = -8.500000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [5] = {--LWin + Num4 : Snap View 4 viewAngle = 84.000000,--FOV hAngle = 90.000000, vAngle = -8.500000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [6] = {--LWin + Num5 : Snap View 5 viewAngle = 42.512844,--FOV hAngle = 0.000000, vAngle = -4.478010, x_trans = 0.154018, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [7] = {--LWin + Num6 : Snap View 6 viewAngle = 84.000000,--FOV hAngle = -90.000000, vAngle = -8.500000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [8] = {--LWin + Num7 : Snap View 7 viewAngle = 84.000000,--FOV hAngle = 58.000000, vAngle = 23.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [9] = {--LWin + Num8 : Snap View 8 viewAngle = 84.000000,--FOV hAngle = 0.000000, vAngle = 35.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [10] = {--LWin + Num9 : Snap View 9 viewAngle = 84.000000,--FOV hAngle = -38.000000, vAngle = 25.000000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [11] = {--look at left mirror viewAngle = 84.000000,--FOV hAngle = 45.000000, vAngle = -8.500000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [12] = {--look at right mirror viewAngle = 84.000000,--FOV hAngle = -45.000000, vAngle = -8.500000, x_trans = 0.000000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, }, [13] = {--default view viewAngle = 74.625000,--FOV hAngle = 1.223145, vAngle = -25.390137, x_trans = 0.095000, y_trans = -0.136902, z_trans = -0.145543, rollAngle = 0.000000, }, }, Which leads to a related question: What's the difference between View.lua and SnapViews.lua?

This is my first post regarding this beautiful aircraft and I'm really loving it! Thank you Polychop! :) QUESTION: Is there a way to toggle the controls display that appears in the center of the HUD view (LAlt+F1), that is make it go away when I don't want it? Thanks!

Fact remains that I and apparently others rushed to their shopping carts justifiably thinking that DCS was offering generous terms for what appears to be a fantastic product. I'll get over it, but I'm left feeling mislead by DCS.

Yes, because that's what the e-mail said: "...we are offering 50% off on all DCS World helicopters using bonus points!" I'm disappointed. It's no fun to discover something like that at checkout; feels like bait & switch. :noexpression:

Yep, issue resolved in Open Alpha with version 2.0.1.50747.

Issue resolved in Open Alpha with version 2.0.1.50747.

Saitek X52 Pro.

LOL, Yes indeed, that' why I mentioned it. :) UPDATE: Okay, got all guns blazing! Thanks again everyone for your help and the great videos! :thumbup: Next I'll need to return to the training missions and see if it was just me (as it likely was).

Thanks everyone for the videos. I made another pass at it and still no joy. I've been flying two L-39ZA training missions: L-39ZA, GSh-23 Gun, and L-39ZA, PK-3 Gun Pods. In neither of the training missions am I able to get the guns to shoot. I'll keep trying though.

I can't get the GS-23 Guns to fire either, neither in the training mission nor elsewhere, and while I have Saitek's X-52 Pro I don't know what VJoy Virtual Joystick is. BTW, is there to be had a PDF or graphic guide to arming and firing these guns? I usually need these things spelled out for me. :) Thanks.

Seems like I'm always getting stuck in the mud.

Nice! I've been looking for something that would boost the brightness of DCS World without my having to mess with my monitor settings. Very much appreciated! I successfully performed quick tests of this in both versions 2.0.1.49921 and 1.5.3.50487. I like the easy toggle. Next question of course: Is there an expedient way to tweak the settings? Thanks again.

I'm having issues creating Snap Views in the new L-39ZA from within the cockpit. Using the LWin+NumKey and RAlt+Num0 technique; sometimes the snap view is saved, but more often it's not. My solution is to edit \Saved Games\DCS.openbeta\Config\View\SnapView.lua directly and simply copy the views I created previously for the L-39C to the L-39ZA. I'm working with DCS World version 1.5.3.50487. Thanks.

The Make HTML option for the L-39C and L-39ZA no longer creates a complete HTML listing for the keyboard and joystick bindings. What I get instead are 2kb HTML files (instead of the usual 110kb) with just a few bindings displayed. This is an issue for both version 2.0.1.49921 and 1.5.3.50487. Thanks

The Make HTML option for the F-86F Sim no longer creates a complete HTML listing for the keyboard and joystick bindings. What I get instead are 2kb HTML files (instead of the usual 110kb) with just a few bindings displayed. This is an issue for both version 2.0.1.49921 and 1.5.3.50487. Thanks

I have been configuring Belsimtek's F-86F sim for both Open Beta 1.5 and Open Alpha 2.0. All has been going well except for one problem: In the Open Alpha 2.0 Controls menu, the Make HTML option for the F-86F Sim no longer creates a complete HTML listing for the keyboard and joystick bindings. What I get instead are 2kb HTML files (instead of the usual 110kb) with just 4 bindings displayed. For example, the only contents of \Saved Games\DCS.openbeta\InputLayoutsTxt\F-86F Sim\Keyboard.html are these 4 lines: "RShift - -" A-4 Sight Bombing Altimeter Index Altitude Handle - CCW/Decrease A-4 Sight "RShift - =" A-4 Sight Bombing Altimeter Index Altitude Handle - CW/Increase A-4 Sight "RCtrl - -" A-4 Sight Bombing Altimeter Target Altitude Knob - CCW/Decrease A-4 Sight "RCtrl - =" A-4 Sight Bombing Altimeter Target Altitude Knob - CW/Increase A-4 Sight This appears to only be a problem with Open Alpha 2.0 and the F-86F sim. Identical F-86F sim keyboard and joystick bindings print to HTML fine from Open Beta 1.5. Also, Make HTML works fine for all other Open Alpha 2.0 modules. I ran the Open Alpha 2.0 repair option, but the problem with the F-86F sim Make HTML remains. Not a show stopper, but a strange quirk. Any suggestions? Thanks