Loophole

I haven't investigated the P-51, but it ought to be possible. So should FC3, but I have not had any success with that; not sure if the problem is in the Exports or with Helios.

You might be interested in this post: http://forums.eagle.ru/showthread.php?p=1602807#post1602807

Not sure what the problem might be - but if you use Helios to set up the Export.lua that will overwrite my customised version. Are you sure you copied it into the correct location?

I also encountered this problem with 1.2.2 and my TrackIR. I tried resetting the snapviews to the defaults (I had customised a couple of views for the A-10 using RALT+NUM0), but that had no effect. I can temporarily fixed the problem by putting aside my TrackIR, using the keyboard to adjust the head position and using RALT+NUM0 to save the corrected position for the NUM5 snapview - but DCSWorld does not seem to be saving that view - even though the relevant view.lua settings have been adjusted - so I have to re-do the fix every time I enter a mission.

lnr212, I think the Export.lua will have to be enhanced in order to get gauges working for the P-51 and other aircraft; I can see how the Export works, but have not yet found out how to determine the new aircraft-specific parameters for the P-51 and others. Not even sure if the older-style 'FC' aircraft support that sort of export at all. It is on my 'to do' list, though.

I have posted a combined A-10 and Ka-50 Export.lua file for Helios, if that is of any assistance. See this post: http://forums.eagle.ru/showthread.php?t=97222

I love the Helios software - it is really great, but I was a little frustrated that I could not easily switch from flying the A-10 to the Ka-50. The problem is the Export.lua file, which exports different data for each aircraft. I decided to have a crack at addressing the problem, and hacked together a combined A-10/Ka-50/FC3 Export.lua file based on Gadroc's individual Export files. It's not the most elegant LUA code in the world, but it seems to work OK. I have attached a copy for anyone who would like to use it. It currently handles A-10C, Ka-50, and the Flaming Cliffs 3 aircraft. It should be possible to extend it to handle the other high-fidelity aircraft, once I get around to it. If anyone has Export files for other DCS aircraft, I'm happy to take those and merge them into the logic. I hope this is of use to some of you! Revision History Updated 27/7/2013 to add FC3 support Updated 06/01/2014 with FC3 AOA fixed, plus tidier and more comments Updated 28/07/2014 with fix for F-86F-related crash Updated 7/08/2014 previous fix broke the A-10C, now fixed Updated 20/08/2014 fixed some logic issues that crashed the script when changing aircraft during a mission Updated 11/09/2014 Re-enabled HSI export for FC3 aircraft; now seems to be working. Updated 24/09/2014 Added some improved HSI logic from Capt Zeen (thanks), and cleaned up code a little. Installation Drop the Export.lua file into <your user folder>\Saved Games\DCS\Scripts Export.zip

The other problem with co-existance of Warthog and BlackShark for Helios is the Exports.lua file, which is different in each case. I've developed a combined Exports.lua that allows both the A-10 and the Ka-50 exports with the one file - I'll start a new thread with a copy of the file, for anyone who needs it.

OK, looks like I managed to fix the problem for my installation. Not sure which step was the critical one, but this is what I did: Uninstalled DCS World Reinstalled DCS World from the 1.2.1 download. Bypassed the updater, and ran Launcher.exe directly. - Tried Instant Action with Su-25. -- Did online authorization step -- Worked OK. Installed A-10 module from 1.2.1 download - Tried Instant Action with A-10. -- Did online authorization step -- Worked OK. Installed Ka-50, P-51 and CA modules from 1.2.1 download - Tried Instant Action with Ka-50. -- Did online authorization step for Ka-50, P-51 and CA -- Worked OK. Ran DCS_Updater.exe; downloaded and installed update - Tried Instant Action with A-10, and with Ka-50. - Worked OK! So, it looks like it either doesn't like installing over the top of a pre-existing installation, or it wants the 1.2.1 DCS World to have been run at least once before applying the patch? At least it works now!

I and another friend are also getting exactly the same problem - as soon as you enter a mission, the aircraft explodes! This happened after installing 1.2.1 and it then auto-updating. Major problem, as it makes the whole sim unusable. I have not seen any 1.2.1 upgrade work yet!

