Jump to content

All my products and services are free. All my costs are met by donations I receive from my users. If you enjoy using any of my products, please donate to support me. My bare hosting costs are currently not met so please consider becoming a contibuting member by either clicking this text or the Patreon link on the right.

Patreon

If neither of those of work for you, you can donate any amount by clicking here.

Recommended Posts

Posted

Greetings all,

I am now having a problem with my copy of GameEx in which it appears to no longer properly monitor for activity from my Media Center remote's "Start" key. Basically, when I press the "Start" key on the remote, Media Center (almost) immediately throws a "(video card/drivers not compatible)" error, followed by GameEx throwing an exception a few seconds later.

I have spoken with Tom about this...for me, this issue appears to have gone away in 7.78, but, it appeared to come back once I updated to 7.79. Tom also says that, to him, this appears to be an issue specific to my HTPC.

Any help you guys could offer getting my GameEx back up and running properly would be very much appreciated.

Thanks in advance for any help you may be able to offer!

--Quinn

Posted
Greetings all,

I am now having a problem with my copy of GameEx in which it appears to no longer properly monitor for activity from my Media Center remote's "Start" key. Basically, when I press the "Start" key on the remote, Media Center (almost) immediately throws a "(video card/drivers not compatible)" error, followed by GameEx throwing an exception a few seconds later.

I have spoken with Tom about this...for me, this issue appears to have gone away in 7.78, but, it appeared to come back once I updated to 7.79. Tom also says that, to him, this appears to be an issue specific to my HTPC.

Any help you guys could offer getting my GameEx back up and running properly would be very much appreciated.

Thanks in advance for any help you may be able to offer!

--Quinn

To keep everyone posted...

Updated to 7.81, and now log shows new/different output when failing to properly release control to media center.

Log file is attached.

Thanks!

--Quinn

log.txt

Posted

Interesting Findings...

After playing around with the semantics of this issue for a bit, I think I understand more about what is going on...

I've now found that, exiting GameEx (by pressing MCE "Start" key) within 15 seconds of starting GameEx reproduces this problem 100% of the time. Directly shadowing that is the finding that pressing the MCE "Start" key MORE than 20 seconds after GameEx has started ALWAYS results in a perfect MCE restart (IE: GameEx does what it's supposed to do 100% of the time in this case). And, the 5 unaccounted seconds seem to produce a meaningless set of results.

In short, let me just apologize for wasting everybody's time with this...this really (IMHO) should be a low-priority issue... The reason I find stuff like this is due to my clumsiness (I am moderately visually impaired, and have a mild case of tourettes,) so it's not uncommon for me to fumble a bit when I use the remote.

Anyway, I'm sorry to have wasted everybody's time with this, and, if Tom sees fit, he can add this to his "To-Do" as merely "something somebody mentioned." :D

Thanks again to anybody and everybody who took the time to simply follow this thread!

--Quinn

Posted

Hi Quinn,

the only errors i have had previously with mce, was when it launched while gameex was still running as a process (the 2 cant be running at the same time me thinks).

Here's a long shot which could fix the problem....You could try adding a delay between gameex and mce by using a batch file.

Try using this setting in GameEx:

LaunchOnExit=MCE Delay.bat

or

LaunchOnExitNoWait=MCE Delay.bat

Create the following batch files using notepad and name them 'WAIT.bat, and 'MCE Delay.bat', and place them in the gameex directory, (both of them must be in the same folder).

WAIT.bat

@ping 127.0.0.1 -n 2 -w 1000 > nul
@ping 127.0.0.1 -n %1% -w 1000> nul

MCE Delay.bat

CALL WAIT 4

The number after CALL WAIT denotes the amount of time delay, this can go as high as 9 seconds.

It might work....

Posted

Amos,

Thanks for the tip. I'll be sure to make use of it if things start going awry again. :-)

Much Thanks!

--Quinn

Guest
This topic is now closed to further replies.
×
×
  • Create New...