unofficial LaunchELF v4.42

[Bootlegninja]

It is not uLE to blame. I can confirm with a USA setup that it is the quality of the component cables.

Test 1: V7 PS2, component cable, mod chip disabled, uLE 4.28, FMCB 1.6b Test 51, USA FF8 (non greatest hits) pressed original set.

Displays magenta in white areas

Test 2: Same setup only composite cables instead.

Displays as it should.

[urbigbro]

It is not uLE to blame. I can confirm with a USA setup that it is the quality of the component cables.

I have also tested the before mentioned games on my s-video cable and the colors are correct.
I'm not sure if we can blame the quality of the component cable in my case, as my games work fine with the same cable when not started from ule's PS2disc function. The cable is shielded and is not corroded, bent, or damaged in any way. It also happened on a different high quality component cable.

So far all the games I have tested have this problem only when using component cables.

My PS2's component video out BIOS setting is set to Y Cb/Pb Cr/Pr.

[Bootlegninja]

I have also tested the before mentioned games on my s-video cable and the colors are correct.
I'm not sure if we can blame the quality of the component cable in my case, as my games work fine with the same cable when not started from ule's PS2disc function. The cable is shielded and is not corroded, bent, or damaged in any way. It also happened on a different high quality component cable.

So far all the games I have tested have this problem only when using component cables.

My PS2's component video out BIOS setting is set to Y Cb/Pb Cr/Pr.

Aye. Same results here. I can play the PS1 games normally with correct colors when started via Sony browser (inner or outer)

And my cable is fairly new, and not really moved around too much where it can develop shorts. naturally my BIOS setting is Y Cb/Pb Cr/Pr as well since my HDTV only accepts that signal.

If I had a second component cable of a different brand, I could do further testing, but I'm running short of equipment. my v10 decided to partially crap out and I've decommissioned it.

[dlanor]

Aye. Same results here. I can play the PS1 games normally with correct colors when started via Sony browser (inner or outer)

That is the significant fact which makes me unwilling to accept cable quality as being the sole cause of this problem, tempting as it may seem to exonerate uLE from all blame. But fixing the real problem is more important than placing blame.

And my cable is fairly new, and not really moved around too much where it can develop shorts. naturally my BIOS setting is Y Cb/Pb Cr/Pr as well since my HDTV only accepts that signal.

Those are all valid points, and if it had truly been just a case of bad quality cables, then I would also have expected varying forms of colour distortion. Not this consistent shift towards magenta that several people have reported (indicating a lack of green in the colour mix).

If I had a second component cable of a different brand, I could do further testing, but I'm running short of equipment. my v10 decided to partially crap out and I've decommissioned it.

IMO we already have enough facts to dismiss the theory about cable quality itself causing this problem, as several users (including yourself) have verified that the colours are perfect when launching the same PS1 games by traditional methods.

I think we can also assume that the description jimmikaelkael gave me of how the OSDSYS invokes PS1DRV was correct, and since it works perfect for myself and some other users it also seems that I correctly implemented the similar invocation in MISC/PS2Disc. But there is one other factor not included in any of the things I mentioned, and which can still cause this weird behaviour for 'component' signal users.

That missing factor is some as yet unknown detail in the initialization of the video hardware, which the PS1DRV driver does not include itself, as it 'knows' that this initialization has already been done by the code that calls PS1DRV. An assumption which is no longer valid when the code is called from a different runtime environment than the OSDSYS that normally launches PS1DRV.

If we knew which detail in the initialization it is that can cause this 'magenta tint' for component outputs, then we should be able to fix it in the PS1DRV launch of uLE, to make the initial conditions of that launch more similar to the conditions obtaining when OSDSYS launches PS1DRV. But this is something I can't even try to experiment with myself, as I do not have the necessary hardware to see the results. With the RGB signals used for my PAL TV sets I never get this colour problem, so I'd get no visual feedback on any experiments I'd try for affecting only component outputs.

Best regards: dlanor

[katananja]

Weird, as that final word doesn't follow the normal pattern of having a value assigned to it. But I suppose it might just be used as a 'flag' then. (flagging use of subchannels ?)

The SUB at the end look like some kind of "EOF" because is binary and when i post here will show a strange character.

I see, so the disc to be tested is not inside the tray during the startup of uLE.
And I assume that this implies that you boot your console with empty tray.

Normally i boot with empty tray, but i have done tests in both ways with/without disc in.

But what then about the "Disc Control" setting of uLE ?
This needs to be ON for reliable disc access,
but needs to be OFF for reliable booting with empty tray...
(Not uLE's fault, as this is mainly due to Sony's console design.)

That could be what's messing up your 'PS2Disc' PS1 launches.

I'd be interested to know your results if you set "Disc Control: ON" in uLE, insert one of those failing PS1 games in the tray, and then reboot and perform the test again. If my hunch is correct most of the games that failed for you earlier will work when launched this way.

Well, my console doesn't like "Disc Control ON" because it shows a dozen problems with it, but you asked for it :

