What would you like to see in Project64 2.2?

[zilmar]

What would you like to see in 2.2?

[HatCat]

When I play games on my free time under any emulator, all I really keep thinking is how nice it would be if this LLE ran at full speed. :P angrylion and I will have to work out stuff about the RDP on our own for that, but I hope that RPG will continue to help you with the recompiler strategies.

Some other stuff I occasionally think of...NetPlay with friends, maybe some internal timing changes, a working cheats debugger I guess.

[RPGMaster]

Definitely would like to see the debugger being complete . Aside from that, I'd love to see audio and timing improved. Also there's some gfx issues in Factor 5 games that I'd like to see fixed.

I'll continue helping with RSP recompiler . I also want to start another task in the near future. Either emulator core, or RDP.

[retroben]

I would like for memory search to get fixed so I can search for codes on 2.x lagfree instead of on the slower emucr leaked 1.7.0.50 ver23 beta.

[zilmar]

I added a commit that should put most of the functionality of memory search/edit back in.

[zilmar]

Originally Posted by RPGMaster

Definitely would like to see the debugger being complete .

Not sure I can do complete, but I did add back in the memory search, what other debugger functionality did you want?

Originally Posted by RPGMaster

Aside from that, I'd love to see audio and timing improved.

I was thinking of making the default sync to audio as on, it seems to give a better play for most people. The sync to the CPU is better for 100% repeatable behavior, so if I have net play, be able to create movies based off key strokes, syncing re compiler/interpreter.

Originally Posted by RPGMaster

Also there's some gfx issues in Factor 5 games that I'd like to see fixed.

Anything gfx related i can not do, would be nice some time in the future to have GLideN64 when it is actually released.

Originally Posted by RPGMaster

I'll continue helping with RSP recompiler . I also want to start another task in the near future. Either emulator core, or RDP.

thanks

[RPGMaster]

Originally Posted by zilmar

Not sure I can do complete, but I did add back in the memory search, what other debugger functionality did you want?

Eh, pretty much w/e 1.7 has is good enough. Just being able to use r4300i command stepping/ breakpoints, memory dumping, and memory view is good enough for me.

Originally Posted by zilmar

I was thinking of making the default sync to audio as on, it seems to give a better play for most people. The sync to the CPU is better for 100% repeatable behavior, so if I have net play, be able to create movies based off key strokes, syncing re compiler/interpreter.

I really wish I knew how audio works from a scientific standpoint. Mupen64 0.5 seems to have a good balance of both. I'm sure the CPU isn't synched perfectly, but the audio quality is nice.

Originally Posted by zilmar

Anything gfx related i can not do, would be nice some time in the future to have GLideN64 when it is actually released.

I can't do anything with gfx either . From what I've heard, the graphical issues in Factor 5 games were caused by the emulator core.

I guess I should learn how the emulator core works, since I'm more likely to accomplish something with that, rather than gfx . I also look forward to GlideN64's release.

Originally Posted by zilmar

thanks

You're welcome

[deathdroid]

Great to see you back about Zilmar! And I hope all is going well with you.
I'll make a pull request for some of my changes tonight hopefully.

I guess peoples biggest complaint seems to be tied to Fixed Audio Timing causing games to stutter.

[HatCat]

Originally Posted by RPGMaster

memory dumping

That's another thing I forgot about.

Supposedly pj64 dumps memory but...I had to write my own RDRAM export feature in angrylion gfx plugin (with endian fixing)? Because pj64 just dumps the RAM in CPU disassembly text view. I don't want a text file; I want a binary file of the 4 or 8 MB dumped so I can navigate through it via a pixel map viewer to look at texture/frame buffer memory in the RDRAM. Can't do that with text files.

I already wrote a program to open binary files as bitmaps and scroll through the pixels/pitch under various color decoding modes, and plus there's LemAsm. But none of the n64 emulators except Nemu64 actually dump the RDRAM to a binary file?!

Originally Posted by RPGMaster

I can't do anything with gfx either . From what I've heard, the graphical issues in Factor 5 games were caused by the emulator core.

Gfx issue with Factor 5 games on PJ64 are caused by incorrect VI registers, or the timing when VI_X_SCALE_REG and things like that get set. That's why they have a black screen a lot of the time. Also, interlaced frame buffer video timing doesn't work on pj64, so games with a 640x480 frame buffer only come out with a 320x240 one.

[Predator82]

Would like to see my issue #5 on git hopefully fixed