funkster Posted February 10, 2014 Posted February 10, 2014 :cry:Hi I have just returned from a bit of a break and updated to 1.2.7. however I cant get helios to work (gauges to update etc). I have gone through the forum and found some post such as this http://forums.eagle.ru/showthread.php?t=102034 but it is a bit confusing. For starters I don't have the 'scripts' folders mentioned in my saved games\DCS folder?? This is actually under my main DCS world install?? Can anyone help and provide me with a step by step as to what I need to do to get Helios up and running in this new version please? Any help much appreciated.
SkateZilla Posted February 10, 2014 Posted February 10, 2014 Make a /Scripts/ Folder in you Saved Games/DCS/ Folder. Place the Files in it Open Helios, Setup/Adjust a Pre-Made profile or make your own. (Profiles are downloaded separate, and must be opened and reset to your monitor config before using) Open Monitor Config, Place MFCDs, RWR, anything else (Clock, CounterMeasures, etc) Constrain your Center Viewport to your Mainscreen (or Screens), Set Aspect Ratio of Center viewport Constrain UI to Your Center Viewport Save Profile Monitor Profile, Open Helios, Select Pre-made profile or your own, Click Start Open DCS, Select Monitor Profile, Set Resolution to the res of all the displays (including the Helios screen). Press OK, let GUI Re-load, Start Mission, Enjoy. Anything other than the MFCDs need to have modified scripts (will look for a guide) Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
SkateZilla Posted February 10, 2014 Posted February 10, 2014 I used this Package from PeterP to enable Viewports, http://forums.eagle.ru/showpost.php?p=1541311&postcount=68 Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
Boltz Posted February 10, 2014 Posted February 10, 2014 Helios worked no problem for me with 1.2.7 and I didn't have to create any folders. Remember that when you add a new interface and click to set it up Helios will create the Scripts folder and export.lua in you Saved Games folder. A-10C Cockpit Build Thread My YouTube Channel
jay43 Posted February 10, 2014 Posted February 10, 2014 Also if DCS is running with admin rights so to does Helios need these rights or thats what i found, i could flick switches and dials which would work in Helios but they would not send the inputs to DCS until i gave it admin rights or UAC whatever you want to call it. Eagles may soar high but weasel's don't get sucked into jet engines. System Spec. Monitors: Samsung 570DX & Rift CV1 Mobo: MSI Godlike gaming X-99A CPU: Intel i7 5930K @ 3.50Ghz RAM: 32gb GPU: EVGA Nvidia GTX 980Ti VR Ready Cooling: Predator 360 Power Supply: OCZ ZX Series 80 Plus Gold Drives: Samsung SSD's 1tb, 500g plus others with OS Win10 64 bit
funkster Posted February 10, 2014 Author Posted February 10, 2014 Hey thanks guys especially Skatezilla. I really appreciate the time you took to reply. I will give it a go tomorrow and report back. I already have my mfd working as I use separate lilliput monitors/ cougar MFD setup but Wil attempt to sort the other viewpoints etc. I was using the loz2.1 profile but reading through posts it seems the radios bindings are no longer working? Will have to see or use gadrocs.
SkateZilla Posted February 10, 2014 Posted February 10, 2014 (edited) clicking and flicking switches not sending to DCS are because there's not Export.LUA in the /Saved Games/DCS/Scripts Folder. The Radio Bindings are linked, but they jump all over the place when trying to use them. I'm Using LozSM2.1 here Edited February 10, 2014 by SkateZilla Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
jay43 Posted February 11, 2014 Posted February 11, 2014 clicking and flicking switches not sending to DCS are because there's not Export.LUA in the /Saved Games/DCS/Scripts Folder. The Radio Bindings are linked, but they jump all over the place when trying to use them. I'm Using LozSM2.1 here Really well i still don't have the export lua in saved games, my understanding of that is that its needed to export things such as the mfcd's and radios from the A10 and display their output to the monitor running helios. I am not flying the A10 only the Huey and those instruments can't be exported yet. Sp for me running it with UAC gives me control simple. Eagles may soar high but weasel's don't get sucked into jet engines. System Spec. Monitors: Samsung 570DX & Rift CV1 Mobo: MSI Godlike gaming X-99A CPU: Intel i7 5930K @ 3.50Ghz RAM: 32gb GPU: EVGA Nvidia GTX 980Ti VR Ready Cooling: Predator 360 Power Supply: OCZ ZX Series 80 Plus Gold Drives: Samsung SSD's 1tb, 500g plus others with OS Win10 64 bit
funkster Posted February 11, 2014 Author Posted February 11, 2014 Hey Thanks Skate - Got Helios working after a few mins.:thumbup: For the benefit of anyone having trouble post today. (I haven't included full paths but you should get the idea) Basically had to manually create the 'Saved Games\DCS\Scripts' as Skatezilla said. I don't think this was clear in previous posts. I then ran the Helios profile editor, opened my Loz2.1 profile, reset monitors then pointed. Selected the DCS A10 interface and pointed it to 'Program files\eagle dynamics\DCS World' and clicked setup. I then had to copy the export.lua file from 'Program files\eagle dynamics\DCS World\config\export\' folder and paste it into the newly created (step 1) 'Scripts' folder. Thanks again for help guys. I will now need to sort out my viewports.
jay43 Posted February 11, 2014 Posted February 11, 2014 Well glad you got it working funkster took me a few days to find my solution. I have just tried the export lua file and disabled UAC and it stopped working for me followed Skates instructions but for some reason still scratching my head that method just does not work my end. So took out the export lua file and put it back to how it was "if it ain't broke don't fix it" should be a DCS motto i think. Eagles may soar high but weasel's don't get sucked into jet engines. System Spec. Monitors: Samsung 570DX & Rift CV1 Mobo: MSI Godlike gaming X-99A CPU: Intel i7 5930K @ 3.50Ghz RAM: 32gb GPU: EVGA Nvidia GTX 980Ti VR Ready Cooling: Predator 360 Power Supply: OCZ ZX Series 80 Plus Gold Drives: Samsung SSD's 1tb, 500g plus others with OS Win10 64 bit
doveman Posted February 11, 2014 Posted February 11, 2014 Hey Thanks Skate - Got Helios working after a few mins.:thumbup: For the benefit of anyone having trouble post today. (I haven't included full paths but you should get the idea) Basically had to manually create the 'Saved Games\DCS\Scripts' as Skatezilla said. I don't think this was clear in previous posts. I then ran the Helios profile editor, opened my Loz2.1 profile, reset monitors then pointed. Selected the DCS A10 interface and pointed it to 'Program files\eagle dynamics\DCS World' and clicked setup. I then had to copy the export.lua file from 'Program files\eagle dynamics\DCS World\config\export\' folder and paste it into the newly created (step 1) 'Scripts' folder. Thanks again for help guys. I will now need to sort out my viewports. Thanks but your instructions don't quite seem to make sense to me, as after I load a profile and reset the monitors, there's no way for me to select any interface or point it anywhere and click Setup. As far as I can tell, the appropriate interface is already enabled (A-10C, KA-50) when I load a profile. Anyway, I'm having trouble getting my KA-50 Shkval to move to the 2nd monitor. I tried several variants on "Shkval" in my monitorsetup.lua as you can see: _ = function(p) return p; end; name = _('spikeHelios-1.1'); Description = 'Two monitor configuration'; Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1200; viewDx = 0; viewDy = 0; aspect = 1.6; } } LEFT_MFCD = { x = 1920; y = 0; width = 921; height = 730; } RIGHT_MFCD = { x = 1920+1272; y = 0; width = 648; height = 812; } UV26 = { x = 1920+1030; y = 610; width = 120; height = 60; } PVI = { x = 1920+15; y = 726; width = 255; height = 90; } EKRAN = { x = 1920+1745; y = 955; width = 95; height = 57; } ED_KA50_ABRIS = { x = 3197; y = -1; width = 644; height = 817; } ED_KA50_SHKVAL = { x = 1920; y = 0; width = 921; height = 730; } SHKVAL = { x = 1920; y = 0; width = 921; height = 730; } ED_KA50_Ekran = { x = 3649; y = 867; width = 124; height = 158; } ED_KA50_PVI = { x = 1985; y = 725; width = 194; height = 84; } ED_KA50_UV26 = { x = 2933; y = 613; width = 160; height = 62; } UIMainView = Viewports.Center and the attached export.lua I downloaded, which is supposedly a combined A-10C, KA-50, FC3 one, in Saved Games/DCS/Scripts/. EMC obviously installs it's various files in the game install folder when I first run it as well, which I can only presume are correct. The Abris at least is moved to the correct position on the second monitor, although strangely it's booted up and ready from the start, whilst the in cockpit one still shows as off/blank! The Shvkal is stuck in the upper left corner of my main monitor though, whatever I try.Export.lua Main rig: i5-4670k @4.4Ghz, Asus Z97-A, Scythe Kotetsu HSF, 32GB Kingston Savage 2400Mhz DDR3, 1070ti, Win 10 x64, Samsung Evo 256GB SSD (OS & Data), OCZ 480GB SSD (Games), WD 2TB and WD 3TB HDDs, 1920x1200 Dell U2412M, 1920x1080 Dell P2314T touchscreen
Recommended Posts