GS Mode Selector: Development & Feedback

[doctorxyz]

Hello everybody,

Master PM some hints... So as a limited sorcerer's apprentice I am studying them (respecting my time and skill limits)... Well, patience is everything!

-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x

I opened PS2ZoneLoader's "bootmaster.elf" on PS2DIS and discovered n useful labels.

So I picked up opcodes from some labeled functions and looked similar for hex sequences into HDLoader ELF file.

I was surprised that MIPS assembly source code from both (PS2ZoneLoader and HDLoader) are identical in some functions - for instance, "memcpy" and "findSyscallTable". Note that using these HDLoader's functions could make my code smaller.

I intend to mod "installPNSelector", "installDebugExceptionHandler", "myGsSetCrt" functions from PS2ZoneLoader, and inject them some address on HDLoader ELF.

But I still do not know where is the best place.

Maybe I need to sacrifice some HDLoader GUI message data area to put those. Or maybe not. It depends on the result of my research.

Suggestions are welcome!

[jepjepjep]

I really hope you get this to work doctorxyz. Since I can't be of any technical help, I just thought I would post to cheer you on.

[dlanor]

I was surprised that MIPS assembly source code from both (PS2ZoneLoader and HDLoader) are identical in some functions - for instance, "memcpy" and "findSyscallTable".

There's really nothing surprising about it.

Though HDLoader eventually became a commercial project, it started out as any other homebrew project, and I assume that Sjeep used the standard ps2dev.org libs throughout, except for those sections he had to code entirely himself, as being unique to HDL needs.

Standard functions like those you mentioned here will be fully identical for all homebrews using the same generation of ps2dev libs, except for minor deviations in compile-time register assignments (also affected by optimization settings).

Best regards: dlanor

[doctorxyz]

@all
Work in progress... I embeed PS2ZoneLoader core into a byte array and I trying to make my testing ELF install and activate it, letting user decide to force NTSC/PAL/VGA modes before launch uLE from mc. If this test succeed, I go further to launch HDL from mc (of course, without destroying my force GS Mode routine).

@jepjepjep

I just thought I would post to cheer you on.

Thanks for your encouragement words.

@dlanor

Though HDLoader eventually became a commercial project, it started out as any other homebrew project, and I assume that Sjeep used the standard ps2dev.org libs throughout, except for those sections he had to code entirely himself, as being unique to HDL needs.

I found this on Net
"(...) About 5% of the HDLoader code is made up of open source code from ps2dev.org including ps2lib, libhdd, ps2drv etc
(all of which I have had a part in the development of anyway) (...)"
Source: "Hdloader - The Real Story"(by malloc) -> http://www.maxconsole.net/?mode=news&newsid=3249

[doctorxyz]

Friends,
I got it!!! Now I must make some improvement and clean up on code. Soon I will post more info here.
BR,

[TnA]

Wow. That was fast.
You got InGame-V-Mode-Force to work??

Btw.: The V-Mode-Patch (in HDL) for other modes than PAL & NTSC alone, is worth a new patch.

[doctorxyz]

You got InGame-V-Mode-Force to work??

Last night I got GT4 start on HDTV 1080p 30 Hz mode (since it was just a proof of technology test, I was not worried about interlace on/off and field/frame parameters... I was worried abot that this stuff work!)

Btw.: The V-Mode-Patch (in HDL) for other modes than PAL & NTSC alone, is worth a new patch.

Certainly. But in HDL I first most unterstand how to hook setupthread correctly. Because should force GS mode only after boot games, and not before that. The ideal situation was that I could select specific parameters for each game in HDL GUI (like a compatibility mode). But I am afraid I cannot all this stuff alone.

-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-

Quotes originally from http://www.psx-scene.com/forums/show...6&postcount=13

It would be interesting for the OSD first.
-Configureable x&y-axis
-Configurable Stretching
-Configurable Interleacing, or at least a mode-choice for all vga and hdtv-modes would be cool and possible.

