Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06861 Graphics Minor Always 18 days ago 12 days ago
Tester EoceneMiacid View Status Public Platform MAME (Self-compiled)
Assigned To Resolution Open OS Linux (64-bit)
Status [?] Confirmed Driver model1.cpp
Version 0.194 Fixed in Version Build 64-bit
Summary 06861: vr / vf: Camera position problem in Virtua Racing / Virtua Fighter (other Model 1 games?)
Description 0.194 appears to have introduced a regression with these games.
The view is now zoomed out too much, the camera position is wrong.
Steps To Reproduce Start and play the game. Virtua Fighter also demonstrates the problem in the attract sequence.
Additional Information
Flags
Regression Version
Affected Sets / Systems vr / vf
Attached Files
png file icon 0006.png (18,979 bytes) 17 days ago Uploaded by EoceneMiacid
EoceneMiacid
png file icon 0003.png (7,730 bytes) 17 days ago Uploaded by EoceneMiacid
EoceneMiacid
png file icon 0004.png (12,635 bytes) 17 days ago Uploaded by EoceneMiacid
EoceneMiacid
png file icon 0000.png (17,728 bytes) 17 days ago Uploaded by EoceneMiacid
EoceneMiacid
png file icon vr.png (29,613 bytes) 17 days ago Uploaded by wuemura
Compiled with make clean && make SOURCES=src/mame/drivers/model1.cpp -j7
wuemura
Relationships
There are no relationsihp linked to this issue.
Notes
21
User avatar
No.14694
EoceneMiacid
Tester
18 days ago
edited on: 18 days ago
Here are MNG's that show the problem

Virtua Racing: http://www.mediafire.com/file/a3gnduapq069iaa/vr.mng
Virtua Fighter: http://www.mediafire.com/file/qiqdq6uum1inlcq/vf.mng

User avatar
No.14695
B2K24
Moderator
18 days ago
Unable to reproduce on Windows 10 X64 with official release 0.194 binary.
User avatar
No.14696
NekoEd
Senior Tester
18 days ago
edited on: 18 days ago
Unable to reproduce, Linux/x64 0.194.

I can't view the MNGs but I'm familiar with vf's gameplay and see no difference from earlier versions. Nothing seems amiss in vr, either, the camera positions are all correct.

User avatar
No.14698
EoceneMiacid
Tester
17 days ago
Okay.

I just downloaded a fresh copy of the source here > https://github.com/mamedev/mame/releases/download/mame0194/mame0194s.zip
Extracted it, and produced a model1-only build with:

make SUBTARGET=tinymame USE_QTDEBUG=0 SOURCES=src/mame/drivers/model1.cpp REGENIE=1 -j5

Binary: http://www.mediafire.com/file/yg74z7nd0ppunmn/model1mame

The problem remains. I'm using GCC 7.2.0, if that matters.
User avatar
No.14699
wuemura
Tester
17 days ago
Try to film a original arcade or find a arcade footage, put mame output side to side so the developers can see how off the camera are.
Unable to reproduce, Linux and Windows.
User avatar
No.14700
EoceneMiacid
Tester
17 days ago
"Try to film a original arcade or find a arcade footage, put mame output side to side so the developers can see how off the camera are."

That's pretty useless advice, right?

I encountered a similar issue with legionna a while ago - gfx were scrambled, which nobody could reproduce. That eventually resolved itself, two MAME iterations (or so) later.
User avatar
No.14701
EoceneMiacid
Tester
17 days ago
edited on: 17 days ago
Added a bunch of screenshots

User avatar
No.14702
wuemura
Tester
17 days ago
Is not a useless advice because we can't reproduce the error and we don't know what you are experiencing.
I understand your frustration because I'm a Linux user myself, and MAME act crazy from time to time and is really annoying to report something that only happens with you and nobody else.

Can't reproduce with Windows, I'll do another test with linux now.

Go to your terminal and type env, copy that output. Then do locale and paste both output here. Post your mame.ini, is in your home in a hidden folder name .mame.
Run MAME with -verbose and post the output here also.
User avatar
No.14703
EoceneMiacid
Tester
17 days ago
edited on: 17 days ago
Well, finding a working Virtua Fighter cab within reasonable distance is not going to happen ;)

And there's no frustration involved, these things come with the territory (and I can't stand playing VF anyway).

And I appreciate you want to help, but none of the actions you proposed I'd take have anything to do with this issue. It's a compilation problem, not a configuration one. I have a few environment variables set up, but none of them have anything to do with compilation.

Also I posted a link to the binary > http://www.mediafire.com/file/yg74z7nd0ppunmn/model1mame

... so if you're on x64 Linux, please try this build to see for yourself.

User avatar
No.14704
wuemura
Tester
17 days ago
I could reproduce other issues.
Waiting for user input to confirm.
User avatar
No.14706
wuemura
Tester
17 days ago
edited on: 17 days ago
Compiling with:
make clean && make SOURCES=src/mame/drivers/model1.cpp -j7
The foreground is missing, run with -video auto. (make sure your mame.ini is default)
Changing video to "-video opengl" the machine runs fine.

