Ready to get dirty? Today, 'MXGP3 - The Official Motocross Videogame' has been officially released for Linux.
Originally developed and published by Milestone S.r.l. and ported to Linux by Virtual Programming, the Linux version arrives little over a year after it was released for Windows. This is the first release from Virtual Programming in some time, after Micro Machines World Series and ARMA 3 updates.
Supporting both NVIDIA and AMD GPUs, plenty of you should be able to jump in.
Direct Link
More about it:
Experience all the adrenaline of Motocross with the official Championship’s only videogame! MXGP3 - The Official Motocross Videogame offers the most involving game experience ever, with completely new gameplay and graphics thanks to Unreal® Engine 4. Race on 18 official tracks and in the MXoN with all riders and bikes from the 2016 MXGP and MX2 seasons and be the first to experience the thrill of riding one of the 10 2-strokes available! Render your rider and your bike unique, with more than 300 official components for a complete customisation!
We've reached out to VP today, to see if we can get a review key for testing. So hopefully we can say a lot more about it in a future article.
Looks like a game I would really enjoy, so hopefully it performs well. The customisation options sound pretty fun!
You can find it on Humble Store (70% off) - No Linux icon there yet since it just released, but it's simply a Steam key or head directly to Steam.
Give them time to reply first before jumping into conclusions. Even if it turns out as a really broken release like Witcher 2 , don't bash them etc. Simply refund and don't look back.
Quoting: XpanderDoesn't work for me sadly :(
https://steamcommunity.com/app/561600/discussions/0/1741100729952845904/
Thanks for testing. Let's see if it can be fixed quickly.
Quoting: GuestEither way it's not a very good look. I am constantly surprised when devs release something and then go home without waiting on reports first.Quoting: XpanderQuoting: liamdaweOuch, another botched release? Was hoping that wouldn't happen after The Witcher 2.
I wonder how they tested it on their systems or did they validate it at all.
I't might be just simple silly thing like missing some files from the build they sent up to steam though..
I wouldnt call this a botched release yet. Lets give them some time. But it worries me that theres even not a single reply from devs/VP to the issue.
Give it another 12 hours. Time zones and all that - VP employees are probably not at work right now. They'll be having a fun day tomorrow though I guess.
Quoting: liamdaweQuoting: GuestEither way it's not a very good look. I am constantly surprised when devs release something and then go home without waiting on reports first.Quoting: XpanderQuoting: liamdaweOuch, another botched release? Was hoping that wouldn't happen after The Witcher 2.
I wonder how they tested it on their systems or did they validate it at all.
I't might be just simple silly thing like missing some files from the build they sent up to steam though..
I wouldnt call this a botched release yet. Lets give them some time. But it worries me that theres even not a single reply from devs/VP to the issue.
Give it another 12 hours. Time zones and all that - VP employees are probably not at work right now. They'll be having a fun day tomorrow though I guess.
I would hope they have a life outside of the office, and their company ensures they work the contracted hours, no more no less.
Quoting: kit89Quoting: liamdaweQuoting: GuestEither way it's not a very good look. I am constantly surprised when devs release something and then go home without waiting on reports first.Quoting: XpanderQuoting: liamdaweOuch, another botched release? Was hoping that wouldn't happen after The Witcher 2.
I wonder how they tested it on their systems or did they validate it at all.
I't might be just simple silly thing like missing some files from the build they sent up to steam though..
I wouldnt call this a botched release yet. Lets give them some time. But it worries me that theres even not a single reply from devs/VP to the issue.
Give it another 12 hours. Time zones and all that - VP employees are probably not at work right now. They'll be having a fun day tomorrow though I guess.
I would hope they have a life outside of the office, and their company ensures they work the contracted hours, no more no less.
The total amount of hours is one thing. But this issue could be avoided with releases earlier in the work day so that you actually have time to receive(and act on) feedback.
Quoting: KristianYes, that was my point that seems to have been missed. You shouldn't release if you have no time to deal with urgent issues. Firing and forgetting as seems to have been the case yesterday is not a good idea for anyone. Why should we have to wait 12/24 etc hours until it works? If it releases, it shouldn't just fail to work for seemingly everyone.Quoting: kit89Quoting: liamdaweQuoting: GuestEither way it's not a very good look. I am constantly surprised when devs release something and then go home without waiting on reports first.Quoting: XpanderQuoting: liamdaweOuch, another botched release? Was hoping that wouldn't happen after The Witcher 2.
I wonder how they tested it on their systems or did they validate it at all.
I't might be just simple silly thing like missing some files from the build they sent up to steam though..
I wouldnt call this a botched release yet. Lets give them some time. But it worries me that theres even not a single reply from devs/VP to the issue.
Give it another 12 hours. Time zones and all that - VP employees are probably not at work right now. They'll be having a fun day tomorrow though I guess.
I would hope they have a life outside of the office, and their company ensures they work the contracted hours, no more no less.
The total amount of hours is one thing. But this issue could be avoided with releases earlier in the work day so that you actually have time to receive(and act on) feedback.
I don't want to be overly negative, but it's very annoying.
Last edited by Liam Dawe on 23 November 2018 at 10:15 am UTC
See more from me