slicker55

Thanks guys - more food for thought - appreciated.

ozTRipwiRE, Don't worry mate... just take your time and read Capt Zeen's instructions carefully. I installed this profile last night and it's straight forward enough (not complicated)... Relax! The files you need to be concerned with are the Export.lua and Default.lua - for each of these, Capt Zeen has provided two specific versions, one for DCS 1.2 and the other for DCS 1.5. When you upgrade DCS from 1.2 to 1.5, you will have a completely new and independent installation for DCS 1.5. This is where you should use the specific files mentioned above and copy/paste them into the correct location inside your DCS 1.5 folder. If you're sticking with DCS 1.2 then use those designed for that version and simple disregard the others. Hope you're OK with this advice - any problems, shout up!

I have followed these links a few times but have yet to find a working instrument profile for the UH-1H.

Have you managed to find an export.lua for UH-1H instruments ... I've recently been looking around but not had any joy yet.

Could tell any difference but maybe it will be more obvious when I try it on my rig especially through headphones?

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! :(

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....

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?

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?

Hi DaWa, wanted to say thanks for preparing and sharing this great reference material... did you ever get round to making one for the landing procedure. If not, can you or anyone else for that matter recommend a good one?

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.

Nice to hear from you.. thanks - appreciated

@Esac_mirmidon, Ref. my last, please disregard (I have sorted it out now)

Appreciate you made this offer a long time ago but if you're still willing, I'm all ears! :)

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.

Guys, Do yourselves a favour, CANCEL the download and you will be offered an alternative download via FTP... :)

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?

Finally got done 2.5 hours later... then decided to purchase a new module... downloaded in seconds at 6.5MB/s (money talks) hahahahahah!

Patiently waited for 2 hours 20 mins and now the 'cleaning up....' progress bar is frozen at 10% and says DCS Updater (Not Responding)

Update: 37 minutes in... 906.9 of 1065.2 MBytes Peers: 197, Up: 216.8KB/s, Down: 85.1KB/s

Hey Ricoo1, Look at it like this... we're two of only 198 people in the whole wide world doing exactly the same thing right now! ;)

Same as others have mentioned... came up to have an hours flying before hitting the sack and have been stuck here twiddling my thumbs whilst watching the transfer rate fluctuate - currently at it's best so far - Peers: 184, Up: 264.0 KB/s, Down: 1.5MB/s :(

can anyone 'throw any light' on when this will be fixed? :)

Hi vincent_dimicco, Further to my earlier post, I owe you an apology - I was hasty in concluding that your reg hack had not worked. As you may recall, I reported that whilst your method had resolved the 'nipple' slew issue, it had stopped my pedals from working. I thought this might be because they were using the same axis's as your fix calls for but Last night, I decided to give it another try and to my total surprise, it worked this time. I don't know what I did wrong the first time - I must have failed to follow your instructions precisely. I'll let you know if I experience any conflicts. Thanks for discovering a great solution @vincent_dimicco,

Hi Capt Zeen, I'm so glad I mentioned this now and I am quite confident you will come up with a solution - fingers crossed! :)