GroovyMAME not switched resolutions?

[agalardi]

Hi, this is my first post, so first of all greetings.

I have CRT emudriver succesfully installed.

If I set desktop in interlaced mode (ie 640x480i) and I launch groovyMAME, the games look fine, but I notice flickering.

If I set desktop in progressive mode (ie 2560x240p) and I launch groovyMAME, the games look fine and I have not flickering.

It looks like there is not resolution change at all.

I thought that with super-resolutions groovyMAME should change vertical resolution for each game. Am I wrong?

What am I missing?

Thanks in advance

PS: Currently using HyperSpin with the same result, so it seems not related.

[agalardi]

Nobody have a suggestion? any clue to investigate? 

[Paradroid]

What am I missing?

A log file?


Sent from my SM-G955F using Tapatalk

[agalardi]

What am I missing?

A log file?


Sent from my SM-G955F using Tapatalk

Touché! 

Attached you can find both examples:
   > gng-i.txt = desktop at 640x480. result is flickering in game
   > gng-p.txt = desktop at 2560x240. result is NO flickering in game

Thank you!

[agalardi]

I give up! 

As I have not solution I will set desktop at 2560x240p. This is useless because the stretch but I will try to change it only when needed.

[Calamity]

Sorry for the late response.

Your configuration looks correct, however D3D9ex is not switching resolutions for some reason. Please before giving up, try this:

- If you're on Windows 10, make sure to disable the Game Bar.
- Make sure to install DirectX Redistibutables (https://www.microsoft.com/en-us/download/details.aspx?id=8109)

You can't use a super resolution on the desktop, if you do so GM will not be able to adjust the refresh rate.

[agalardi]

Hi Calamity, if I have chances I'll retake the problem... Thank you

- Curretly using RetroOS 2.0.3 (Windows 7 Pro 64 bit)
- DirectX 11 is pre-installed (attached screenshot)

GroovyMAME is also 64bit version. HyperSpin and RocketLauncher ... I don't know, I think that they are 32 bit. I don't know if it really matters.

[Calamity]

You need to install the DirectX redistributables from the link above. See the error you have in your log. It's because DX 9.0c is not included by default in Windows.


Also, try renaming your GM executable to something different. This may sound silly, but sometimes after a failure, Windows includes a given executable into some sort of black list and then DX runs into an emulated mode. Renaming it will bypass the issue.

[agalardi]

Bad news (for me). Same result.

DirectX 9c installed. System rebooted. GM EXE renamed.

Attached the verbose logs. Maybe I am not very good at it, but I am not able to see the problem in the logs... are you?

[Calamity]

The DX specific error is now fixed.

However you still have a problem with modes not switching:

Code: [Select]

Direct3D: Device created at 640x480
There you should see the correct resolution (2560x240 or any other).

The reason why it's not switching is impossible to say by looking into the log. There must be something in your system blocking mode switching from working correctly. It could be a remote desktop app, or desktop cloning, or pointing to the wrong output, etc. Can you switch modes through Arcade OSD?

[agalardi]

... Can you switch modes through Arcade OSD?

Yes, I can switch modes through Arcade OSD.

There must be something in your system blocking mode switching from working correctly. It could be a remote desktop app, or desktop cloning, or pointing to the wrong output, etc....

wait! wait! wait!... I am using UltraVNC to work without opening the cabinet, connecting keyboard... do you mean that this could be the reason? I can even use Arcade OSD to switch it remotely...mmm

I need to say that working remotely is totally comfortable and fast. If there is no option to do it it will be a pain. But of course, the most important is to solve the problem.

To do list for this evening:
- Connect a physical keyboard and try without using UltraVNC
- Connect a physical keyboard and try uninstalling UltraVNC if needed

[newmanfamilyvlogs]

I may be wrong, but I seem to recall having a similar issue with UltraVNC in the past. I currently use TightVNC and do not have this problem (TightVNC also has an excellent mobile version which is very handy when you're standing at the machine).

Does UltraVNC install a 'display mirror' driver? There is one available for TightVNC, which I do not use, that I also think I've run into issues with.

I would try uninstalling UltraVNC in favor of a vanilla TightVNC installation.

[agalardi]

I haven't time to make all tests. Only one: stop UltraVNC and try, but it didn't work.

When I have a little more time I will test other options.

I may be wrong, but I seem to recall having a similar issue with UltraVNC in the past. I currently use TightVNC and do not have this problem (TightVNC also has an excellent mobile version which is very handy when you're standing at the machine).

Does UltraVNC install a 'display mirror' driver? There is one available for TightVNC, which I do not use, that I also think I've run into issues with.

I would try uninstalling UltraVNC in favor of a vanilla TightVNC installation.

Thank you for your suggestion newmanfamilyvlogs, If UVNC is the problem, TightVNC will be a perfect solution.

[Calamity]

If the problem is related to a remote desktop app, it's certainly cause by its mirror driver. So probably you'd need to uninstall it rather than just stop it.

IIRC mirror drivers are a Windows 7 thing, probably you wouldn't have this problem on 8 or 10.