Modchip ON
- It doesn't detect/boot PS2 discs, CD or DVD.
- It doesn't detect/boot PS1 Discs.
- Controls get crazy, if you press "down" on time it jumps 10 lines or more, is impossible to select one item.
- If you select MISC/PS2Disc and press "O" one time has the effect of pressin the button a dozen times, showing the error readSystemCnf Failed.
- If you turn the PS2 ON with the tray open, and use Matrix DEV1 (press and hold R1) uLE will not boot until you close the tray.
- If you go to Configuration and try to turn Disc Control to OFF, it takes more than 2 minutes to save. And if you keep pressing any button PS2 will display this nice screen that i don't know what is it:

NB: This does not necessarily mean that you must have the right disc in the tray before starting the console each time. "Disc Control: ON" only needs some disc, regardless of which it is. And when you have booted and decided what disc you want to test next, you can just eject the old disc and insert the new one.

Also, the caching error I mentioned earlier will not occur if you have not read the SYSTEM.CNF file (like in uLE's TextEditor, or by copying it) before replacing the old disc with the new one to be tested.

Best regards: dlanor

In my case messing with "Disc Control" make things worse, i've never seen a screen like that before....

[TnA]

That missing factor is some as yet unknown detail in the initialization of the video hardware,

I think so, too.


I have a few question, to those who have problems.
Are you using FMCB, to boot ule?
Did you also tested it with Chip-DEV.1-Mode?
Did you also tested to boot your ule from disc (through OSD, or not...), change to the PS1-Disc and than try to run the PS2Disc-Feature?

Btw.: Is the name "PS2Disc" still applicable?

[katananja]

I have a few question, to those who have problems.

Shoot.

Are you using FMCB, to boot ule?

I've tested both ways, with and without it.

Did you also tested it with Chip-DEV.1-Mode?

Yes

Did you also tested to boot your ule from disc (through OSD, or not...), change to the PS1-Disc and than try to run the PS2Disc-Feature?

I did not boot uLE from disc, but i've boot from OSD with the same results.

Btw.: Is the name "PS2Disc" still applicable?

I think "BootDisc" will be more appropriate to represent the intention to boot PS1/PS2/Whatever discs you have there.

[TnA]

I've tested both ways, with and without it.

Yes

So you tested it with and without FMCB (I guess, with "without FMCB" you mean with DEV.1).

I did not boot uLE from disc, but i've boot from OSD with the same results.

From OSD? With FMCB?
That wouldn't make any difference. If it didn't run properly through FMCB-Core/Splash-screen, than it also won't through the OSD (unless there is a bug in pad-mapping, or something that I don't mind/thought about yet...).

I meant from disc through OSD, or fastboot (both with FMCB).
...and through OSD from Disc, without FMCB.

I think "BootDisc" will be more appropriate to represent the intention to boot PS1/PS2/Whatever discs you have there.

Well,... I guess so too, but it doesn't support ESR-Discs, or DVD-Video and ule is in no relation to other apps (directly) and dlanor and E P most probably won't blow up the ELF-Size for this (I assume dlanor also wants to use ule with DMS4-DEV3 so no "unnecessary features". ).
"PS1-/PS2-Disc" would be enough.

Well,... I don't mind. It's just a name,...

[katananja]

So you tested it with and without FMCB (I guess, with "without FMCB" you mean with DEV.1).

Yes, with and without FMCB. When FMCB is off i use DEV-1 to boot uLE.

From OSD? With FMCB?
That wouldn't make any difference. If it didn't run properly through FMCB-Core/Splash-screen, than it also won't through the OSD (unless there is a bug in pad-mapping, or something that I don't mind/thought about yet...).

Yes at times that I've made tests with FMCB, i have tried many ways you can imagine, with DEV-1, with FMCB, with chip on/off, clap my hands two times, do a smal jump and press start doesn't work either. Up, Up, Down, Down, Left, Right, Left, Right, A, B, Start did not work also

I meant from disc through OSD, or fastboot (both with FMCB).
...and through OSD from Disc, without FMCB.

Did all that dude, fastboot on/off, disc control on/off, nothing helps.

Well,... I guess so too, but it doesn't support ESR-Discs, or DVD-Video and ule is in no relation to other apps (directly) and dlanor and E P most probably won't blow up the ELF-Size for this (I assume dlanor also wants to use ule with DMS4-DEV3 so no "unnecessary features". ).
"PS1-/PS2-Disc" would be enough.

Well,... I don't mind. It's just a name,...

I mean, is obvious enough that the intention is to boot PS2/PS1 discs and not ESR-Discs, VCD, DVD, CD-G, PhotoCD(Kodak), Windows 98/ME/2000/XP/2003/VISTA Discs, MACOS install discs, 3DO, MegaCD, Saturn, DreamCast.....

I know that there is people that stupid, but I think the "BootDisc" name is straight forward, there is no need to be that specific.

[TnA]

Are you kidding me?

But,... lol

I agree with the last sentence you mentioned.
Not thought about it,...