NO$PSX Feature Requests

[Administrator]

NO$PSX - Highly Requested Features

• Have the ability to debug CPE files that have been compiled under Psy-Q with the '-g' command (via CCPSX) which will use the Psy-Q *.SYM (symbol files) to debug the source code in real-time (exactly like a DTL-H2000) [Requested by: Shadow & LameGuy64]
  
• Display 'cop2' instructions in the debugger as GTE commands (RTPT, NCLIP, etc) as well as displaying 'cop2' registers as regular r0-r31 registers or 'C2_*' macros that represents the register's purpose (C2_XY0, C2_Z0, etc like when writing GTE routines in assembly with the macro headers in the official development kit) [Requested by: LameGuy64].

[Gh0stBlade]

I've been asking for this feature several times over the years. I hope No$psx in the future can emulate sio parallel port. This will allow running games which attempt to retrieve files from a PC via PCOpen/PCClose etc.

[gwald]

2nd controller support would be very nice? :/

[Someone]

Wireframe rendering as a debug feature is really needed.

[Administrator]

Real-time debugging support on a real PlayStation would be awesome. At the moment, I think "Upload a PS-EXE" only uploads to the PSX's RAM. It doesn't actually allow you to debug the program running I don't believe.

I'd also really like to see the GUI re-designed to something more like S.N System's design.

[Administrator]

There is a major bug in NO$PSX V2.0 which is that the TOC (Table of Contents) is not being updated correctly: http://www.psxdev.net/forum/viewtopic.p ... 158#p14340

[Squaresoft74]

Uploading exe to Xplorer / Xplorer FX, no matter what original rom version they had, worked flawlessly and the upload is damn fast and stable compared to X-killer.
Great work with that stuff, thank you very much for this.
Maybe Caetla roms support could be considered in later release ?

[ViLXDRYAD]

being able search for ascii strings and for values changed over a step would be incredibly useful imo

[celophi]

Memory breakpoints on read/write would be heaven.

[train_conductor]

Have a memory usage indicator, so it is easy to see the Main RAM, SPU RAM and GPU RAM usage levels.

[masterg0r0]

Whenever I boot up the PS1 BIOS on the latest version of "NO$PSX", it freezes on the Sony Computer Entertainment screen. Looking in the TTY command logs, there seems to be some interferance with the CD-ROM DMA channel by the looks of it. I'm using the latest version of "NO$PSX", version 2.8 to be exact and not the gaming version.

Code: Select all

PS-X Realtime Kernel Ver.2.5
Copyright 1993,1994 (C) Sony Computer Entertainment Inc. 
KERNEL SETUP!

Configuration : EvCB    0x10            TCB     0x04
System ROM Version 4.1 12/16/97 E
Copyright 1993-1997 (C) Sony Computer Entertainment Inc.
ResetCallback: _96_remove ..
System Controller ROM Version 99/02/01 c3
PS-X Control PAD Driver  Ver 3.0
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
IRQ3 DMA DMA2.GPU
...

[alexfree]

Allow disc swapping (open/close drive lid WITHOUT RESET), like DuckStation.

I'd also like to know if anyone has gotten this working well with wine. Most games encounter a 'mem full' error when using wine to play them.

[nocash]

Allow disc swapping (open/close drive lid WITHOUT RESET), like DuckStation.

Disabling the "Autostart CDROM" checkbox (in lower-left of the Open file dialog window) when loading the CDROM-image should work.

I'd also like to know if anyone has gotten this working well with wine. Most games encounter a 'mem full' error when using wine to play them.

I've never heard about that problem. As far as I know, no$gba is working fine with wine, and no$psx should require even less memory (compared to no$gba in NDS mode with huge memory mapped NDS rom-images).

Does the error screen look as if it's generated by no$psx, or by the OS utself? And does the error message really say 'mem full'? I can't find any such message in my source code.

