slicker55

There's your answer then...!

Hi Maestro, Sorry, I can't offer any help in relation to your multi-gpu setup but I think I've read somewhere that DCS doesn't handle SLI and Crossfire setup's too well. Please don't take this as read, this may not be true. I'm feeling for you mate - I've had my fair share of problems too - some very early mornings recently. This stuff really pushes your patience to the limit (and sometimes beyond). Everything is working fine one minute and then suddenly, something inexplicably goes wrong and before you know it, you're trouble-shooting again. It's all so time consuming, often at the expense of other things and of course leads to spending more time fixing than flying. The only thing which keeps me going is my passion for the hobby and grit determination. There has been many occasions when I've felt like dumping the whole lot but of course, this is short lived and just borne out of sheer frustration. Hang on in there, someone will come along soon - you'll get it right. It might be helpful if you provide details of your rig (see my signature)... I appreciate you're using multi-gpu's which suggests you have a high-end system but I'm just wondering whether your's is an example of a system which is bottlenecked? Alternatively, (and, in my opinion, more likely) it may just be that DCS cannot fully utilise your gpu set-up? This is just speculation on my part but nonetheless, something I find very interesting - Have you previously had your system running DCS at much higher frame rates? (Here, some comparative values might also be helpful). If so, we can eliminate the hardware and move on to the question of tuning DCS itself. As far as I know and, at the risk of stating the obvious, it is as simple as this... the more eye-candly and filtering you have 'ticked' the more processing power you need - low frame rates would tell me your settings are too high but of course, if your system has run better in the past with the same settings, then something else is the culprit.... ummmmm... .

thdman1511, Just to say thanks for sharing this doc... very useful for future reference so I just grabbed a copy :)

Well, I must say this has turned out to be a very honest poll. When I was the first to say 'None', I really didn't expect so many people to say the same!

Sorry if this has already been covered but have you checked to make sure you have added the dcs a-10c interface in the helios profile editor and checked that the install path points to the correct installation (C:\Program Files\Eagle Dynamics\DCS World OpenBeta). If you've done it right, look in the Helios profile editor, DCS A 10C tab, at the bottom of the A-10C Setup panel and it should say 'Your DCS A-10C configuration is up to date'.

Maestro72x, Those lua's are required to get all the digital stuff working. You also need the latest Export.lua for DCS 1.5 which is available here: http://www.captzeen.com/helios/downloads.asp and this one goes here: C:\Users\your user name\Saved Games\DCS.openbeta\Scripts\ Here's a copy of the file for you: . Export.lua

Hi Maestro72, I said I'd be back to offer some help if I can - this may be difficult because I'm not sure what stage of the installation you're at. If you have followed the advice offered by others so far, you may just need to ensure you have copied and pasted the specific Instrument Init Lua's (included in LOZ A-10C V2.1) to the correct folders on your computer. Suggest you backup the originals before overwriting, just for peace of mind and as a fall-back. Here's a list of where these files need to be placed 1. AN_ALR69V_init.lua C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\AN_ALR69V\indicator 2. CMSC_init.lua C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\CMSC\ 3. CMSP_init.lua C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\CMSP\indicator\ 4. DIGIT_CLK_init.lua C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\DigitalClock\Indicator\ 5. freq_status_init.lua 6. preset_channel_init.lua 7. repeater_init.lua C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C\Cockpit\Scripts\UHF_Radio\indicator\ Here's a link to download LOZ A-10C V2.1 http://www.gadrocsworkshop.com/sites/all/modules/pubdlcnt/pubdlcnt.php?file=http://www.gadrocsworkshop.com/sites/default/files/downloads/Loz%20SM%20v2.1.rar&nid=9 Look forward to hearing how you get on... .

Hi, I tried your Reg hack method (adding axis #6 and #7 as recommended) which did resolve the 'slew' issue (works great) but it stopped my combat pedals from working! I now realise the pedals utilise axis # 6 and #7 so this makes sense. It looks like I will have to 'lose' two axis's from somewhere in order to retry this hack. Going to see if I can track down the stick 'twist' axis (don't need these as I have pedals) and give it another try.

Hi Maestro72x, Have you figured it out yet... I saw your post earlier but wasn't able to help as I wasn't at home. Hope you've got it sorted but if not shout up :)

Hi Guys, I'm learning to set up and use the radio's in A-10C. My newbie errors such as the frequency being inputted incorrectly or the wrong preset being selected goes unnoticed until trying to use a given radio system. Is there a 'Test Radio' option anywhere or have I just had a bright idea? If not, maybe this could be included in the menu system? .

Thanks for this information. I'm trying to ensure my reference material is correct before attempting to test my understanding of the radio's in the A-10C. According to the chart I'm using, Kutaisi ILS is RWY 08-109.8 but other reference material shows this as RWY 08-109.75 Which one is correct?

Where can I get an up-to-date list of radio frequencies for use with DCSW 1.5 and A-10C ?

Several months ago I felt quite reassured that something from Saitek was imminent. This was after establishing contact with someone 'in-the-know at one of their offices. However, months on and we're still trying to find workarounds for what is essentially poor customer support.

No probs - just wondered...

bouncerj21, Oh, that's good news - not too painful I hope. Out of interest, did you try RightStuff's posts (#50 and #52) before deciding to reinstall the OS? That's a bit of a naughty one (Windows 10 Restore Points) don't you think?

@bouncerj21 Hi mate,have you fixed it yet?

This is very interesting - were you logged into Windows 10 as an 'administrator' and running Helios 'as administrator' when the fault developed?

I know, lets ignore everything we've just said... you try A-10C next week and I'll try Ka-50.... :) Only jokin... hahahahahah

Thanks for taking the time to forward this suggestion - appreciated. I will read with interest but when it comes to editing the registration you're on dodgy territory (unless you know what you're doing)

