21 June 2011, 17:28 | #21 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Probably related to old unexplained d3d blank screen issue, switching modes usually fixes it.. ("Effect" in your screen shot happens because 3d objects are usually made from triangles and for some reason second triangle is missing)
|
21 June 2011, 18:03 | #22 |
cheeky scoundrel
Join Date: Nov 2004
Location: Spijkenisse/Netherlands
Age: 43
Posts: 6,978
|
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... |
21 June 2011, 19:03 | #23 |
I Identify as an Ewok
Join Date: Jul 2001
Location: North Lincolnshire
Age: 45
Posts: 2,356
|
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.
|
21 June 2011, 19:34 | #24 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
Does http://www.winuae.net/files/b/winuae.zip change anything in D3D problem? |
|
22 June 2011, 21:21 | #25 | |
I Identify as an Ewok
Join Date: Jul 2001
Location: North Lincolnshire
Age: 45
Posts: 2,356
|
Quote:
EDIT: Forgot to test DirectDraw mode! Display now looks better in WB although the mouse pointer is still missing. |
|
23 June 2011, 13:19 | #26 | ||
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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:
|
||
24 June 2011, 09:44 | #27 |
cheeky scoundrel
Join Date: Nov 2004
Location: Spijkenisse/Netherlands
Age: 43
Posts: 6,978
|
I wouldn't punch yourself. In my opinion forgetting to clear a buffer is an easier to make and harder to debug 'mistake' than bad pointer handling; its a piece of legacy that programmers using native languages will always have to carry around as a burden.
It may seem silly, but this is a true bastard. No brown paper bag for you mister |
28 June 2011, 09:10 | #28 |
Zone Friend
Join Date: Apr 2006
Location: Gothenburg/Sweden
Age: 48
Posts: 345
|
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").
|
28 June 2011, 09:46 | #29 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
|
28 June 2011, 10:02 | #30 |
Zone Friend
Join Date: Apr 2006
Location: Gothenburg/Sweden
Age: 48
Posts: 345
|
|
28 June 2011, 10:05 | #31 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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) |
28 June 2011, 10:29 | #32 |
Registered User
Join Date: Apr 2008
Location: France
Posts: 29
|
I can not tick the box
|
28 June 2011, 12:34 | #33 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
|
30 June 2011, 00:36 | #34 | |
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
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). |
|
03 July 2011, 17:19 | #35 |
Super Robot Pilot
Join Date: Dec 2007
Location: Modena (Italy)
Age: 49
Posts: 871
|
There is any 64bit version of WinUAE 2.3.3 beta?
|
04 July 2011, 20:25 | #36 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
|
05 July 2011, 20:58 | #37 |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
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 |
06 July 2011, 00:44 | #38 | ||
Registered User
Join Date: Jul 2008
Location: Netherlands
Posts: 485
|
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 |
||
06 July 2011, 01:58 | #39 |
Zone Friend
Join Date: Apr 2005
Location: London
Posts: 1,179
|
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. |
06 July 2011, 10:11 | #40 | |
WinUAE developer
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 49
Posts: 26,574
|
Quote:
This needs some re-design.. (This was also in private version) EDIT: In other words, it only worked accidentally. Last edited by Toni Wilen; 06 July 2011 at 17:57. |
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
WinUAE 2.5.1 beta series | Toni Wilen | support.WinUAE | 69 | 22 December 2012 10:22 |
WinUAE 2.3.2 beta series | Toni Wilen | support.WinUAE | 79 | 31 May 2011 19:39 |
WinUAE 2.3.0 beta series (was 2.2.1) | Toni Wilen | support.WinUAE | 229 | 22 September 2010 19:20 |
WinUAE 1.5.3 beta series | Toni Wilen | support.WinUAE | 58 | 09 November 2008 13:46 |
|
|