15,188
edits
 |
Progress Continues
We've already had 21455 updates since Dolphin 5.0. Keep up with Dolphin's continuing progress through the Dolphin Blog: August, September, and October 2023 Progress Report. |
 |
The Dolphin Emulator Wiki needs your help! Dolphin can play thousands of games, and changes are happening all the time. Help us keep up! Join in and help us make this the best resource for Dolphin. |
Template talk:Problems/GC Widescreen Auto: Difference between revisions
Jump to navigation
Jump to search
Template talk:Problems/GC Widescreen Auto (view source)
Revision as of 22:29, 6 August 2017
, 6 August 2017Username rename (Jhonn => mbc07)
(Username rename (Jhonn => mbc07)) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 11: | Line 11: | ||
:Widescreen notes have been purged from these titles. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 11:52, 2 December 2015 (CET) | :Widescreen notes have been purged from these titles. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 11:52, 2 December 2015 (CET) | ||
Reply 1: As for the in-game widescreen option for battalion wars; only black bars are added to the menus and cut-scenes. In game levels are displayed in widescreen see: | |||
https://forums.dolphin-emu.org/Thread-gc-battalion-wars--26055?pid=430278#pid430278 [[User:Sam3|Sam3]] 17:57, 10 December 2016 (GMT) | |||
=== Auto + Force 16:9 === | === Auto + Force 16:9 === | ||
| Line 21: | Line 24: | ||
I've updated these titles to indicate "Force 16:9". [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 11:46, 2 December 2015 (CET) | I've updated these titles to indicate "Force 16:9". [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 11:46, 2 December 2015 (CET) | ||
: We should investigate those games further before setting force. For example, the menus of those games may still be rendered in 4:3 even with widescreen enabled (like Zelda Wind Waker with AR code). Using Auto in that case would seamlessly switch between 4:3 and 16:9 when needed, while in Force mode the menus would be stretched... - [[User: | : We should investigate those games further before setting force. For example, the menus of those games may still be rendered in 4:3 even with widescreen enabled (like Zelda Wind Waker with AR code). Using Auto in that case would seamlessly switch between 4:3 and 16:9 when needed, while in Force mode the menus would be stretched... - [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 16:50, 2 December 2015 (CET) | ||
::OK, got around to trying these tonight. First off we had been confused on the particular settings, I revised things to align with the actual settings. "Anamorphic" works fine with Auto AR, the "16:9" does not. "16:9" option is weird and seems to more or less output a 16:9 image on a 4:3 display. It outputs incorrectly /w Force 16:9, being stretched to thin. It outputs correctly with Force 4:3, but has black bars on all 4 sides on a widescreen display, so it's not useful. With /w auto it depends on the order you enable things, if "16:9" is activated first it outputs like Force 4:3, but if you enable "Anamorphic" first and then "16:9" it outputs like Force 16:9. I'm going to swap them back to recommending Auto, and leave a note providing details of each in game settings, since I don't think we want a third template just for these two. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 07:03, 3 December 2015 (CET) | ::OK, got around to trying these tonight. First off we had been confused on the particular settings, I revised things to align with the actual settings. "Anamorphic" works fine with Auto AR, the "16:9" does not. "16:9" option is weird and seems to more or less output a 16:9 image on a 4:3 display. It outputs incorrectly /w Force 16:9, being stretched to thin. It outputs correctly with Force 4:3, but has black bars on all 4 sides on a widescreen display, so it's not useful. With /w auto it depends on the order you enable things, if "16:9" is activated first it outputs like Force 4:3, but if you enable "Anamorphic" first and then "16:9" it outputs like Force 16:9. I'm going to swap them back to recommending Auto, and leave a note providing details of each in game settings, since I don't think we want a third template just for these two. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 07:03, 3 December 2015 (CET) | ||
| Line 28: | Line 31: | ||
=== Inconsistent Widescreen === | === Inconsistent Widescreen === | ||
Just a heads up, I asked JMC47 and he tested various of those games. Something he said that I think it's important to note somewhere is that "a lot of these games won't change into widescreen until something using a widescreen viewport shows up (3D graphics, usually. Such as the character models in Soul Calibur II's menus.)". [[User: | Just a heads up, I asked JMC47 and he tested various of those games. Something he said that I think it's important to note somewhere is that "a lot of these games won't change into widescreen until something using a widescreen viewport shows up (3D graphics, usually. Such as the character models in Soul Calibur II's menus.)". [[User:mbc07|mbc07]] ([[User talk:mbc07|talk]]) 05:30, 29 November 2015 (CET) | ||
Yes, many of these titles provide widescreen output inconsistently. This usually seems related to the underlying assets not being suited for 16:9 display. I'm not clear we should worry about this. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 10:16, 2 December 2015 (CET) | Yes, many of these titles provide widescreen output inconsistently. This usually seems related to the underlying assets not being suited for 16:9 display. I'm not clear we should worry about this. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 10:16, 2 December 2015 (CET) | ||
Should boil down the above to some notes to include in the templates description. [[User:Kolano|Kolano]] ([[User talk:Kolano|talk]]) 21:04, 9 December 2016 (CET) | |||