Angelgdl
Forum Replies Created
-
AuthorPosts
-
Thank you so much for the update notification
Hello, the firmware was updated 3 weeks ago, New Firmware 1.21: finalize Lumacode support and fix SD profile save/load (That was the problem I had on N64 a while ago, I’m glad they fixed it.) https://github.com/marqs85/ossc/releases/tag/v1.21
Could you please update the online profiles to version 1.21?
Hey, good tip! I applied it in OSSC and it worked. I reset the profile and it fixed it. I think there must be a conflict between the optimal timming profiles for FirebrandX on N64 and this new firmware. I should clarify that I converted them on the website for this new firmware, so I don’t know what the conflict could be, but at least the reset profile worked for me. In case anyone else has the same problem, this is the solution.
Thank you so much for your support, it was truly very helpful.
Update: After turning OSSC off and on again with the default profile, the split-screen issue occurred again. The solution was the same: reset the profile. However, I found that when I re-enabled the shadow mask, the screen went black. Another issue with this strange bug is that when I reset the profile and everything returns to normal, the resolution shows 480p, but in the “line multi-option” menu, trying to change the 480p line doesn’t do anything; it has no effect on any of the options.
https://drive.google.com/file/d/1JOPaKbva5NsDGzH7SWlhsyHhPVszeW1K/view?usp=drivesdk
The information displayed on the screen is limited, but it does say that the image resolution is 1024×490.
https://drive.google.com/file/d/14mHCn_Xy4bdl8d0DgCVbUTqqW5EabfRG/view?usp=drivesdk
A small step forward with my problem: I’ve managed to get the black screen to display something. I had to disable “ultra hd deep color” on my LG UH8500 TV. Now it shows the image, but it’s duplicated in two parts on the screen.
Images:
https://drive.google.com/file/d/1OKRtVWbaF7Re8lyqE3349kjAO98WY8cR/view?usp=drivesdk
https://drive.google.com/file/d/1MvbLvSFMJGF3YjYwzSEsoVDvvQ55LuwA/view?usp=drivesdk
https://drive.google.com/file/d/1XZUHOld4m6q74lxc27eVrTMolH8aq7Ow/view?usp=drivesdk
https://drive.google.com/file/d/18SZRg9_uI3-oJgA2NW0hKgdGomKviY_4/view?usp=drivesdk
-
This reply was modified 2 months, 1 week ago by
Angelgdl.
The signal only disappears on the TV; the OSSC continues to function and display information. The information displayed is: AV1_RGBS 525-i 15.73kHz 59.94Hz
As additional information, I use an N64 with the RGB mod, and when the resolution changes and the problem occurs, I go into the OSSC menu and none of the resolution or profile options that worked before are working. I repeat, this didn’t happen in the previous version, 1.12; back then, the resolution conversion was automatic and there were no black screen problems.
Okay, I’ll use Star Wars Racer as an example. The game starts in 263p with a screen that says “expansion pack detected,” and it goes all the way to the main menu. When I select any option to start playing, the resolution changes to 525i and the signal drops. I turn the OSSC off and on to check if it was a bug or something, and I can only hear the sound, but the screen is black. This similar thing happens with other games that constantly change resolution between the menu and gameplay with the expansion pack.
Hello, I hope you’re having a good day. I have a problem: how do I launch, or rather, how do I install the second firmware in OSSC 1.20?
I’m having problems with four N64 games that worked fine on firmware 1.12. The games are ISSS 2000, Hybrid Heaven, Star Wars EP1 Racer, and Star Wars Rogue Squadron.
These games use the expansion pack, which improves the resolution, but this results in a black screen during conversion. This didn’t happen with the previous firmware.New Firmware 1.20 for OSSC “normal” more info here: https://retrorgb.com/ossc-firmware-update-v1-20.html
It was recently updated on March 26th, and I thought I’d be patient because I know we all have a lot going on in our daily lives. Thank you so much for the 1.12 update. I’ve already tested it and can confirm that everything is working fine for now.
-
This reply was modified 1 year ago by
Angelgdl.
-
This reply was modified 2 months, 1 week ago by
-
AuthorPosts
