Airio revival - Printable Version

Airio revival - Printable Version

+- AirAttack Racing Forum (https://airattackteam.com)
+-- Forum: Live For Speed (https://airattackteam.com/forum-27.html)
+--- Forum: General Discussion (https://airattackteam.com/forum-39.html)
+--- Thread: Airio revival (/thread-1527.html)

Airio revival - fstarter - 01-09-2022

On lfs discord there was a talk about airio revival. Tim managed to get in contact with EQ Worry and there was a talk about buying the source code.

So, do we have people that have some kind of experience when it comes to insim coding?

RE: Airio revival - Ivanov - 01-10-2022

Yes, basic stuff like changing values from true to false Smile

RE: Airio revival - rane_nbg - 01-11-2022

Well, that is a very good news, but taking responsibility to maintain the code is quite a big task. I'm not sure if we are on par with it, but we sure can give it a try unless it's too expencive. JoRuss is capable of developing it and a few of us are familiar with coding, so it should be ok I guess. It's not like we need to change a ton of stuff at first.

RE: Airio revival - fstarter - 01-12-2022

Here are some of the highlights from the conversation in discord
[Image: fDmUnks.jpg]

RE: Airio revival - joruss - 01-14-2022

(01-12-2022, 12:10 PM)fstarter Wrote: Here are some of the highlights from the conversation in discord

Thing is that because it is written in non obfuscated C# it's pretty much open source since day one so I don't really see any change (beside legal/moral issues) when it comes into opening the sources officially.

I'm all for compensating EQ and all his time he spent on the project but it really shouldn't be a case of asking turkey how sharp (hehe) the knife should be. EQ should be the one that states the price to avoid offers like 400€ which seems big until you realize that is a junior developer wage for a week.

I like the idea of patreon, maybe that's something EQ should consider instead of giving away rights to his code but that'd mean there should be "perks" like taking feature requests and further developing the software in coordination with teams/patrons.

Another road I'd consider being in his place is to sell the sources to LFS devs and it becoming de facto part of LFS service (not quite sure if they'd be interested tho).