Helios acting crazy, mouse but no touch. I need help. Please
-
Hello All,
I’m really at a lost here.
I upgraded my computer to Windows 10 Home 64. I did a perfectly clean install, on an empty system.
Everything seems to work OK, except for Helios.
I’ve tried to install the 1.3.190 version, but the Helios installation routine asked me to install the .Net Framework client profile 2.0 and some DirectX stuff, which I did. I managed to install Helios. I opened one of my profiles in the profile editor, that worked perfectly OK on Windows 8.1. After resetting the monitors and saving my profile again, I launched the control centre to test the profile.
And here’s the crazy part : my profile works just fine if I use the mouse to activate, rotate, etc. the buttons and panels. But when I try to do it with my fingers, that’s a no go. And my monitor’s touch function is correctly activated. I can use my fingers with other software, I can move windows on the desktop, etc. But impossible to make my Helios profiles “feel” my digital actions. I’ve searched the forums, here and at DCS and I can’t find any solution. I’ve tried running the Control Centre as administrator, I’ve tried compatibility mode with Windows 8 and Windows 7, but to no avail.
So any help would be greatly appreciated.
Thanks a lot -
I’m guessing you’re running Windows 10 Creator’s Update. I’m also guessing you missed my PSA here.
I’ve rolled back to Windows 10 Anniversary Update and everything’s working fine.
-
-
I’m guessing you’re running Windows 10 Creator’s Update. I’m also guessing you missed my PSA here.
I’ve rolled back to Windows 10 Anniversary Update and everything’s working fine.
Ice, thanks a million for your prompt answer. I thought I was the only one having this problem and I hadn’t seen your PSA.
I’m definitely going to roll back to AU. Can you give me an idea how to proceed? I’m a bit worried about Windows Update that could reinstall CU without asking me if I agree.
I’ll keep following this issue. There’s no reason we can’t find a solution, even under CU.Judy
-
[A little bit more discussion on the issue here.
Oh no I might need to go back to Win 8.1 :(](http://simhq.com/forum/ubbthreads.php/topics/4350550/re-windows-10-creators-update-ver-1703#Post4350550)
-
From the day I updated Win10 to the CE update, Target would not run properly. Last night I updated the update and so far Target is running fine. Too soon to be sure. Helios is also running fine. Again, too soon to be sure.
-
No need to go back to 8.1…. but if I were to roll back, I’d go back to Win7
I had an image of Win10AU that I’ve saved as part of my backup files, so I was good on that front. I’ve also turned off the big update feature; Google is your friend on how to do this. So far, I’ve been through 3 updates but it’s not forced me to go to CU yet. I always make a system image before updating and always check my Windows version after updating to make sure I’m still on AU.
-
So,
I was not able to stop the auto install of Windows Creators Update.
After everything was finished, I cranked up Helios, and it appears to be behaving ok.
However, now YAME 64 does not start.
I uninstalled and reinstalled, cleaned registry with CCleaner and still nothing.
I don’t know what may be causing this.
Ice any ideas?
Pika -
OK, here’s where I am right now:
I have Win10 Home running with BMS, YAME, Target scrip, Livrot and Helios running as they all should be.
But I’ve had to fight a bit:
I did a clean install of WIN10 AU with my Ethernet cable disconnect, to prevent even the downloading of any update during installation, you never know
Then I edited the Registry in order to force Windows to warn me before downloading and installing updates. It is explained here :
https://www.forbes.com/sites/gordonkelly/2015/08/26/windows-10-how-to-stop-forced-updates/#20293aa046f6
I connected my Ethernet cable again, launched Windows update. It downloaded and installed hotfixes and security updates, but not Creators Update.
After rebooting, Windows Update told me that Creators Update was just around the corner and that it would be installed soon.
I then disabled the Windows Update service, just to be sure.
I am now running Windows 10 with the current hotfixes and security updates and with everything I need for my simming experience.
I know that eventually I’ll need to update to CU, but I’ll try to defer it as long as I can, hoping that someone in the know can modify Helios’ code so that it runs under WIN10 without hacking it.Pika,
Are you saying that you installed Helios and Yame under Win10 AU and that Helios continues to work after updating to CU?
As for Yame, I suppose its developers are testing it under Win10 and I trust them to make sure the next version works OK under Win10.Judy
-
Yes, that’s exactly what I’m saying. I could not stop the Creators Update update and so I installed it. After the install, I fired up BMS and it worked fine. Then I fired up Helios and it worked fine so far. When I loaded YAME the program crashes.
Have you tried doing a Helios clean install?
Pika -
I have yame working well under cu win10
-
Roccio,
I suspect it has to do with unrecognized apps.
What do you suggest I turn off?
Pika -
Yes, that’s exactly what I’m saying. I could not stop the Creators Update update and so I installed it. After the install, I fired up BMS and it worked fine. Then I fired up Helios and it worked fine so far. When I loaded YAME the program crashes.
Have you tried doing a Helios clean install?
PikaSo maybe that would mean that Helios needs to be installed under AU before updating to CU… That would be very interesting and that would allow us to use Helios on a touchscreen with Win10 CU. I’d like that
Yes I tried to clean install Helios under CU, but it would only work with the mouse and not in touch mode.Judy
-
Is your YAME app working?
We seem to have the same problem but with different apps
Pika -
One more thing:
I started windows in safe mode and my YAME app worked!!
I am just going by process of elimination now. I started with the antivirus first.
I’ll post what else I’ve done.
Pika -
Unfortunately, I was so pre-occupied with Helios that I can’t remember if I tested YAME.
Pika, you may be able to System Restore to a point before CU was installed? There are quite a few articles on the net about stopping AU from patching onto CU. I’m still on AU and I’ve not had to turn off updates.
-
Yeah,
That is my next step.
Like you, I built my Rig just to run BMS. So I don’t need no Creators Update. I don’t create anything on this computer.
I hate M$!!!
Pika
PS. Its a necessary evil I know -
Like you, I built my Rig just to run BMS.
Haha… the rig runs other stuff too, you know
Elite Dangerous on VR… oh boy! -
Yame runs fine here.
-
ICE, I just read this could this be the issue to all my problems that I mentioned in a earlier post? Has this not gotten resolved yet?