I've tried that but couldn't get mode 2 or 3 to work with the beta software. I'm using HUD, Windows 10 beta version and I think I may have read (possibly on the update notes) that modes are not supported yet. In my opinion, it's time Saitek got their backsides in gear and released a full working version for Windows 10.

Oh shit.. that's bad news... well, it was for me mate.. I tried everything I could think of to get that thing running again but nothing seemed to work. I tried uninstalling it and the reinstalling it to a custom path thinking that might trick it but that didn't work. I really don't know what caused it to stop working... it was fine one minute and then booooom! I realised I would have to bite the bullet and use windows restore but then discovered something I didn't know. For a long time now, I've been regularly creating restore points before making any significant updates to my system but I didn't realise that my settings (by default) was only keeping the last restore point created... yeah... that's the one... the one I created before trying to get Helios working again... yeah, you're right... the one containing a broken Helios.... bugger! So, sorry to say, for me it was a full image restore using my Acronis True Image, unfortunately, using a backup made some time ago. I then took a systematic approach (recording every step) to get everything back up-to-date whilst testing Helios at every stage hoping to find the culprit responsible for breaking it in the first place. Everything is back up and running but despite every effort, I still don't know why Helios threw a wobbly.. very worrying... I thought, here we go... Windows 10 or DCS 1.5 and Helios isn't going to be compatible... not an option, I'd go back to Windows 7 and 1.2 rather than lose the use of my touchscreen and Helios profiles. But, rest assured Helios lives on... Hope this has been of some help... just as a reminder - have a look at your restore settings (I've increased the amount of storage space in mine to allow more restore points to be saved) and I've also reviewed my backup strategy. Please let us all know how you get on - hoping you will discover what has caused Helios to stop working.

dburne, When you stop to think about it, it's no wonder our brains get scrambled... It's not just the amount of planes to tempt us in DCS... Reflecting on the last 12 months, I've upgraded my hardware, adding additional things like multiscreens, TrackIR, HOTAS, pedals and a touch-screen (all stuff which requires setting up, configuring and getting used to). I then set about learning to use Helios to create custom profiles for my touchscreen. No sooner had the dust started to settle when Windows 10 came along, resulting in my controllers not working.. new drivers and HUD software had just resolved those issues and I thought yeah... I'll get on with some flying but then DCS 1.5 beta takes the stage. Yes, a great improvement over DCS 1.2 but one which impacted on my Helios profiles requiring yet more time fixing things rather than actually learning to fly... All this going on and trying to focus on a study plane at the same time... mind blowing but we do it because we love it.. we get it but it wouldn't make sense to normal people! Finally, there's the other sims etc sitting on our desktops which we don't want to lose touch with. It's probably these which have led us to where we currently are - in my case I'm referring to IL2 '46/CLOD, and the seasoned guys still flying these great games several times a week - always willing to encourage newcomers and help them out. So, to this end, for me it's not just been one plane, one sim but rather a pattern of dipping in and out of everything, updating content, fixing issues, watching tutorials, researching and making a copious amount of notes. Despite everything, I still love everything I do and have no regrets. However, I have come to the conclusion that all this is too much and so, like you, I have decided to concentrate my efforts on studying one plane rather than trying to take on the world. Good luck with mastering Ka-50... I've taken on the equally challenging A-10C... hope to see you up in the blue stuff one day... (watch your ass) hahahahahahah!

After several hours of trying to get this working without success I'm off to bed all slewed out... :(

I would like to take part in this poll but there isn't a 'none' option! :lol:

Hi Vincent, I have the same issue and have found this post which may resolve: http://forums.eagle.ru/showthread.php?t=74071&page=2 I am going to check out the links contained within post #17 by Cibit Fingers crossed!