slicker55

Hi v81, I think you have made a very valid point in relation to 'intended use' and like you say if you're serious about flying and it's primarily for A-10C, the Warthog is the way to go. Damn these forums... I want one now... hahahahah, but then in my opinion, the X-55 is a great alternative if one or more of the other considerations is taken into account. Now to 'grease my stick'... again! :)

This is a very interesting debate. I have the X-55 and I'm happy enough with it for now but if it were to suddenly stop working, I would replace it with a warthog. For me, it was the old story... I was embarking on a new interest and didn't want to buy something really cheap and nasty. That said, I didn't want to go 'top shelf' to later find myself not taking to the flying scene. I must admit the price differential is a significant factor when deciding which way to go (particularly if you're new to the hobby like I was). So, for me it was the X-55 and it has served me well. That is, until Windows 10 came along and then the trouble started. However, the latest beta drivers/software has solved most (but not all) of the issues I was experiencing - some things still don't work as they should but overall, it's very usable once again. I'm currently learning to fly DCS A-10C and have only recently discovered the importance of the slew function. I have managed to get the nipple on the X-55 throttle to work but, like others have mentioned, the movement is very slow and I also find it hard to control. I am aware there are some in-game settings which can be altered to address this issue but I haven't managed to get enough info on this to be able to have a go myself. Perhaps someone will chime in with some instructions please?

Thanks for clearing that up - much appreciated :)

Hi BSS Sniper, I appreciate your last reply is for SuperSix2 but this is something I was curious about. Thanks for enlightening us - it just goes to show, 'you never know what goes on behind closed doors' :)

Hi HMA, Another sterling response to my questions - very impressed and grateful to you guys for being so helpful - I'll have another play and see if I have understood you correctly - fingers crossed. Either way, it's all good stuff - it's surprising how much you learn whilst trying something else out. Cheers again... :)

Hi P*Funk, Thanks for taking the time to respond to my post but I'm confused by your explanation. Please bear in mind that I am new to this and doing my best to understand your advice. I have recently learned how to use the mission-editor and created a very basic training mission to assist me with practising navigation. Then I found the youtube tutorial demonstrating how to create a flight plan using the CDU. I created a flight plan using the CDU and flew it successfully but later couldn't find a way of saving it for future use. I appreciate a 'mission' and a 'flight plan' are different things but you may agree that in it's simplest form a 'mission' (containing only waypoints) is, in itself, a flight plan. So, if this is correct, why not just create a mission (which can be saved) using the mission-editor instead of the CDU method shown in the youtube tutorial? .

Re. Post #45 (I was barking up the wrong tree)... copied/pasted all the instrument .lua's from Loz V2.1 and everything is working now.

I have followed a youtube tutorial and learned how to create a custom flight plan using the CDU but I can't see any way of saving this for future use. Just wondering if this is possible and if so, how to do it? Here's a link to the tutorial should others be interested: .

Forget it chaps - sorted. Windows 10 (Touch settings) Uncheck the option Show visual feedback when touching the screen Bingo!

I have been using most of CaptZeen Helios profiles without any issues until recently. I'm not sure whether it's Windows 10, DCS 1.5 beta upgrade or something entirely different that is affecting the way my buttons work in Helios. I've noticed they don't respond in the same way as they did prior to my upgrades. I'll try to clarify what I'm referring to. Normally, when a button is pressed, it just activates and that's it. The same applies when tapping certain area's of the screen to reveal a 'hidden' panel (A-10C profile by LOZ). However, since the upgrades, these buttons do not function in the same way and instead require a little 'nursing' to get them to function. In the case of activating a 'hidden' panel, it seems the 'hot-spot' has to be tapped several times or even stroked to reveal the panel which then quickly disappears unless the button is physically held down. I have found that with a little patience the hidden panel will remain visible even after releasing the pressure but this behaviour is a bit hit and miss. It's a very similar procedure to re-hide a panel after use. Anyone else experienced this behaviour? Anyone got any suggestions? .

Thanks for taking the trouble to capture these screenshots and upload them here. I think they're very encouraging - I've just had a flash of inspiration... I haven't managed to get so many exports showing on my touchscreen yet but I'm feeling more confident having now seen your screenshots. If I can get as close as you, I'll be having a look at the layer order in Helios to see if moving things up or down allow the exports to become visible? Just an idea - might be barking up the wrong tree but who knows :)

Hi Sobe, Thanks for sending me your .lua (very helpful) I have managed to get the shkval export working on my Su-25T. I have also got the two MFD's on my A-10C working. Now, to see if I can get the other exports working on the A-10C. I believe my monitor issues were caused by a few lines of code at the end of my custom monitorsetup.lua's which used to force the GUI/Menu onto the centre screen only. This code worked great in the previous version of DCS but causes havoc in 1.5. This is a shame because I found the GUI/Menu confined to the centre screen much better than spread across all three screens.

