From my testing it currently only got worse. Seemingly because of the overhead the 3dses operating system introduces when sending commands to the dsp. I also tested without handling sound mixing at all and it was still slow at o3ds speed. So I guess it is not the (only) problem.
There are binaries of gericom's port if you know where to look.Interesting. Its a pitty that "borb" only distribute the binaries
God am I dense. How did I miss that.I know, check my username
Aah, yeah. Could try shooting them a PM? I thought I saw them post it, but I think I'm misremembering.
The performance on O3DS is already good enough to play the game, but do you have any other ideas left to improve performance a little? or is this most likely the best we'll get?
I guess the current way the 3d backend works isn't optimal either. It was build onto the pc port thing, but it could probably be more efficient.
It will be great if me can use some ports from hacked nintendo 64 games from example this two projects:
I have tried the WiiU port and it throws a lack of memory error. The elf file is quite massive compared to the 3DS binary
Looks cool for an Unity demo, his Vita demo looks even more impressive.
I heard the opposite from speed runners. The 3DS games are running in the original engine with upgrades. They have the same exact bugs as the N64 versions.
Interesting. I never quite understood if they could just use the original source, because if not then the similarity between the n64 and 3ds remake is very surprising, considering the latter would have had to be completely remade. That's why I find it more likely to be a port of sorts.
Usually if an engine is designed well, it should be possible to reuse the logic part and only rewrite the rendering parts (and sound backend and such) for new hardware. That way the behavior of the game should be equal.
The source code to my project will be released in the future.I know, check my username
I was wondering about the source code of the borb's project.
