(02-26-2014, 02:16 AM)ExtremeDude2 Wrote: [ -> ] (02-25-2014, 07:08 PM)delroth Wrote: [ -> ]Might be https://code.google.com/p/dolphin-emu/is...fullscreen
If that is the case, could 4.0 be tested with dx9 to see if that works? (dx9 supports exclusive fullscreen right?)
D3D9 only uses exclusive fullscreen if 3d vision is enabled.
(02-26-2014, 03:51 AM)neobrain Wrote: [ -> ] (02-26-2014, 02:16 AM)ExtremeDude2 Wrote: [ -> ] (02-25-2014, 07:08 PM)delroth Wrote: [ -> ]Might be https://code.google.com/p/dolphin-emu/is...fullscreen
If that is the case, could 4.0 be tested with dx9 to see if that works? (dx9 supports exclusive fullscreen right?)
D3D9 only uses exclusive fullscreen if 3d vision is enabled.
Well uh, that is interesting
I did some more testing, and "keep window on top" only enables g-sync for OpenGL. When using dx11, none of the options available will engage g-sync.
(06-19-2014, 09:37 PM)Armada Wrote: [ -> ]Try this build which includes exclusive fullscreen support: https://dl.dolphin-emu.org/prs/pr-506-do...est-x64.7z
Use the D3D backend and make sure "Render to Main Window" is disabled.
Since you code Media Player Classic, maybe you understand more about NTSC / PAL
for Dolphin is running NTSC Games at 60FPS rather then the correct 60000/1001 (around 59.94 FPS)
Every PAL Game is also producing this warning
"PAL game is trying to use incorrect (NTSC) field ordering"
Fixing PAL/NTSC would greatly benefit Gsync and TV users.
(06-19-2014, 11:26 PM)Gir Wrote: [ -> ] (06-19-2014, 09:37 PM)Armada Wrote: [ -> ]Try this build which includes exclusive fullscreen support: https://dl.dolphin-emu.org/prs/pr-506-do...est-x64.7z
Use the D3D backend and make sure "Render to Main Window" is disabled.
Since you code Media Player Classic, maybe you understand more about NTSC / PAL
for Dolphin is running NTSC Games at 60FPS rather then the correct 60000/1001 (around 59.94 FPS)
Every PAL Game is also producing this warning
"PAL game is trying to use incorrect (NTSC) field ordering"
Fixing PAL/NTSC would greatly benefit Gsync and TV users.
Where is it producing that warning? The emulation log?
(06-19-2014, 11:37 PM)Armada Wrote: [ -> ] (06-19-2014, 11:26 PM)Gir Wrote: [ -> ] (06-19-2014, 09:37 PM)Armada Wrote: [ -> ]Try this build which includes exclusive fullscreen support: https://dl.dolphin-emu.org/prs/pr-506-do...est-x64.7z
Use the D3D backend and make sure "Render to Main Window" is disabled.
Since you code Media Player Classic, maybe you understand more about NTSC / PAL
for Dolphin is running NTSC Games at 60FPS rather then the correct 60000/1001 (around 59.94 FPS)
Every PAL Game is also producing this warning
"PAL game is trying to use incorrect (NTSC) field ordering"
Fixing PAL/NTSC would greatly benefit Gsync and TV users.
Where is it producing that warning? The emulation log?
Seems so. I only have one PAL game that does this. This is from a demo version of 1080 Avalanche that is a PAL version when unpacked from one of the multigame demo discs:
Code:
46:43:274 Boot\Boot.cpp:194 N[BOOT]: Booting N:\ROMs\Gamecube/demos/Ver 12 2003/zz_1080_game.gcm
46:43:290 HLE\HLE_OS.cpp:46 N[OSREPORT]: 81200500->81300000| Apploader Initialized. $Revision: 31 $.
46:43:290 HLE\HLE_OS.cpp:46 N[OSREPORT]: 8120051c->81300000| This Apploader built Sep 5 2002 05:58:53
46:43:311 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
46:43:465 PowerPC\SignatureDB.cpp:126 E[HLE]: Wrong size! Found __DBExceptionDestination at 800e5734 (size: 0000002c instead of 00000010)!
46:43:465 PowerPC\SignatureDB.cpp:126 E[HLE]: Wrong size! Found SystemCallVector at 800e0c6c (size: 00000084 instead of 00000020)!
46:43:465 PowerPC\SignatureDB.cpp:126 E[HLE]: Wrong size! Found OSSwitchFPUContext at 800de458 (size: 000000cc instead of 00000084)!
46:43:465 PowerPC\SignatureDB.cpp:126 E[HLE]: Wrong size! Found OSLoadContext at 800ddff0 (size: 000000e0 instead of 000000d8)!
46:43:465 PowerPC\SignatureDB.cpp:126 E[HLE]: Wrong size! Found Reset at 800dfc68 (size: 000000b8 instead of 00000070)!
46:43:465 PowerPC\SignatureDB.cpp:126 E[HLE]: Wrong size! Found ExternalInterruptHandler at 800df444 (size: 00000068 instead of 00000050)!
46:43:470 D3DBase.cpp:112 N[Video]: Successfully loaded D3DCompiler_42.dll. If you're having trouble, try updating your DX runtime first.
46:43:561 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: << Dolphin SDK - EXI release build: Sep 5 2002 05:33:04 (0x2301) >>
46:43:562 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: << Dolphin SDK - SI release build: Sep 5 2002 05:33:08 (0x2301) >>
46:43:567 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]:
46:43:567 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: Dolphin OS $Revision: 58 $.
46:43:567 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: Kernel built : Sep 5 2002 05:32:39
46:43:568 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: Console Type : Development HW3 (10000006)
46:43:568 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: Memory 24 MB
46:43:568 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: Arena : 0x802b0f60 - 0x817fcee0
46:43:569 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: << Dolphin SDK - OS release build: Sep 5 2002 05:32:39 (0x2301) >>
46:43:573 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
46:43:575 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: << Dolphin SDK - DVD release build: Sep 5 2002 05:34:06 (0x2301) >>
46:43:576 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: << Dolphin SDK - VI release build: Sep 5 2002 05:33:13 (0x2301) >>
46:43:577 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: << Dolphin SDK - PAD release build: Sep 5 2002 05:34:02 (0x2301) >>
46:43:577 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: -NTSC VERSION-
46:43:578 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: VIConfigure(): Tried to change mode from (1) to (0), which is forbidden
46:43:578 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: in "vi.c" on line 1884.
46:43:578 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]:
46:43:578 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: Address: Back Chain LR Save
46:43:579 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: 0x802b0de0: 0x802b0e70 0x800de660
46:43:579 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: 0x802b0e70: 0x802b0ee8 0x800ec808
46:43:579 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: 0x802b0ee8: 0x802b0f20 0x8007de98
46:43:579 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: 0x802b0f20: 0x802b0f40 0x80039f08
46:43:580 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: 0x802b0f40: 0x802b0f48 0x80039b14
46:43:580 HW\EXI_DeviceIPL.cpp:281 N[OSREPORT]: 0x802b0f48: 0xffffffff 0x80003274
46:43:582 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
46:43:586 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
46:43:599 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
46:43:619 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
46:43:639 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
46:43:659 HW\VideoInterface.cpp:530 W[VI]: PAL game is trying to use incorrect (NTSC) field ordering
Then it just repeats the last line endlessly until you close the game.
(EDIT: Off topic side note while I'm at it: This demo includes an .ELF file with function symbols, not sure if the final version does this too. Would this be helpful for anything?)
(06-19-2014, 11:37 PM)Armada Wrote: [ -> ] (06-19-2014, 11:26 PM)Gir Wrote: [ -> ] (06-19-2014, 09:37 PM)Armada Wrote: [ -> ]Try this build which includes exclusive fullscreen support: https://dl.dolphin-emu.org/prs/pr-506-do...est-x64.7z
Use the D3D backend and make sure "Render to Main Window" is disabled.
Since you code Media Player Classic, maybe you understand more about NTSC / PAL
for Dolphin is running NTSC Games at 60FPS rather then the correct 60000/1001 (around 59.94 FPS)
Every PAL Game is also producing this warning
"PAL game is trying to use incorrect (NTSC) field ordering"
Fixing PAL/NTSC would greatly benefit Gsync and TV users.
Where is it producing that warning? The emulation log?
View > Show Log , in Log Configuration select Warning Verbosity
(in a PAL-50 Game)
e.g. Resident Evil 3
http://s9.postimg.org/pkgwln927/loh.jpg
Seems like it's really a problem with the game, the emulator is automatically applying a fix for it. It shouldn't affect G-Sync and it's unrelated to the video backend which I'm focusing on.
If it is causing issues for you please make a new ticket on the bug tracker.