I'm now running DCS 1.5 on triple screens but can't get viewports to show up on my additional touchscreen - I have tried everything I've read so far but to no avail - I must be missing something. This is an export issue only as all the gauges and switches in my helios profile are working correctly. It may be helpful to see a working copy of a custom monitorsetup.lua from someone with a multi-monitor / touchscreen setup like mine. Would someone be kind enough to upload theirs please? Any suggestions greatly appreciated.

I've just come across this post whilst looking for something else. I see you've had no takers so I'll do my best to help since I am also using the X-55 HOTAS system with DCS. Before going into further detail, have you managed to get everything sorted out? .

. I use a similar aide-memoire but just wanted to say 'that's a nice piece of artwork' - well done :) .

Viewport Not Working Since 1.5 :( Hi Guys, DCS 1.5 is working fine for me using a triple-screen setup and additional touchscreen for helios. I'm testing my setup using CaptZeen's Su-25T profile - all the gauges are working fine in the profile but I can't get the viewport to work for the shyval. (note: it is working in the sim). Everything used to work 100% before upgrading to DCS 1.5 Any suggestions please?

Did you get one... did it fix it? I would also be interested to know if your X99 system will do a warm 'restart' if the controllers are connected - mine won't / just hangs at the BIOS screen so I always switch off rather than choosing restart - not a big problem until an update requires a restart. Another thing for you to bear in mind in relation to the Siatek drivers (are you aware there are windows 10 beta drivers available now from Saitek web site), But, bear in mind... once you have installed the beta drivers, if you unplug the controllers for any reason, windows will automatically reload the original drivers - just watch out for this one... ...

.. Are you saying this is what's causing my problem or are you saying you've found something else? ..

Helios people, My world has fell apart tonight.. Just starting to test DCS 1.5 Beta after resetting controllers etc. I have been using Helios for over 12 months and it has worked flawlessly under Windows 7 and 10 (64 bit). Tonight, I had just saved some work I had been doing on a DCS profile and closed the Helios editor. I tried to open the control centre but I just get a pop-up message which says the program has stopped working I tried to re-open the editor - again, it won't run - actually nothing happens - no message - just nothing. So, I tried uninstalling helios and reinstalling (no joy), there's only been one windows 10 update in the last few days so I tried uninstalling that (no joy). So, now wondering if this is a Windows 10 issue or has DCS 1.5 beta installed something which conflicts with Helios (thinking directX 11).. reaching out for some idea's before jumping in with both feet, uninstalling DCS 1.5, then, if no joy going back to windows 7. (that will have to wait for another day - been on it too long already and need to be on the ball to tackle that minefield)... ..

Hi Gary, Thanks for your comment, sorry I can't offer an answer to your issue either but yes, you're right... once the correct file is identified I think I'll be onto a winner.

On my DCS (non-beta) version I changed the appearance of the ATC menu (font, font size and font colour) by editing the CommandMenu.lua (not my genius - something I found on the net somewhere). I thought it would be a simple case of copying/pasting this file from the none-beta version to the beta version. I did this, ran a test and found the appearance of the ATC menu (on the the right-hand side of the screen) had changed but the response messages (on the left-hand side of the screen) remained very small and almost unreadable (default font, size, colour). So, I believe there must be another config file somewhere which determines the appearance of the response dialogue - question is... does anyone know where this file is stored?? I'm not a programmer but in my own tin-pot way I've been at it for a few hours now and can't nail the bugger down.

Hoping someone will drop in and provide a definite yes/no (to deletion question) as I don't want to drop a clanger

Guys, Hope this hasn't been answered somewhere else and I've missed it - here goes... I have been told the beta installs to a new directory and sits side by side with the original so the modules can be transferred without losing an activation life. If this is correct, once the beta has been installed and modules transferred, can the original installation be deleted?

Helios users may appreciate this quick update... after a few hours of further testing I discovered that I could get the 'add interface' to display the X-55 controllers by creating a new profile, adding the interfaces and then copying/pasting all the content from the 'old' helios profile into the new one. I have also found that if all key commands are 'saved' in the Helios profile, everything seems to work fine. Key commands stored within the HUD profile seem to be a bit hit and miss although all axis's work well. I really do hope updated HUD software will resolve these issues - fingers crossed - would love to hear from any other Helios users.

Hi guys, Since upgrading from Windows 7 (64 bit) to 10 (64 bit) I have noticed a few issues. Initially, the Saitek X-55 HOTAS system threw a wobbly (USB connectivity, some switches not working, some key strokes repeating endlessly). For anyone experiencing similar issues - I'm glad to say the latest beta drivers seem to have addressed these issues. madcatz.kayako.com/Knowledgebase/Article/View/604/46/windows-10--saitek-hotas-beta-drivers-and-software-release However, there are further issues with Helios and the X-55 as follows: First, in relation to Helios... I have noticed that Helios profiles created since the W10 upgrade are not working properly. The 'add interface' no longer shows the X-55 Stick or Throttle and hence are unavailable to Helios. Anyone got any suggestions? Gadroc... (if you see this post) ... appreciate your excellent Helios program was created some time ago but do you know whether it is compatible with Windows 10? I'm hoping these issues are driver/software related and that they will be rectified when Saitek release a final version of the HUD software. Any thoughts guys...