I haven't found any documentation yet (though I haven't looked very hard), but I am guessing the view you get when you hit "B" while in 1st-person mode is the "Binocular" view. If so, it has a problem when you have multiple monitors that are NOT all dedicated to the 3D view. The "Binocular" view (like the F10 map view) renders across ALL monitors, rather than in the designated 3D world viewport. This makes it almost unusable if you have a second monitor that is a touch-screen running something like the (awesome) Helios program, or simply have it dedidicated to displaying instruments. It can also be a severe problem if there are areas of the desktop that don't show on any monitor, but the view (Binocular or map) renders GUI elements there. For example, my desktop is a wide "T" shape (3840x1024 triplehead above a 1920x1080 touchscreen). Anything rendered in the lower left or right corners in F10 or Binocular view would never be visible or accessible to me. As touch-screens are becoming cheaper and more readily available, this sort of thing is going to become more prevalent - particularly amongst a crowd like the dedicated DCS fans. Much like TrackIR and TripleHead monitors, a touch-screen for control panels is going to be a quite common configuration - so it would be good if it could be accomodated from the start. If you need some screenshots to clarify the issue, let me know and I will provide some. Thanks!

My vote for addressing this issue! SoftTH isn't an option for me (I have a "Hard" TH :-). I add my vote (for what it is worth) to addressing this issue. It would just need the ability to direct the F10 rendering to a named viewport, like the other instruments and the 3D world view. Applies to all the DCS modules, of course. I can only hope... Thanks!

Simplified instrument LUA changes Hi everyone. I went through the process of implementing Helios for DCS:A-10 on my touchscreen, using Loz's Helios profile as the basis. All the information proved to be quite straight forward to follow, but I found that the scripting changes for the instrument exports seemed rather complex and inconsistent. After analysing it, I came up with the following, which seems to work in all the cases I have tried (CMSC, CMSP, ALR69V, CLOCK, UHF status, UHF preset & UHF repeater). In each case, in the XXX_init.lua script (under Scripts\Aircrafts\A-10C\Cockpit\XXX\indicator), I add the following lines just after the last "dofile" command at the start of the script: --- MB customisation: --- dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") render_target_always = false purposes = {render_purpose.GENERAL,render_purpose.HUD_ONLY_VIEW} try_find_assigned_viewport("AN_ALR69V_SCREEN") --- end customisation --- Of course, in each case the argument specified to "try_find_assigned_viewport" is changed to the appropriate viewport set in your MonitorLayout for that instrument. I then just check the rest of the script for any other lines assigning a value to "purposes", and comment them out (put "---" at the start of the line). And that seems to be it - all seems to work nicely (at least, for my setup - no guarantees!)

I've tried to document what has been discovered about snap views in the DCS Wiki: see http://en.wiki.eagle.ru/wiki/Snap_views

Small graphical glitch I noticed in a mission I picked at random: The shadow on the moon, when it is visible in daytime, does not match the direction of the sun. Unluckily, I am not sure what the time of day was, or even which mission I was in at the time, but the sun was overhead, and the moon was about 30 degrees up. The terminator on the moon was vertical, with the sunlit side to the left.

It has basicly the same multi-monitor capabilities as DCS Black Shark, so it supports triplehead and similar setups. The only limitation is that in fullscreen it always runs on the primary monitor - there does not appear to be any way to direct it to a secondary monitor unless you run it windowed.

Hi. I just installed Flaming Cliffs 2 - thanks for the good work! However, when I click on "Training" in the main menu and go to the Training screen, there are no training options listed. If I click on Download I get a browser to the Lock On website, with training instructions and YouTube videos, but nowhere can I find any training missions to download and populate my lonely Training page! In the normal Missions list there seems to be a few training missions, but shouldn't there be a set of missions to match each of the sections in the online training course? And shouldn't they appear listed in the Training menu? I am using Google Chrome as my browser. My system is Windows 7 x64. Its no big disaster for me, but newcomers to the simulation might find it a problem!