- --
Viewing Issue Advanced Details
[ Jump to Notes ]
ID | Category [?] | Severity [?] | Reproducibility | Date Submitted | Last Update |
---|---|---|---|---|---|
05756 | Documentation | Trivial | Always | Oct 22, 2014, 10:25 | Oct 22, 2014, 16:04 |
Tester | demotester | View Status | Public | Platform | MESS (Official Binary) |
Assigned To | Resolution | Invalid report | OS | Windows XP | |
Status [?] | Closed | Driver | |||
Version | 0.155 | Fixed in Version | Build | Normal | |
Fixed in Git Commit | Github Pull Request # | ||||
Summary | 05756: Documentation: -d3dversion option no longer supported, but still listed in documentation | ||||
Description |
The MESS crashes if start with options "-video d3d -d3dversion 9". some examples: mess0155 megadriv -cart day_trip.BIN -video d3d -d3dversion 9 (it crashes at start) mess0155 vectrex -video d3d -d3dversion 9 (it crashes at start) Note: My PC supports Direct X 9c by hardware ... DXDIAG passes w/o a problem. The problem seems starts to appear from MESS 0.149 version: (some examples) mess0148 megadriv -cart day_trip.BIN -video d3d -d3dversion 9 (it starts and works fine) mess0149 megadriv -cart day_trip.BIN -video d3d -d3dversion 9 (it crashes at start) mess0148 vectrex -video d3d -d3dversion 9 (it starts and works fine) mess0149 vectrex -video d3d -d3dversion 9 (it crashes at start) Note: mess0148b, mess0149b ..... http://www.progettosnaps.net/mess/links.html |
||||
Steps To Reproduce | |||||
Additional Information | |||||
Github Commit | |||||
Flags | |||||
Regression Version | |||||
Affected Sets / Systems | Documentation | ||||
Attached Files
|
requested_output.png (7,850 bytes) Oct 22, 2014, 15:45 Uploaded by demotester
| ||||
Relationships
There are no relationship linked to this issue. |
Notes
7
No.11148
Mamesick Senior Tester
Oct 22, 2014, 11:31
edited on: Oct 22, 2014, 11:32 |
Ehm... Actually D3DVERSION option has been removed from the core, exactly around 0.149 IIRC. It should not be used... Though MESS shouldn't crash but simply ignore the inexistant option... MAME/MESS now use the latest D3D version by default. |
---|---|
No.11149
demotester Tester
Oct 22, 2014, 12:02
edited on: Oct 22, 2014, 12:23 |
And it should also revert itself at least to gdi if found any problem in d3d ... cases like MT05754 should not happen, right? ... Ehm, what a MESS ! ;-) Btw ... MESS User's Manual -> http://www.mess.org/mess/howto (it is still mentioned there) --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Video Modes MESS allows you to choose also different video configurations, to improve compatibility with older video card. These settings are OS-depending. If you are using MESS for Windows, you can select -video d3d -video ddraw -video gdi D3D is the fastest setting, but it requires a Direct 3D 8+ compatible graphics card. If your card is not compatible with latest Direct 3D, you may want to try ddraw or gdi. You can also select which version of Direct 3D libraries to use, by setting the -d3dversion options. You can only choose between 8 and 9 (corresponding to Direct 3D 8 and Direct 3D 9), 9 being the default. --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
No.11152
Tafoid Administrator
Oct 22, 2014, 14:23
|
With such a large and ever expanding project, it is not uncommon to see remains of commands which were refactored or even disposed of/replaced. I'll see that the mess.org is updated ASAP. Like I mentioned in the other bug, all these display issues are falling under "configuration' which we simply don't have all day to work through with each person who has a problem. As it stands, I cannot replicate in any instance listed above any crashes at all other than it telling me: Error: unknown option: -d3dversion. Anyway, If you have the official binary, MESS should provide to the command prompt a stack crawl for any emulator crash (the mess.exe comes with a mess.sym file). Can you please post this output? |
No.11153
demotester Tester
Oct 22, 2014, 15:06
|
Yes, the mess0155b.exe is official binary ... but now not sure what exactly you asking me to do ... could you provide an example command how to use mess.sym file to get requested output ? |
No.11154
Tafoid Administrator
Oct 22, 2014, 15:17
|
You said your MESS crashes... if it is crashing there will be some message or stack crawl which details information related to where the crash occurred or why. This will require you to run MESS from one of these command prompts and not double-click the MESS file to run it. |
No.11159
demotester Tester
Oct 22, 2014, 15:44
edited on: Oct 22, 2014, 15:47 |
Yeah, if start from command prompt it reports: "Error: unknown option: -d3dversion" (see on attached picture) Before I was starting from a created batch file ... f.ex. start.bat ... with content f.ex.-> "mess vectrex -video d3d -d3dversion 9 > output.txt" ... and got an empty output.file. It appears now it is more a "not starting emu" than a "crashes emu" issue. Or no issue at all if it starts from a command prompt. |
No.11161
Tafoid Administrator
Oct 22, 2014, 16:00
|
That's what I thought. This is not a crash in any real way of reporting bugs. It is an error (user error) which is indicating to you that the option is invalid. FYI, " > output.txt" only covers STDOUT. You also need to cover STDERR if you are to capture all output from an application and any type of error will likely be a STDERR output. In order to cover both instance, use > output.txt 2>&1 . This will bring all text captured to the same file. Closing as an invalid report. |