@kas1e
@any

Can you just remind me with some examples of what will now be possible to non beta users with NovaBridge? I know what it allows, but... some concrete examples.

Hi.

You cannot use the BIN file. You have to give it a CUE file.

Check Google on how to make your own CUE file, it's easy. I think there is a post above explaining how to so it.

3246251196ryan<>gmaildotcom , paypal. No need for donations, but I also would not say no since it buys beer.

Thanks.

Okay, how much slower are we talking? I noticed a slight slow down by only a few FPS.

What is your .conf file? And what machine?

Mednafen would run a lot better with another core ExecMC! (or, I think that is what the rumor was: that ExecMC stood for Exec MultuCore).

As for a front end, if someone wants to collaborate that is fine. But the eGame that was shown at AmiWest looked quite good anyway.

I will not be making a front-end.

It is worth mentioning that Spotless V2 is not usable to non-Beta, right?

@samo79

Actually, I see your issue and can reproduce it. Wonder if someone else has noticed this another SDL application?

@mufa

<module>.videoip 0 (disables any *linearfiltering)
<module>.(x|y)scale (scaling for window mode)
<module>.(x|y)scalefs (scaling for FS mode)
video.driver (can be "opengl","default" or "softfb").

Try changing scaling, and also changing to "softfb" ?

Let me know how it goes.

@kas1e
Quote:

I have said this to Samo79 a few times, and also in my explanation in the first post as to why I even did this port.

For me, the only reason for doing this was for PSX. I just wanted a way to play my childhood game of Resident Evil on PSX natively on the AmigaOS4 with the lights off.

Now, FPSE is clearly a really good emulator. You can see because when I run RE using FPSE there is not much CPU utilisation, and it runs and looks great and the audio is better. The issue seems to be that in emulation mode, the timings are all off. And, I am unable to even save the game. No card is found - even if I configure the card file. When I use acceleation, I think this needs WARP3D - on both my X1000 and X5000 the same thing happens: now, the performance is really slow. I think there was still an issue with saving the game. Also, I noticed that some of my image files would just outright not load in FPSE. I do not think that the source code for FPSE is available. So, I ported Mednafen, which hammers the CPU, but I am able to enjoyably play ALL of my PSX games and everything just works. The performance is not quite as good, and the sound implementation should perhaps use OpenAL - I am not sure.

As for other modules like SNES, I would generally advise the other emulators out there - but if Mednafen is more convenient for users because it is everything under the same common emulator - then fine. I was always just interested in the PSX - and found that the other modules all just compiled anyway.

There is no N64.

Okay, thanks for the update.

Do you see any speed degradation? I actually see a slight speed decrease with this version for PSX, but more stability. Work is on-going.

Yes, well, the Saturn requires 64-bit. So, that would take SOME amount of looking into.

Much more often then not, I come across a project with the usual configure, then make etc and the following issue:

the configure knows that this is a cross-compiling toolchain and yet... STILL... in various location during the "make" process, the system will try and invoke some recently built binaries; of course, they do not work: they are have been built for a different host system running a different architecture!

So, am I missing a commonly used option to configure other than build/host/target? I do read the disable/enable,with/without sections of the configure, but it is still not always clear which one to use. Things like --disable-testing make sense.

Or, are these just people that have made the build system under the assumption that the programs are always executable by the build machine!?

I updated the release (thank you Samo79 for contributions). All the modules compile, but I am unsure which ones work other than SNES and PSX. Mufa has a list above, but that was with an older version. This time, with clib2 (afxgroup), GBA compiled okay.

It would be nice for people to test which ever modules they are interested in and report back.

If you do use it, remember that you need to run mednafen initially for it to populate the configuration file. Then, always change

"sound.period_time" to value "100000" and
"cd.image_memcache" to value "1"

X1000.. Lower priority than a1222,

They found the cfe source code again, but need to figure out how to build it again.

Right, collections was not released in until after 2.5.6.

Collections is a fundamental module for Python, but it is not existing in our SYS:System/Python/lib.

Presumably, we at least should have all the modules from package: libpython2.7-minimal?

Is it a simple matter of copying the PY files over. I am guessing so .....

For the sake of completeness and history:

See also: https://www.amigans.net/modules/newbb/viewtopic.php?topic_id=4187

Great news.

At least we know of that bug. Manipulation of PYTHONPATH (and friends) is quite common for PY stuff; even I know that I am by far an expert in PY.

If we had access to the source code for PY2.5.6 we could perhaps have a look and fix it - versus: porting PY from scratch when someone has clearly already done most of the hard work.

Since there is no github location, I cannot report an official bug.

I noticed it when invoking a "configure". In the configure it runs a python script and sets PYTHONPATH - now, the native modules installed in Workbench are not visable.

I am working on the configure script now, but I would guess it is going to have to be a hack to also add the native OS4 modules path - as well as - the additional path wanted by the configure script.

RAM:test.py:


Ensure there is no value set for PYTHONPATH at the moment:


Execute the script:


Set PYTHONPATH:


Ensure that it has been set:


Execute the script:


Try also in "sh" - the same issue.

I report this because on OS4Depot it is version 2.4.1, but somehow I have 2.5.6 and I cannot remember where I got that from. I am not sure if 2.5.6 was meant to be more mature than 2.4.1 or whether this is a known issue.

PYTHONPATH is meant to extend - not replace - the searchables.

@kas1e

Hi Kas,
indeed - most of Boost is just template stuff and generally do not need the libraries - but there are some headers missing from Os4depot version.

If someone does not look into before me, then I will get around to looking at it.