Jump to content

Helios -> DCS World 1.5


OzDeaDMeaT
 Share

Recommended Posts

Hi Iku64,

 

My mistake, I thought you had got the radar working also... no probs...

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

  • Replies 119
  • Created
  • Last Reply

Top Posters In This Topic

I have four monitors (3pcs 1920x1200 + 1680x1050) and was trying to run those three monitors with surround. So Windows and Helios was seeing that setup as 2 monitors (1pcs 5760x1200 + 1pcs 1680x1050).

But now I have everything working just fine because I disabled surround and all 4 monitors are separate in Windows setup.

That's exactly how it should be set up... DCS on the main three screens at 5760x1200 and configured in DCS as 'one screen' and Helios on the fourth at 1680x1050 (after monitor reset in Helios). Have you managed to get this working yet?

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Hey SLicker suggestions on Helios on a 1080p monitor how to setup? I'm running 3 30" 2560x1600 monitors and have my fourth 1080p touchscreen for Helios

Hi maestro72x, how's it going... have you figured it out yet... how far have you got with it...there's plenty of info on the forum but I'll try to help if if you're really struggling...

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

  • 2 weeks later...

Guys after trawling through the posts Im starting to see some similarities with my problem. I am running 3 x 1920x1200 screens and a 4th 1280x1024 touch screen. My main three screens are running Nvidia Surround. According to your posts running NV Surround stops Helios from working on the 4th screen (Analog Gages etc.) I also see that people mention running the config as 1 screen?? Do you mean the 1camera.lua?? Can someone post a screen shot of the Lua file they use for 1 screen.

 

If I try to RUN DCS as 4 separate screens it scrunches everything up to the top of the screen making the UI unusable.

 

Any help would be great

Screens.jpg.6cd8e6dc449aadfedf2fe8c00df3de7f.jpg


Edited by IADC
Link to comment
Share on other sites

I run it with 3 seperate screens/viewports + a fourth for Helios and exports, no problems, so it can be done..

I have however seen the scrunched (is that a word? :P ) view in top of the screen, while fiddling around with my monitor config.lua, but why it happens I don't know. I just took a step back, and tried it another way, until it worked. Not much help, I know..

System: Asus z270 A Prime, Intel i7-7700K 4.8GHz, 32GB DDR4, RTX2080, Samsung 500GB 850 EVO SSD.

Valve Index VR, TM Warthog Throttle & Grip, Virpil MongoosT-50CM2 base, TM TPDR Rudders.

OS: Win10 Home

 

 

Link to comment
Share on other sites

IADC,

 

I'll try to help you but time is against me and I don't have time to read this entire thread,

 

Which Helios profile are you trying to get running?

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

I make my own Helios profiles by clipping and pasting from Gadroc's A10C single touch screen. I add the A10 interface and point everything to the right target line and I get the message that DSC A10 is configured.

 

I have done it this way from the start and it has always worked but not with 1.5.

 

I am thinking maybe the Export Lua. file may be the problem. I did use the Captzeen Lua file configured for DCS 1.5 Would using another profile to build my helios profile conflict with Captzeen Export Lua. ?

Link to comment
Share on other sites

IADC,

 

Just a quick check... have you pointed Helios to the correct version of DCS (note the path will be different) - sorry about mentioning this basic error but just want to be sure you've thought of this.

 

If you start DCS (without running the Helios profile), do any of the gauges appear on your touchscreen?

 

If not, what have you got your in-game resolution set to?

 

I have 4 x (1920x1080) screens so mine is set to 7680x1080

 

Apologies in advance, you may already know the lua defines the 'game area' (5760x1080) but the in-game settings in DCS/Options reflect the total screen size of all monitors.

 

Once this is set correctly, you also need to select the appropriate monitor.lua from the drop-down list (but, I suspect you know this).

 

I note you have 3 x (1920x1200) + 1 x (1680x1050) - so maybe you should set your in-game settings to 7440x1200. That is (5760+1680) x 1200 (max depth)

 

My screens are set up as shown in the screenshot in post #105. Would you like to try a copy of my A-10C monitor.lua file?

 

