To debug, use NO$PSX with the Psy-Q symbols. However, for basic debugging just adding printf() will suffice.

You mean, X-LINK for MS-DOS or Windows 95 by FCD?



XLINK95 (for Windows 95)
XLINK (for MS-DOS)
Enjoy

If we assume your soldering was done right and the code was flashed correctly to the PIC, it could be anything from incorrect install guide images to bad code on the chip. The most common being that the install image that told you where to solder doesn't align with the pinouts and logic on the PIC. ...

Solved. Put LoadImage at the end of Display function in order to reload the background on every frame. void display(void) { // Flip buffer index //db = !db; // Wait for all drawing to complete DrawSync(0); // Wait for vertical sync to cap the logic to 60fps (or 50 in PAL mode) // and prevent screen...

That looks nice. I've only watched the movie because I haven't been able to decompress the .7z file, the downloaded file is 30,246,760 bytes tall, but 7zip tells me that it can't open it as an archive (my 7zip version is quite old, but I never had that problem before). I have that problem on Window...

That's pretty impressive. It looks very difficult though. I'd suggest improving the textures, adding lighting and working on maintaining 60 FPS. The biggest problem to me seems to be the texture resolution. Also, paper aeroplanes are white (not sure why you picked grey) ;) For some reference to what...

There's a PDF and PowerPoint presentation from Sony describing the matrix's in better detail on the Technical Reference CD. That information should help you.

roob wrote: ↑February 17th, 2023, 9:03 pm Thanks! I'll take a look at the NO$PSX.

The latest NO$PSX supports Psy-Q symbols as well so that means you'll be able to see your symbols in MIPS assembly. NO$PSX is the first one to handle that

The formula varies from each country: https://en.wikipedia.org/wiki/WD-40 For the Australian formula, I find WD-40 tends to evaporate, dry out and leave a film of slime. Hence, it's not good for actual permanent lubrication of moving parts where you need the oil to remain the same viscosity. I find ...

I need help about converting a Ps1 exe compiled with Psy-Q to Ps2 POPS compatible SLUS_XX.XX file. These are the PSXDEV forums. They were specifically setup since 2012 for the PS1. For that, you'll need to find a "PS2DEV" forum to find someone who knows PS2 development. I'm not sure why y...

If you can't find clock oil, you can use sewing machine oil. Basically you want a very thin and light oil with no heavy detergents (IE: you wouldn't want to use WD-40 even if it's generally thin because it has detergents).

Once you have VSCodePSX from NDR008 's repo working in Visual Studio Code, you can run the PS-EXE that was built in an emulator such as NO$PSX (undisputedly the best emulator for debugging) or DuckStation (great for running the final build of your game with upscaled graphics). The author of PCSX Red...

I noticed that it only run with a 32bit Windows Version. is there a 64BIT BIN2_C.exe ? If yes, i can adapt and update this tool for x64 Systems too ;) thanks Why don't you just write your own binary to raw hex converter in whatever language your program uses? There are plenty of examples out there ...

Uz3rN4m3 wrote: ↑August 3rd, 2022, 9:07 am not all symbols work...
symbols i found working are: !$%&/()=?+-#;:,.><^

It should be using the font sheet located in the BIOS and that in itself is indeed missing some symbols.

Leirisal wrote: ↑February 8th, 2023, 7:01 am If i wanted to replace the PS logo with a simple picture...

Use Losers bootedit program.

No, you use GENCTI.EXE. It will read every file and directory in your working directory and create the CTI (so it needs to be edited after usually to remove a few non-needed files). The SYSTEM.CNF sheet must always be the first file on the disc as well. REM Make the CTI sheet (edit it as needed afte...

I've used the artist board before. I managed to run the program which lets you render 3D stuff. It worked, but mapping textures to 3D objects is basically impossible due to how poor the program interface is. Instead, I used Lameguys Blender export tool for doing the 3D stuff and then I threw the fin...

When you write the RCUBE sample via BUILDCD, make sure in the CTI sheet the SYSTEM.CNF file is the first one in the hierarchy. Also make sure the CNF text is correct and it points to the correct PS-EXE (IE: the "BOOT" string value).

Just an update regarding the broken volume levels. It seems I overlooked the volume slider ('Sound Volume' seen in my screenshot below) within the NO$PSX options. Sliding it back to full volume restored the issue. It operates independently from the Windows volume slider which is why I was so confuse...