Main > Main Forum

VMMaker shows only 1 analog output for 5450 where Calamity Guide says 2?

Pages: (1/5) > >>

Duffy:

Hi guys,

First of all thank you very much calamity for creating all this so that us plebs can enjoy games as they were originally intended!

I noticed when using vmmaker to install modelines that my 5450 only shows as having one analog output, where the guide says that Calamity’s has two analog outputs. Is this a bug? Could this be a symptom of the issues I’m having with crt switchres?

Thanks in advance,

Duffy



Zebidee:

What video outputs does your video card actually have? If unsure, post a pic (of the output ports, end-on).

Duffy:

I have a Radeon HD 5450 2GB GDDR3 (DVI-I, HDMI, VGA), i’m using a VGA to Component transcoder
With success, but some issues.

  https://visiontek.com/products/visiontek-radeon%E2%84%A2-5450-2gb-ddr3-dvi-i-hdmi-vga

The same one from Calamity’s guide here

  http://geedorah.com/eiusdemmodi/forum/viewtopic.php?pid=1052#p1052

In the guide he mentions that he’s using an HD 5450, there are two analog ports, and to use analog1
for the 5450. No mention of AIB (whether visiontek, sapphire etc. unsure if it matters).

I’m wondering about this because I'm having some issues where groovymame doesn’t start on the crt through launchbox.. sometimes.

Something odd that happened this afternoon,I uninstalled every video driver and did a ddu cleanup for both my nvidia card and this amd card, reinstalled crimson and nvidia drivers, reinstalled  crtemudriver, and in VMMaker,
Analog1 was there. I enabled edid for it, but all that happened was my oled screen flickered (no signal from crt).
I went to the drop down again and the options were changed to just analog0 and the two digital outputs. I enabled edid again with analog0 selected, and then I get a stable signal from my crt. Still having the groovymame starting on the oled sometimes issue.

Here are my outs, thanks for takin a look man.




Zebidee:

Maybe you want to specify the display in mame.ini?

On last (fourth) tab in VMMaker, there is a checkbox to export settings to mame.ini - make sure that is ticked and the right executable (*.exe) selected. This allows VMMaker to update mame.ini.

Only other thing I can think of is your transcoder - maybe it is sending monitor ID (EDID) signals of it's own? Seems unlikely, though if you've got one of the ---steaming pile of meadow muffin--- ones floating around on Aliexpress right now then who knows for sure.

You could generate a log file and attach it here - this should show what monitor Groovymame is trying to use.

EDIT: Instructions for generating a log file are at the bottom of all Calamity's posts.

Duffy:

Mmmmm muffins..

I've changed screen0 in mame.ini to the current display label set by VMMaker which is \\.\DISPLAY9 (I've noticed the display number changes every time I generate and install new modelines which I think is normal?).

Edit: I do have the export setting to mame.ini ticked in the mame tab and have it directed to mame.exe in GM folder.

I think I am not doing the Groovymame install right, so I try to reinstall Groovymame following Calamity's 2019 Guide (most recent i can find):

  http://geedorah.com/eiusdemmodi/forum/viewtopic.php?id=433

In step 2, he mentions to unzip GM, give mame64.exe admin privileges. Mine is just called mame.exe, I assume they're meant to be the same thing? The admin privileges tickbox is greyed out for me. Any idea why?
In step 3, he mentions there should be a source folder in the ini folder, that's not there for me. Otherwise I follow it to a T.

Now I navigate to groovymame root, open mame.ini and set:

  rompath                   <path to romset>
  ..
  screen0                     \.\\DISPLAY5

Then I try to start a game through command line by opening CMD with admin privileges, navigating to groovymame root

 mame.exe -v romname

Mame now opens on the CRT!
But the game does not run, just an error message (photo below)

I followed the instructions from Calamity's sig to get a log.

  - From command line, run: groovymame.exe -v romname >romname.txt
 - Attach resulting romname.txt file to your post, instead of pasting it.

In my case it the command looked like

  mame.exe -v romname >romname.txt

And the .txt file generated in the groovymame root folder.

Sorry if I'm being too wordy, I'm still learning and I've run into so many weird issues that I want to be as clear as possible, also I want to make sure anyone else having my issues in the future can get help from this.

Thank you very much for your time and patience Sensei! Oh yes before I forget, I do have a turdmuffin VGA to Component transcoder from ali express:

  https://www.aliexpress.us/item/3256806686968960.html

but I also have a wakaba VGA to Component transcoder on the way, it should be here in about 3 weeks or so, I had the same thought as you a couple weeks ago.


Pages: (1/5) > >>

Go to full version