@utri007 I'm not sure what do you mean by already a game. Both are replacements for the original Tomb Raider engine, and from what I've seen OpenTomb is the more advanced from the two. The Cannonball engine doesn't look all that different to me to running OutRun in Mame, but if there's interest I can add it to my list.
This is just like television, only you can see much further.
I think I had a quick look at some transmission code once. IIRC there was a problem with multi-threading and sockets mixed with Amiga signals, or something like that.
Software developer for Amiga OS3 and OS4. Develops for OnyxSoft and the Amiga using E and C and occasionally C++
Lords and ladies, LÖVE is in the air! To quote their website: Quote:
LÖVE is an *awesome* framework you can use to make 2D games in Lua.
In case you don't want to create your own game, there are quite a few floating on the net, including Mari0. Keep in mind that different LÖVE versions are not API compatible, so only games made for LÖVE 0.8.0 will work. I included a few of these on my website. If you find more compatible games, I'll add them to the list. As usual, I uploaded everything to my website (boo!): http://bszili.morphos.me
Addendum: Despite of being a 2D engine, LÖVE draws everything using OpenGL, so you need a card with Warp3D support. I tried Wazp3D, but I couldn't find any compatible settings. Maybe Alain can help us out with a cfg file?
This is just like television, only you can see much further.
Thanks for the Love port. Very nice. I do get a system lock up after closing a game though. Can you try to reproduce?
Download In your Face City trains from your site. Leave OWB running in the background. Run IYFCT Play a while Quit with "esc" Go back to your site on OWB click a link = SYSTEM LOCKUP
@ddni The problem with this is that it's not LÖVE that locks up the system, but OWB. It might be doing something off, but there is no way for me to tell. I can't do much with lock ups anyway, this is the curse of low level operating systems. The only solution is not using LÖVE and OWB at the same time.
This is just like television, only you can see much further.
Do you plan to finish Homeworld port soon ? Last WIP version that was released drops to 2 fps when AHI is enabled, but runs smoothly (Sam460) when you disable AHI.
@SinanSam460 That's an SDL bug identified by Hans. The audio task has too high priority (15) starving device driver tasks on some systems. I don't know who is the current maintainer of SDL is, but he has to be contacted regarding this issue.
Edited by BSzili on 2015/4/21 6:57:46
This is just like television, only you can see much further.
@tekmage It's not really about the lack of sex appeal, but I don't think synthetic tests like this are particularly useful for the users. I can put this to the very end of my list, but I'd prefer put my time into porting user applications instead.
This is just like television, only you can see much further.
That's an SDL bug identified by Hans. The audio task has too high priority (15) starving device driver tasks on some systems. I don't know who is the current maintainer of SDL is, but he has to be contacted regarding this issue.
Sadly, nobody is currently maintaining SDL.
I do wonder if the root cause is SDL, or if the audio driver busy-waiting. Or maybe the audio task itself is wasting CPU cycles by busy-waiting.
The audio slowdown is less pronounced with a beta RadeonHD driver that's currently being tested. It reduces how often the CPU gets yielded to other tasks. The audio still sounds fine even though the audio task gets less CPU time, which is why I suspect that something the audio task is wasting CPU cycles by busy-waiting.
Something running with as high a priority as 15 should behave similarly to an interrupt handler; it should perform whatever processing it must do quickly, and then hand over the CPU to other tasks ASAP (usually, by waiting for the message/signal to arrive). It absolutely must not waste CPU cycles in a tight polling loop while waiting for something to happen.