Quote:
|
Hur, triangles that just disappear under random circumstances?
Its always something silly you don't think of, so could it in any way be related to the vertex winding order perhaps? I know I've made a triangle or two disappear that way when I was playing around with 3D stuff... |
It changed when I resized the window which makes me wonder if its related to the depth buffer when you first setup the 3D viewport. I have had issues with polygons vanishing due to z buffer.
|
Quote:
Does http://www.winuae.net/files/b/winuae.zip change anything in D3D problem? |
Quote:
EDIT: Forgot to test DirectDraw mode! Display now looks better in WB although the mouse pointer is still missing. |
Quote:
Vertex buffer's Z-coordinates were left uninitialized (should have been zeroed). Apparently allocated vertex buffer contains usually zeros but not always (I'd have expected D3D debug mode to fill it with random values to prevent these kinds of hidden uninitialized variable bugs) Quote:
|
Quote:
It may seem silly, but this is a true bastard. No brown paper bag for you mister ;) |
The latest WinUAE beta 2.3.3 beta 1 seems to run in 60fps no matter how I change my settings (changing different vsync methods or selecting "PAL").
|
Quote:
|
Quote:
|
It was a hint that "it does not work" is not a bug report and you missed to include something important :)
(logs and config file) |
1 Attachment(s)
I can not tick the box
|
Quote:
|
Quote:
I further noticed that when a custom refresh entry in combination with vsync(new) is used, it doesn't seem to bring the start of display in line with the vertical blank (which the automated does). This means that the user can end up with a horizontal steady tear in (for example) the middle of the screen, when he's using a custom refresh in combination with vsync(new), even if the custom refresh is close to the real refresh (for example when 'locking' an automated refresh value). |
There is any 64bit version of WinUAE 2.3.3 beta?
|
Quote:
|
Beta 2:
http://www.winuae.net/files/b/winuae_2330b2.zip - experimental joystick raw input support, enable using -rawhid command line parameter. - D3D blank screen problem should be really fixed now - empty winuae.ini now does exact same as -portable command line parameter - harddrive paths relative to win32.hardfile_path didn't work - config file full paths are converted to relative if path matches win32.xxx_path entries - ignore new displaydata vsync stuff if RTG mode is currently in use - Display panel new vsync refresh rate GUI really works now - uaescsi.device cd image on the fly switching was unreliable - uaescsi.device crash when switching images (I could only duplicate it with AROS CDFS) - AROS ROM updated |
Quote:
Quote:
As a suggestion, possibly you could add a "displaydata_pal_RTG" and a "displaydata_ntsc_RTG", for when matched only a selected set of gfx configs can be used as parameters? EDIT: apart from the above, the beta seems to work well. I like the option to enable RawInput :) |
2 Attachment(s)
The new v-sync method seems to be working for me, if I select no v-sync I see lots of screen tearing, but if I select v-sync (new) I see no screen tearing.
I used 'no buffering' and A500 quickstart. Graphics chip is "Mobile Intel(R) 915GM/GMS,910GML Express Chipset Family" which claims to be running in 50hz mode. I thought it might be interesting to see results for such an old chipset. |
Quote:
This needs some re-design.. (This was also in private version) EDIT: In other words, it only worked accidentally. |
All times are GMT +2. The time now is 04:23. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.