Still waiting for EoceneMiacid so we can see what environment he is running at.
This is binary compiled with that options.
http://www.mediafire.com/file/yyz23t0hbeb2x8b/model1.7z

User avatar
No.14708
EoceneMiacid
Tester
17 days ago
edited on: 17 days ago
Pardon my expression, but what the actual fuck.

Your binary behaves exactly the same as mine.

I did some more testing:

Running with "-video software" either causes the game to run fine, to exhibit the camera problem or not render any polygons at all, seemingly at random;
Running with "-video opengl" appears to work fine most of the time, though every now and then (roughly once every five times?) no polygons are rendered.
Running with "-video bgfx" causes the camera problem 100% of the time, but never the 'no polygons' one.

I ran each test twenty times consecutively. There's a randomness factor in here which makes narrowing it down difficult.

User avatar
No.14709
wuemura
Tester
17 days ago
edited on: 17 days ago
Everything that was asked has everything to do to with everything, is well known that mame has issues with non C locales, this makes mame go crazy and mess up the graphics among other things.
https://github.com/mamedev/mame/issues/3004

That's why we need to know what environment you are at and what settings your are using to try to reproduce the issue.

Anyway, you get a confirmed from me.

For other testers with Windows, please try this binary.
http://www.mediafire.com/file/c8n6jbnaull3abm/Mame.7z

It was build with:
make clean && make TARGETOS=windows CROSS_BUILD=1 SYMBOLS=1 SYMLEVEL=1 STRIP_SYMBOLS=1 PTR64=1 SOURCES=src/mame/drivers/model1.cpp -j8

This mess up the graphics also.

User avatar
No.14710
EoceneMiacid
Tester
17 days ago
Huh. Okay.

My environment is:

COLORFGBG=15;0
COLORTERM=truecolor
DISPLAY=:0
HOME=/home/eocene
HUSHLOGIN=FALSE
KONSOLE_DBUS_SERVICE=:1.0
KONSOLE_DBUS_SESSION=/Sessions/18
KONSOLE_PROFILE_NAME=Default
LANG=en_US.UTF-8
LANGUAGE=
LC_ADDRESS=de_BE.UTF-8
LC_IDENTIFICATION=de_BE.UTF-8
LC_MEASUREMENT=de_BE.UTF-8
LC_MONETARY=de_BE.UTF-8
LC_NAME=de_BE.UTF-8
LC_NUMERIC=de_BE.UTF-8
LC_PAPER=de_BE.UTF-8
LC_TELEPHONE=de_BE.UTF-8
LC_TIME=de_BE.UTF-8
LOGNAME=eocene
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/system/data/scripts:/gamedata/bin
PROFILEHOME=
PWD=/mame
QT_QPA_PLATFORMTHEME=qt5ct
SHELL=/usr/bin/fish
SHELL_SESSION_ID=9dd1f4e1e4464d2c9fadf8fc6bce9bc7
SHLVL=2
TERM=xterm-256color
USER=eocene
WINDOWID=4194310
WINDOWPATH=2
WINEDEBUG=-all
XAUTHORITY=/home/ralf/.Xauthority
XDG_CACHE_HOME=/download/temp/cache
XDG_CONFIG_HOME=/system/config
XDG_CURRENT_DESKTOP=rde
XDG_DATA_HOME=/system/data
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SESSION_ID=1
XDG_VTNR=2

I notice LANGUAGE= isn't set properly. I did a clean install of Kubuntu 17.10 last week.
User avatar
No.14712
wuemura
Tester
17 days ago
edited on: 17 days ago
Running your build or my build with:
LANG=de_BE.UTF-8 ./model1mame -video bgfx vr

I got a similar result as yours.
Confirmed.

User avatar
No.14713
EoceneMiacid
Tester
17 days ago
Hey, thanks for investigating this.

I've been trying to run MAME with a few locales prefixed (en_US.UTF-8 for example) but that doesn't fix it for me.
User avatar
No.14714
wuemura
Tester
16 days ago
edited on: 16 days ago
You're welcome.
Mame team in general don't look in to this kind of thing, funky bugs like this get dismissed on the spot if can't be reproduced.

This will not get fixed by just changing locales, the developers have to look on to this to get a proper fix.

User avatar
No.14716
EoceneMiacid
Tester
16 days ago
Well, it's probably not straightforward to fix, and there's more rewarding things to pursue as a dev, no doubt.
I'm just glad someone else confirmed the bug :)
User avatar
No.14728
B2K24
Moderator
13 days ago
It seems another tester was able to confirm this behavior.
User avatar
No.14732
NekoEd
Senior Tester
12 days ago
I was waiting on developer input before doing anything, but nobody showed up.
User avatar
No.14734
Haze
Senior Tester
12 days ago
right, setting the MAME language option is causing some rather horrific glitches for some users, of note, some of which almost look like memory is being trashed.

probably needs running through valgrind or similar with the language options activated.