Yes, I would like evolve my OSD part, using PAD buttons to setup
-x&y-axis -> DX and DY
-Stretching -> MAGH and MAGV
-Interlacing -> Interlace on/off
-Frame/Field -> Frame/Field -> Frames Per Second has twice Hz frequency than Field ones (I suppose)
- GS Modes (all possible)

Or at least a mode-choice for all vga and hdtv-modes would be cool and possible.

A set of pre-defined choices could be a good idea. Since many people do not understand all these parameters settings... Me, for example... ;-)

I don´t know if it will still match the loader with the current compression (with NRL it should match and I didn´t saw any strange results, while my loader-tests with it...).

What does "NRL" stands for?

The other way around, there is only the choice for a bigger dvdelf (but for an official FMCB-release, there MUST be a small loader available so a choice in the installer for big or small-loader must be there, IF it would need a bigger dvdelf...

(If I understood you well) I think the core part is not so much bigger.
Since I am not a good coder and new into psx-scene, it could be a much more better idea share my sources to some of FCMB contributors to inject GS Force Mode code in a better way to FCMB.

Simple idea: If the dvdelf, which the installer found [be it in ROM, or from INJECT-Folder] offers enough space to embed the big-loader, it request wether to install the big, or the small loader after the user selected one of both installer-options [multi- or normal-install].).

I did not undertand so much what you wrote above... Are those all FCMB's terminologies? Would you mind to give a complementary explanation?

Btw.: I hope your thread/project continues, so we can have perfect fullscreen and "high-res" for games, homebrew and maybe other stuff... on most if not all possible combinations of console-/cable-/tv-sets.

I would be very happy to acomplish that...! But it is hard, due to my restrictions of time - I have a family and a job ;-) - and knowledge - I am just trying to learn the answers for my questions.

[doctorxyz]

Hi,

I want to accomplish at least PHASE 1 from my TO DO" list (could be changed), before launch a minimal and acceptable release.

PHASE 1
a) Make my own myGsSetCrt function (let's call it "ModdedSetGsCrt"), based on original one from PS2ZoneLoader:
--> Add Interlace, Mode and Field input parameters directly on its opcodes.
--> Re-compile it.
--> Take its opcodes.
--> Put this function into a byte array on a C specific file.

b) Improve InstallGSModeSelector
--> Copy ModdedSetGsCrt to Kernel RAM Area, right after PS2ZoneLoader core
--> Store Interlace, Mode and Field input parameters directy into ModdedSetGsCrt opcodes.

PHASE 2
Test yposHandler "as is" with many values, in order to have sure that ypos fix really work.

PHASE 3
a) Make my own yposHandler function (let's call it "DisplayHandler"), based on original one from PS2ZoneLoader:
- Add DX, DY, MAGH and MAGV input parameters directly on its opcodes.

b) Improve InstallGSModeSelector
--> Copy DisplayHandler to Kernel RAM Area, right after PS2ZoneLoader core and ModdedSetGsCrt.
--> Store DX, DY, MAGH and MAGV parameters directy into DisplayHandler opcodes.

PHASE 4
Improve DisplayHandler
a) Add automatic fix for MAGH and MAGV values, based on
----> DW and DH ones (these are also trapped by handler, so we can use it)
----> Interlace, Mode and Field input parameters (previously stored on ModdedSetGsCrt opcodes)

PHASE Z (Alternate / Advanced)

From a set of pre-defined and/or custom list, choiced by users on a GUI (like Xploder HDTV Player, but better), give Magic Numbers to setup parameters to ModdedSetGsCrt (Interlace, Mode and Field) and DisplayHandler (DX, DY, MAGH and MAGV).

Maybe, on the future I can use some of precious hints from ffgriever (hook setupthread, etc.) to activate patch only after an game be selected from HDL list.
I already compiled some documentation about how do it, but I am not prepared to do it yet... It is much information to my limited mind... ;-)

[TnA]

Last night I got GT4 start on HDTV 1080p 30 Hz mode (since it was just a proof of technology test, I was not worried about interlace on/off and field/frame parameters... I was worried abot that this stuff work!)

I hope to see your efforts there.
May the project continue.

