Quoting: cprnI ride a motorcycle. :><: Hatred grows when I see arcade physics...

It's a spiritual successor to RoadRash, so it does make kind of sense that it has the same intentionally unrealistic physics and controls.

View this comment - View article - View full comments

It's released? I'll have to install this one again then. Last time I tried it (several months ago) it still had ugly garbage collector lag spikes. Hopefully the developers have meanwhile reduced heap allocations to get this issue under control.

View this comment - View article - View full comments

I can confirm that this game freezes the system if one tries to start it with AMD open source drivers when using llvm-4.0.1. An update to the just recently released llvm version 5.0.0 does fix this issue however.

View this comment - View article - View full comments

It's a nice remake. Yet, while I can't name any real reason, I still prefer the original DOS game (which btw. is available at GoG [External Link] and runs pretty well in DOSBox).

View this comment - View article - View full comments

Including Quadro/FireGL might actually be reasonable for laptop users. Laptop manufacturers tend to only sell regular GeForce or Radeon chips in their lowest quality, ultra-cheap models.
If one wants a somewhat acceptable build quality (think: sufficient cooling, so that the laptop case does not start to melt when gaming...), one is either stuck with integrated graphics, or one has to buy a device with a workstation graphics chip...

View this comment - View article - View full comments

Does the OpenGL core context usage relate to WINE's own Direct3D -> OpenGL translation layer, or does it apply to Windows applications using OpenGL (if the latter: how)?

View this comment - View article - View full comments

One thing to consider: Switchable graphics support is basically broken with the proprietary nVidia driver. One is therefore either required to restart X11 whenever one wants to switch graphics chip between the dedicated and the integrated one, or one has to use the open source drivers.
That's why I'd very much prefer an AMD graphics chip: Good performance with open source drivers, and working switchable graphics support...

View this comment - View article - View full comments

Quoting: GuestYes, all games should have key binding settings. Unfortunately even those who have them usually do it wrong:
- they only support ASCII characters (good bye "éèà«»", all keys conveniently placed under my left hand on my bépo keyboard), instead of unicode.
- they do not update tutorial messages to take into account the user key bindings.
- the key binding settings GUI refuses to assign a key if it’s already assigned to another action, instead of simply swapping the keys or deleting the other assignment.
- they do not automatically reassign the keys to the current keyboard layout.

Unfortunately it seems all developers have to write their key binding code from scratch so we see the same mistakes again and again…

Those things are typically engine-limitations, there is not much game developers can do (except for writing their own input-handling instead of using functionality already present in the engine). For instance, in Unity there is no way I would know of for the game code to determine which key is bound to which input event, what makes it pretty much impossible to display correct key bindings in tutorials.

View this comment - View article - View full comments

Quoting: NaibThis sort of thing needs to finally be resolved by AMD be it via fixing the die (shame for those with ryzen...), fixing ucode, patches to kernel.

CPUs will always have some architectural bottlenecks, so fixing such issues on-die will not be an option (as fixing this issue will cause others...). µcode will not help, as it's a scheduling issue, and µcode has nothing to do with scheduling.
The right place to "fix" this issue is the task scheduler of the OS, and I would be strongly surprised if we wouldn't see patches from AMD that address such issues soon.

Edit: As far as I know there are (were?) the same issues on windows. People were even suggesting to treat Ryzen as NUMA due to the relatively long access times for cache on the other CCX.

View this comment - View article - View full comments

Performance wasn't that good in the beta. Certainly playable, but there were occasional stutters that got worse over time.
Glad to see that it has been updated, as I liked the game. Maybe I'm going to install it today again.

View this comment - View article - View full comments