Helios acting crazy, mouse but no touch. I need help. Please
-
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?
-
Which one? This post talks about a few issues.
-
Having Windows 10 creators update installed.
-
Could be. I can only suggest based on my experience. It may well be resolved now with updates to Win10CU, but I’m in no mood to be spending time testing. I KNOW it works with Win10AE, so I’ll stick with that for the near future.