Certainly. But in HDL I first most unterstand how to hook setupthread correctly. Because should force GS mode only after boot games, and not before that. The ideal situation was that I could select specific parameters for each game in HDL GUI (like a compatibility mode). But I am afraid I cannot all this stuff alone.


-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-

Quotes originally from http://www.psx-scene.com/forums/show...6&postcount=13

Hm,... The HDL-Patches might gave some examples how to add such an extra-button in compatibility-Menu.
But even cooler would be a global option, which can be changed at any time (while in HDL-GUI/Game-List), but maybe even harder.

But I like the idea very much.
I´m sure, there are more people interested in it out there two,...

Stretching-Capabilities and special V-modes, like PAL60, or 576p would be cool if possible.
x&y-position also.

I think many people would like playing their games in high-res (not limited to internal HD, but also USB-HD, or ESR-Discs).
All efforts here can improve some stuff&projects in the scene.

Yes, I would like evolve my OSD part, using PAD buttons to setup
-x&y-axis -> DX and DY
-Stretching -> MAGH and MAGV
-Interlacing -> Interlace on/off
-Frame/Field -> Frame/Field -> Frames Per Second has twice Hz frequency than Field ones (I suppose)
- GS Modes (all possible)


A set of pre-defined choices could be a good idea. Since many people do not understand all these parameters settings... Me, for example... ;-)

That is like it is yet, but a "configurable word" like "PAL", "NTSC" or "AUTO" could be "MANUAL", which let the loader/cnf-parser search for manually defined options.

What does "NRL" stands for?

NRL-Packer from Neureal is an ELF-Packer for PS2 64K-Intros.
It showed some strange results, if tools like uLE where compressed with it.

The FMCB 1.8-Loader compressed with NRL didn´t gave me any strange results.
Maybe because FMCB tries to start in a clear state, or because the compressed loader is smaller than 64k, or whatever reasons it have.
No new issues (which weren´t there with the old compression) to report there yet.

(If I understood you well) I think the core part is not so much bigger.
Since I am not a good coder and new into psx-scene, it could be a much more better idea share my sources to some of FCMB contributors to inject GS Force Mode code in a better way to FCMB.

You can send it to someone, or attach it here simply.
If I remember correctly, this part of code is identical to FMCB 1.7, but I´m not sure about it (didn´t looked at it yet).

I did not undertand so much what you wrote above... Are those all FCMB's terminologies? Would you mind to give a complementary explanation?

Yes they are.

The dvdelf.bin is the encrypted DVD-Player from PS2s ROM.
It is used to generate a valid KELF-Header.
So we are limited to the filesize of this file and how many code could be injected into a dvdelf.bin.
Old "FAT" PS2s usually have bigger dvdelfs, while smalls have the 75KB-Mini-DVDPLx (DVDELFs, which are only ~74KB in size and only 60,9KB could be injected...)

The NRL-Packer packs the normal loader down to 43,4KB, much better than PS2-Packer but how it can conflict with software isn´t known (at least I didn´t had the reported problems, when I only compressed the FMCB-Loader with it... ).

If the loader which should be embedded crosses the mark of 60,9KB, a bigger DVDELF simply must be used.
This is wasting space and loading-time on mc, but also gives a huge freedom to expand the loader or embed big ELFs.

Sorry, to be that short on this part.
dlanor explained it a few time in detail here and also neme postet some very detailed posts, also how the xoring of the injected code works to create a valid MC-KELF.

KELF=Krypto ELF (the OSD- or DVD-Player-Upgrades normally...).

I would be very happy to acomplish that...! But it is hard, due to my restrictions of time - I have a family and a job ;-) - and knowledge - I am just trying to learn the answers for my questions.

I´m sure, there are a few people out there willing to help ya and contribute.


Edit: You "beat" me,... 1 minute.

[urbigbro]

Alright! Call the doctor, he's got the cure

Here's another possibility, perhaps Ragnarok could integrate this into the "Dash" functionality he is working on. I haven't seen him on here since the last time this forum went down thought

Thanks for doing this project doc xyz, hopefully some more of the "big gun" programmers see you efforts and help you out!