And when does that error occur, immediately after loading the ROM-image, or after running the emulation for some minutes? There are some logging functions in no$psx that might allocate more and more memory over time (for TTY messages and for the most recent video frame in the GPU/VRAM viewer, the latter can be a problem with homebrew code that doesn't do "swap buffers" to indicate the begin of a new frame).

PS. If it's logging related: does it also occur in gaming version? And, you have the most recent no$psx v2.1, right?

[alexfree]

Allow disc swapping (open/close drive lid WITHOUT RESET), like DuckStation.

Disabling the "Autostart CDROM" checkbox (in lower-left of the Open file dialog window) when loading the CDROM-image should work.

I'd also like to know if anyone has gotten this working well with wine. Most games encounter a 'mem full' error when using wine to play them.

I've never heard about that problem. As far as I know, no$gba is working fine with wine, and no$psx should require even less memory (compared to no$gba in NDS mode with huge memory mapped NDS rom-images).

Does the error screen look as if it's generated by no$psx, or by the OS utself? And does the error message really say 'mem full'? I can't find any such message in my source code.

And when does that error occur, immediately after loading the ROM-image, or after running the emulation for some minutes? There are some logging functions in no$psx that might allocate more and more memory over time (for TTY messages and for the most recent video frame in the GPU/VRAM viewer, the latter can be a problem with homebrew code that doesn't do "swap buffers" to indicate the begin of a new frame).

PS. If it's logging related: does it also occur in gaming version? And, you have the most recent no$psx v2.1, right?

Thank you for the response. I will check with the memory error and let you know.

[alexfree]

Allow disc swapping (open/close drive lid WITHOUT RESET), like DuckStation.

Disabling the "Autostart CDROM" checkbox (in lower-left of the Open file dialog window) when loading the CDROM-image should work.

I'd also like to know if anyone has gotten this working well with wine. Most games encounter a 'mem full' error when using wine to play them.

I've never heard about that problem. As far as I know, no$gba is working fine with wine, and no$psx should require even less memory (compared to no$gba in NDS mode with huge memory mapped NDS rom-images).

Does the error screen look as if it's generated by no$psx, or by the OS utself? And does the error message really say 'mem full'? I can't find any such message in my source code.

And when does that error occur, immediately after loading the ROM-image, or after running the emulation for some minutes? There are some logging functions in no$psx that might allocate more and more memory over time (for TTY messages and for the most recent video frame in the GPU/VRAM viewer, the latter can be a problem with homebrew code that doesn't do "swap buffers" to indicate the begin of a new frame).

PS. If it's logging related: does it also occur in gaming version? And, you have the most recent no$psx v2.1, right?

I setup no $ psx emu v2.1 with lutris (on linux using a different wine version from lutris) and it works great now, including the swapping of discs without reset. Thanks a lot, now this can be my main emulator for testing things.

I was wondering if it would be possible to add even larger fonts? I also can not find a way to increase the font size for the debug tty messages window.

[mkultimate]

Add these features

1.: fps counter, this helps when you want to go for 60 fps, where it is set to 30 to start the game and when unlocked to 60 the counter should change to 60fps, I do this but with the ePSXe emulator, since it detects the change of FPS, this would be of great help.

2.: add copy the address shown in the status bar

3.: Add to pause or not the emulator when losing focus, for realtime editing in memory.

4.: add edit the instruction when executing double click and the instruction is complete only to edit something necessary and not write the complete instruction.

5.: add search AOB

6.: add copy AOB

[nocash]

fps counter - I don't know what you mean, there is an option for displaying the emulation speed (in percents) and the number of rendered/emulated frames (per second) in the window caption - if you mean that?

copy address & edit old instructions - yes, isn't yet released, but I have added and a few more things that a while ago.

auto pause - yeah, I should probably add that someday, especially for the gaming version. Ah, wait, you mean opposite: NOT pausing the game window when the debug window is in foreground... not planned at the moment, but that's an interesting idea.

AOB - I don't know what that means... business something?

[mkultimate]

fps counter - I don't know what you mean, there is an option for displaying the emulation speed (in percents) and the number of rendered/emulated frames (per second) in the window caption - if you mean that?

copy address & edit old instructions - yes, isn't yet released, but I have added and a few more things that a while ago.

auto pause - yeah, I should probably add that someday, especially for the gaming version. Ah, wait, you mean opposite: NOT pausing the game window when the debug window is in foreground... not planned at the moment, but that's an interesting idea.

AOB - I don't know what that means... business something?

AOB (Array Of Bytes scan)

On the subject of FPS, I'll explain, when you're looking to unlock 60 fps, when you have a counter activated where it shows 30 fps and you unlock 60 fps, the counter changes from 30 to 60 fps

[inirdin]

Being able to save/export the correctly colored texture in bottom right corner in Vram Viewer would be nice.

[Lollie]

I've mentioned it before, but support for PocketStation memory card functions - the ability to save and load PocketStation-specific data on a memory card - would be greatly welcomed. To date, XEBRA is the only PS1 emulator with support for these functions.

(Relatedly, NO$GBA is also unable to save data to PocketStation memory cards.)