LÖVE

Hello all today I am going to open up testing on a fork of Vapor I have been working on. I made a compatibility layer for 0.8.0 games and updated Vapor to 0.9.x. Most of the games work and have been tested. But I have not fully played many of them. So I'm asking y'all to play some games. Some really fun ones. A lot of fun ones lol.

Submit any issues that y'all have on this forum and in the issue tracker on my fork:
https://github.com/Bobbyjoness/vapor

Here is attached is the .love also please make suggestion for the future of Vapor.
Also just in case some of y'all don't know I'm not the original author of Vapor but I did get permission to run this test. The original author is Josefnpat and the original repo is here https://github.com/josefnpat/vapor

Edit 1: The second Vapor file fixed some games using threads. But they way I did it may introduce race conditions and ultimately can cause threads to hang if they are waiting on a package that they will never receive or whatever is happening. I was told I would have to make a mutex lock but I'm putting that off. If any of y’all would like to take a stab at it I would much appreciate it. If a game with threads freezes just restart it. Guys tell me what y'all think of the fixed cover flow

Nice job! Seems to work for some, not for all.

In the end my pc crashed but that's an ATI Linux driver issue

Thanks qubodup and its hard to tell. Did the first game crash?

I'm working up from the bottom. Everything up to Xapalus works. Xapalus technically works but the server seems not to be working because money never increases despite having factories.

Everything from there to TrAInsported works. TrAInsported fails to load assets properly at first-run.

Stuff works until I got to Soundscape which errors.

Snaik runs with console open, maybe change that. It also seems not to work properly, try to start a game with default settings.

I've tested up to Sienna which works well.

Thanks and the console being open is the game's fault not vapor's

lost_RD wrote:Everything from there to TrAInsported works. TrAInsported fails to load assets properly at first-run.

I'm pretty sure TrAInsported is using threads to load assets, which may be the issue, if you havent throughly test threads I think that may be the cause of the problem, It may be trying to load another LÖVE module, like love.filesystem and trying to use a function that has changed from 0.8.0 (ie: love.filesystem.enumerate)... But even then I'm just guessing!

Keep it up I'm sure you can do it

If you run trainsported multiple time it will eventually power through.

bobbyjones wrote:Thanks qubodup and its hard to tell. Did the first game crash?

I'm pretty sure it crashed when I confirmed wanting to exit.