In fact, let me know if you want me to send any of my config files (it's no problem)...

 

You (or others) may be interested to learn that in my previous setup, I had the same screens arranged in Windows to form a 'T' shape instead of side by side (as in post#105). As a result, my in-game setting was 5760x2160 and the .lua was set to 5760x1080.

 

This setup did work fine but I always suspected that I could improve my frame rate by rearranging the monitors so they were side-by-side. It always seemed to me there was some 'waste' either side of the touchscreen, if you get what I mean?

 

Anyway, the change did make a slight difference but nothing significant.

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Please see below

 

IADC,

 

Just a quick check... have you pointed Helios to the correct version of DCS (note the path will be different) - sorry about mentioning this basic error but just want to be sure you've thought of this. X:\Eagle Dynamics\DCS World OpenBeta

If you start DCS (without running the Helios profile), do any of the gauges appear on your touchscreen? No not yet as I don't have any view ports exported yet. Im trying to get just the analog gauges in my helios profile working before I mess with the Monitor.lua

If not, what have you got your in-game resolution set to? My in game res is set to currently 5760x1200 using NVidia Surround (see above post picture) as I have no view ports exported, when I apply the view ports for the MFD's which are the only ones I use then I would set the res to 7680x1200 (3ea 1920x1200) (1ea 1280x1024)

I have 4 x (1920x1080) screens so mine is set to 7680x1080

 

Apologies in advance, you may already know the lua defines the 'game area' (5760x1080) but the in-game settings in DCS/Options reflect the total screen size of all monitors.

 

Once this is set correctly, you also need to select the appropriate monitor.lua from the drop-down list (but, I suspect you know this). Yup got that

 

I note you have 3 x (1920x1200) + 1 x (1680x1050) - so maybe you should set your in-game settings to 7440x1200. That is (5760+1680) x 1200 (max depth)

 

My screens are set up as shown in the screenshot in post #105. Would you like to try a copy of my A-10C monitor.lua file?

 

In fact, let me know if you want me to send any of my config files (it's no problem)...

 

You (or others) may be interested to learn that in my previous setup, I had the same screens arranged in Windows to form a 'T' shape instead of side by side (as in post#105). As a result, my in-game setting was 5760x2160 and the .lua was set to 5760x1080.

 

This setup did work fine but I always suspected that I could improve my frame rate by rearranging the monitors so they were side-by-side. It always seemed to me there was some 'waste' either side of the touchscreen, if you get what I mean?

 

Anyway, the change did make a slight difference but nothing significant.

Link to comment
Share on other sites

I have now my 4 monitors at T-shape but now I also have GTX980Ti (6Gb) GPU so didn't notice big difference at fps to compared to shape where your all monitors are side by side.

 

However at same rig with GTX670 4Gb GPU there was huge difference in negative mean when I tested T-shape.

 

I think that T-shape is slower when you don't have enuff GPU memory because seems that at 7680x2250 resolution DCS takes over 4Gb GPU memory (in my situtation it takes about 4.5Gb)

 

[sIGPIC][/sIGPIC]

HP Z420 | Xeon E5-1650 @3.20GHz/3.70Ghz | 16Gb DDR3-1333 | ZOTAC GTX 980 Ti AMP! | Micron RealSSD C400 256Gb | Sound Blaster Z | TrackIR4 | Thrustmaster HOTAS Warthog| CH Pro pedals | Win 10 Pro 64-bit

 

Link to comment
Share on other sites

Thank you for clearing up those few things. I now have a clearer picture of what you're trying to do. I'm afraid this is something you would be best referring to the master profile builder himself - Capt Zeen. You will find he is a very helpful guy and I'm sure he will be only too pleased to assist you.

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Has anyone come across this yet. When I set up helios on I main screen and exporting to the right screen. The first time everything lined up, next time when I opened the side panels, it had moved the MFCD's up.

This is what it ended up like.

 

MFCDs%20moved%20north.jpg

 

weeb

Windows 7 64 Home Premium, i5 3570K (3.4 @ 4.4GHz), Asus P8Z77-V LX, 16GB dual channel 1600 ram, EVGA Nvidia GTX980ti, 240 GB OCZ SSD, 3 TB Raptor, Thrustmaster Warthog Hotas and Throttle, Saitek Pro Combat Rudder pedals.

Link to comment
Share on other sites

Never had this happen (yet)

That's jinxed it!

I'll check mine and let you know if anything has changed

Have you tried rebooting the computer and trying again?

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Yup, still working OK... do you have any other profiles you can try to see if this may be just a corrupted .lua

Might be an idea to use a backup .lua if you have one?

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Here's a copy of mine - you will notice line 14 is expressed different to yours and if you changed yours to follow the same format it would read 5760/1200

 

A10-C.lua

 

I can't see all the lines in your screenshot but just check the last line (90 in my case) reads:

 

UIMainView = Viewports.Center

 

Make sure the name shown in ' ' (at line 2) is identical to the name of the .lua

 

For example:

 

Nvidia Surrond 2 screen

 

Note the spelling mistake (Surrond)

 

Hope this helps....


Edited by slicker55

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

Yup, still working OK... do you have any other profiles you can try to see if this may be just a corrupted .lua

Might be an idea to use a backup .lua if you have one?

 

Hi m8, thanks for input but I sussed it out. I was following a guide on here purely to test helios, just to see if it was still doing what it was good at. This is not my games machine I'm working on, hence the 2 side by side 1920 X 1080's. The guide was for 1920 x 1080 plus 1980 X 1200 so the position of the viewports was totally irrelevant for my set-up. I had to write my own monitor lua from scratch and whilst doing that I came across a really handy tool. I do not endorse this, I am not connected to this software in any way/shape or form, I just found it incredibly helpful when working out pixel placement. It's virus free and the source code is available for perusal if in doubt.

 

http://www.cthing.com/Meazure.asp

 

weeb :thumbup:

Windows 7 64 Home Premium, i5 3570K (3.4 @ 4.4GHz), Asus P8Z77-V LX, 16GB dual channel 1600 ram, EVGA Nvidia GTX980ti, 240 GB OCZ SSD, 3 TB Raptor, Thrustmaster Warthog Hotas and Throttle, Saitek Pro Combat Rudder pedals.

Link to comment
Share on other sites

Cheers weeb,

 

Glad you got it sussed ... and, hey, thanks for mentioning the measure software. I have downloaded it and will take a look at a more sociable hour!

 

:(

i7-5820K 3.30Ghz | Asus X99-S | Sapphire R290X | R7 240 | 16GB DDR4 PC4 2800MHz | Samsung 850 EVO 500GB SSD (OS) | Samsung 840 EVO 500GB SSD (DCS) | Noctua NH-D14 2011 Cooler | OCZ ZT 750W '80 Plus Bronze' Modular PSU | NZXT Phantom Enthusiast | 3 x IIyama Prolite E2473HDS 24" | 1 x Dell S2240T 21.5" Touch Screen | Windows 10 64-Bit | AMD Eyefinity 5760 x 1080 | TrackIR5 | TM Warthog HOTAS | MFG Crosswind 1771 | Vaicom Pro + VA (Licensed) | Sennheiser Game Zero | Honeycomb Yoke (June 2020)]

Link to comment
Share on other sites

DCS 2.0

 

Ok bit off topic from 1.5, which works well for me, having followed the helpful tips on this thread.

Sooooo DCS 2.0 tried the same method of Inserting export and pointing Helios at the Alpha install. No joy, no gauges or interaction with the sim. Any thoughts or tips lads ??

Link to comment
Share on other sites

Ok bit off topic from 1.5, which works well for me, having followed the helpful tips on this thread.

Sooooo DCS 2.0 tried the same method of Inserting export and pointing Helios at the Alpha install. No joy, no gauges or interaction with the sim. Any thoughts or tips lads ??

 

Open your dcs saved game folder in the 1.5 version and also in another window open the 2.0 beta version copy the scripts folder over into the Alpha version, it did not exist for me. All gauges and buttons (so far) work. No Clock, CDU, or RWR though....

Link to comment
Share on other sites

 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...