QuickPlay Frontend

Hello,

When exiting a PC game, how do I get QP to auto close the command window. Currently, the game exits but the command window remains opened.

Thanks,
Jason

I don't experience the same problem when using the 'Windows Start Command` emulator. Which 'Emulator' are you using?

Thanks Butter100fly.

Here's what I am using:

D:\QuickPlay\tools\ReactOS_CMD\cmd.exe

Here's the parameter:

/C start "QP" /D "%ROMDIR%" /WAIT /B "%ROM%"

Any suggestions?

Works fine on all my PCs I'm afraid. Perhaps you have some terminal setting setup to not quit on the exit of the child program that React is inheriting from windows (pure guess, probably not true, React probably doesn't work like that). You've tried it with a variety of games I guess...

Some things you can try:
1) ALT+TAB out of the game and right click the react window and look at the settings
2) Try the OTHER PC 'emulator' QP has (I setup two for situations like this: "Windows Explorer (for shortcuts)". Try it with and without pointing to a shortcut instead of the executable
3) get rid of the /WAIT in the call, what does that do?
4) Instead of calling react change the call to CMD.exe in SYSTEM32 (same parameters)

Thanks again Butterfly.

The /WAIT command - no idea where that came from. I removed it.

As for the other options, I tried looking in the options of cmd.exe and do not see anything out of the ordinary. Also tried the other options you suggested. No joy.

The problem is on my end so I will see what else I can do. Minor issue though and not even a problem.

jaw970 wrote:Thanks again Butterfly.

The /WAIT command - no idea where that came from. I removed it.

Umm - it came from the config, I figured out, to stop parent processes taking over the active window until your game is finished

jaw970 wrote:TAs for the other options, I tried looking in the options of cmd.exe and do not see anything out of the ordinary. Also tried the other options you suggested. No joy.

Shame. I have 3 windows pcs i test stuff on, totally unrelated builds all work with this without seeing your issues

It crashes right after it exits to the desktop. I see my desktop for about a second, then it powers off. I can't list all the games, since it seems to be happening to almost all current generation games, (stuff that's slightly demanding). Some are L4D2, Crysis, Civ5, Bad Company 2.

Hi there

What do you mean 'crashes' and 'powers off'? Can you say what you expect to happen, what command line you are running from QuickPlay (right click and 'run as'), and what actually happens, step by step, from when you select to launch the game?

Also, what happens if you run that command line outside of QuickPlay?

hi all. I still want to understand what problems people are having with this so i can fix them?

As I said I have several test pcs using different environments and don't find any issues, QuickPlay has two different means for loading pc games and other windows apps: explorer and windows start command. Both work great for me with PC games. Can someone please tell me in more detail what goes wrong for them? Its definitely time to look at command line runners.....