GRIP: Combat Racing

GRIP: Combat Racing

Ver estadísticas:
MazeFrame 1 DIC 2016 a las 4:01 a. m.
Grip on Linux
As I really enjoy this game but also will not stay a windows user any longer than needed, I wonder if there are plans on porting Grip to linux.
< >
Mostrando 31-45 de 68 comentarios
vreten 14 ABR 2017 a las 4:21 a. m. 
Publicado originalmente por Fincer:
Lol, Linux players can play the game in different colors and hues which are randomly generated each time for now. That's some exclusive!

What I really mean...

Menu screenshots:

http://i.imgur.com/mx91Seq.png
http://i.imgur.com/d6cHEgY.png (no, I didn't paint that black spot. It just was there)

Actual gameplay videos:

blue colors
https://www.youtube.com/watch?v=8N7ncOnRQOQ

red/green color mix
https://www.youtube.com/watch?v=oFGyknsFy98

Nice psychedelic disco show, feels like an extra difficult level. GRIP - Version Extreme, or maybe GRIP on Steroids?

P.S. And yes, my computer is quite powerless, especially while recording takes a part of CPU processing power. And as a player, I may suck, too. The videos are more or less a technical demo.

Arch Linux, 64-bit clean Wine prefix.
Wine 2.5 Staging, latest git.

Hi Fincer. How did you get working Grip on linux ?
I have playonlinux already have installed wine 2.5 staging but after game start it writes that grip need DX11 feature level 10 to work. Can you provide me some your system information and configuration. Kernel version, wine configuration and if you have any thirty party packages installed in wine ? Are you using nvidia radeon or intel graphics ? Graphic driver nvidia proprietary, nouveau, radeon, amdgpu, or amd proprietary crimnson or old fglrx? Mesa3d library version? Or simply you can install and run command "inxi -F" to get your system info. Thank you very much.

If this game developers are already focusing on other than Linux, we must get support by wine, adding it to appdb, raise bugs and solve it.
Fincer 17 ABR 2017 a las 10:46 p. m. 
Hi,

sorry for late answer.

- If you are using an Optimus laptop, you must enable optirun (Nvidia card) to play the game. It doesn't launch with Intel card and says just as you described, "need DX11 feature level..." or similar.

- I've used Wine Staging 2.5, latest Git version which I needed to compile from Wine + Wine-Staging GitHub-hosted source code (because that's where the latest DX11 patches are actually available). I've installed the compiled Wine on my system and just use "System" version in PlayOnLinux.

- I use Asus laptop with Intel HD 4000 + Nvidia Geforce GTX 760M inside. I enable Nvidia card in order to start GRIP. I do that with optirun. I use optirun to launch the whole Steam client executable.

- I have nvidia proprietary drivers version 378.13 installed. Mesa version is 17.0.3. Bumblebee packages: bbswitch-dkms-git (Arch Linux AUR repository), bumblebee-git (current version 3.2.1, from Arch Linux AUR repository)

- I have clean Wine 64-bit prefix for Steam client. I've set my Windows version as "Windows 10". I don't have any special settings for GRIP.exe. No DLL overrides or whatsoever. I don't have Staging features enabled in winecfg.

The game may hang on "Installing: U 1/2" window. What I've done I just kill Unreal Engine process (some UE* exe) which is hanging there in background. After that, the game should launch.

You may experience screen resolution changes during splash screen loading period. The game likely gets stuck for a while and it seems that GRIP just freezes (invisible window etc). Just wait for couple of minutes and you may get into the main menu. Personally, I can access the main menu most of the time but not always. And graphics are currently badly corrupted as I've shown in my pics/videos.

Edit: My kernel is currently "4.10.8-1-ARCH" from official Arch Linux repositories.

Edit 2: I've already added the game into Wine Application Database. See it here:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=35014

(yeah, I know the version description should be only "Steam", not "1.1.8 (Steam)". Maybe I'll post a request to change that someday)

Edit 3: This is one of the bugs I've reported already:

https://bugs.winehq.org/show_bug.cgi?id=42728

I'm very sure more bugs exist, but I'm waiting as Józef Kucia, Henri Verbeet, Matteo Bruni and other proud Wine D3D developers are implementing DX11 features (these guys are the guys who are actually doing the whole DX11 implementation in Wine) before I'll fill new bug reports.

Links you may find interesting (these are the sites I use to follow DX11 implementation status):

Wine - patches which are pushed but may not be accepted yet:
https://source.winehq.org/patches/

Wine - implemented DX11 commits/patches:
https://source.winehq.org/git/wine.git/?a=search&st=commit&s=d3d11

Wine - Windows DLL API implementation stats:
https://www.winehq.org/winapi_stats
Última edición por Fincer; 17 ABR 2017 a las 11:29 p. m.
vreten 18 ABR 2017 a las 5:01 a. m. 
Publicado originalmente por Fincer:
Hi,

sorry for late answer.

- If you are using an Optimus laptop, you must enable optirun (Nvidia card) to play the game. It doesn't launch with Intel card and says just as you described, "need DX11 feature level..." or similar.

- I've used Wine Staging 2.5, latest Git version which I needed to compile from Wine + Wine-Staging GitHub-hosted source code (because that's where the latest DX11 patches are actually available). I've installed the compiled Wine on my system and just use "System" version in PlayOnLinux.

- I use Asus laptop with Intel HD 4000 + Nvidia Geforce GTX 760M inside. I enable Nvidia card in order to start GRIP. I do that with optirun. I use optirun to launch the whole Steam client executable.

- I have nvidia proprietary drivers version 378.13 installed. Mesa version is 17.0.3. Bumblebee packages: bbswitch-dkms-git (Arch Linux AUR repository), bumblebee-git (current version 3.2.1, from Arch Linux AUR repository)

- I have clean Wine 64-bit prefix for Steam client. I've set my Windows version as "Windows 10". I don't have any special settings for GRIP.exe. No DLL overrides or whatsoever. I don't have Staging features enabled in winecfg.

The game may hang on "Installing: U 1/2" window. What I've done I just kill Unreal Engine process (some UE* exe) which is hanging there in background. After that, the game should launch.

You may experience screen resolution changes during splash screen loading period. The game likely gets stuck for a while and it seems that GRIP just freezes (invisible window etc). Just wait for couple of minutes and you may get into the main menu. Personally, I can access the main menu most of the time but not always. And graphics are currently badly corrupted as I've shown in my pics/videos.

Edit: My kernel is currently "4.10.8-1-ARCH" from official Arch Linux repositories.

Edit 2: I've already added the game into Wine Application Database. See it here:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=35014

(yeah, I know the version description should be only "Steam", not "1.1.8 (Steam)". Maybe I'll post a request to change that someday)

Edit 3: This is one of the bugs I've reported already:

https://bugs.winehq.org/show_bug.cgi?id=42728

I'm very sure more bugs exist, but I'm waiting as Józef Kucia, Henri Verbeet, Matteo Bruni and other proud Wine D3D developers are implementing DX11 features (these guys are the guys who are actually doing the whole DX11 implementation in Wine) before I'll fill new bug reports.

Links you may find interesting (these are the sites I use to follow DX11 implementation status):

Wine - patches which are pushed but may not be accepted yet:
https://source.winehq.org/patches/

Wine - implemented DX11 commits/patches:
https://source.winehq.org/git/wine.git/?a=search&st=commit&s=d3d11

Wine - Windows DLL API implementation stats:
https://www.winehq.org/winapi_stats

Its ok, Thank you very much for your summary, system information, config, workround and useful weblinks.

I have only one radeon R9 380 graphic card and using amdgpu driver and mesa same version.

At WineHQ appdb Grip status page you are writing that "main menu is completely black", did you have installed "libtxc" packages on your system ? I have previously same problems with grip autosport linux native, maybe wine is using this library too and it will fix your problem.
Fincer 18 ABR 2017 a las 5:48 a. m. 
You're welcome.

Yeah, I have libtxc installed.

Actually, the black menu problem occured with the Wine version 2.3 (as the reported version number is on AppDB page). The issue seems not to be valid on Wine 2.5 anymore. Instead, the graphics are insanely corrupted.

As the Wine development progresses, these issues seem to change either worse or better. I'll re-test the game someday and if significant improvements can be seen, I'll fill a new test report on AppDB.
Fincer 28 ABR 2017 a las 3:11 p. m. 
Forget all pics & videos I've posted above. The graphics has been improved *significantly* since the latest review.

Actually, I guess most graphics are correctly rendered. I still get a weird red color cast on Norvos/Acrophobia track and some wrong rendering for effects (explosions etc). Anyway, see pics here:

Main menu: http://imgur.com/D3QTtIy (yep, and UI layout is correct now)

In-game racing: https://imgur.com/DBEJP9p
In-game racing: https://imgur.com/0iulLgy

In-game racing (red color cast): https://imgur.com/rvIP538
In-game racing (red color cast): https://imgur.com/tM58E2m

And yes. The screenshots were taken on Linux. Low graphics.

This is the latest Wine staging version used. The performance is still quite bad, either due to my crappy laptop, missing DX11 features or both. Anyway, I'm glad to see how the progress is going on, and if I only had a better computer, this game can be quite playable on Linux already.

The game consumes ~2gb of RAM on my Arch Linux system. And it doesn't get stuck on "Installing: U 1/2" popup anymore unlike I claimed above. However, it can take quite some time from splash loading screen to the main menu (it eventually goes there, just be patient)
Última edición por Fincer; 28 ABR 2017 a las 3:12 p. m.
vreten 28 ABR 2017 a las 4:00 p. m. 
For me, no way to get it worked. The only one difference between my and your system is graphic card my radeon/ your nvidia.
Fincer 28 ABR 2017 a las 4:07 p. m. 
Damn. Quite unfortunate. We talked this already but yeah. I'm using Nvidia GTX 760M, Nvidia 378.13 drivers. Radeon seems to be no go option for now.

Have you considered opening a new bug report on Wine Bugzilla for the Radeon/GRIP issue?
Fincer 3 MAY 2017 a las 3:20 p. m. 
New test results submitted to Wine AppDB:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=35014

I guess correct rating for AMD Radeon users might be "Garbage" instead of "Gold". Unfortunately, I'm unable to test the game with Radeon card.
Bero 3 MAY 2017 a las 4:00 p. m. 
if you are going to develop handheld version of Grip Nintendo Switch is obvious choice
vreten 4 MAY 2017 a las 12:39 p. m. 
Publicado originalmente por Fincer:
Damn. Quite unfortunate. We talked this already but yeah. I'm using Nvidia GTX 760M, Nvidia 378.13 drivers. Radeon seems to be no go option for now.

Have you considered opening a new bug report on Wine Bugzilla for the Radeon/GRIP issue?

Hi. Thanks for testing. I'm using Debian/Testing and some version of packages same as you. So maybe is not about Radeon but about Debian problem, maybe you are using some newer packages, but i do not know. We need someone who has Debian+Nvidia or Arch+Radeon system configuration to test it.

I was also testing Debian/Testing+Radeon+wine-2.7-staging but it still not work. I have reserved some space on hard drive to install arch, so next time i will test Arch+radeon+wine-2.7-staging.
vreten 4 MAY 2017 a las 12:42 p. m. 
Publicado originalmente por Fincer:
New test results submitted to Wine AppDB:

https://appdb.winehq.org/objectManager.php?sClass=version&iId=35014

I guess correct rating for AMD Radeon users might be "Garbage" instead of "Gold". Unfortunately, I'm unable to test the game with Radeon card.

Also. Nice to see, that GRIP is already working in WINEHQ.
Fincer 4 MAY 2017 a las 1:24 p. m. 
Publicado originalmente por vreten:
Hi. Thanks for testing. I'm using Debian/Testing and some version of packages same as you. So maybe is not about Radeon but about Debian problem, maybe you are using some newer packages, but i do not know. We need someone who has Debian+Nvidia or Arch+Radeon system configuration to test it.

I was also testing Debian/Testing+Radeon+wine-2.7-staging but it still not work. I have reserved some space on hard drive to install arch, so next time i will test Arch+radeon+wine-2.7-staging.

Yeah, after having read your message I think you are right. We need more testers or more test data.

In summary: More data we have, better chances we have for narrowing down the reasons for these issues and thus we'd be able to give more data for Wine devs to create a fix as well.

It sounds very great if you are kind enough to install and test the game on Arch Linux (I know all the trouble configuring an Arch installation may take). Any information (about installed packages, versions etc) you need about my Arch configuration, just ask me (via Steam chat or here).

If your assumption is correct (Radeon card is not the issue here but package versions are), I will modify my Wine test report on that part.
Última edición por Fincer; 4 MAY 2017 a las 1:28 p. m.
vreten 7 MAY 2017 a las 6:31 a. m. 
Today i was trying to force wine to support DX11 in Debian/testin+wine-2.7-staging+csmt=true+radeon+mesa-17.0.4-1. From the beginning, it looked like everything works fine, there was some GRIP loading screen, but then screen has switched off and pc totally freezed and also hard reset did not help. And after I unplugged power sources and started it again, the computer started to work.
Fincer 7 MAY 2017 a las 7:33 a. m. 
That sounds really bad. So playing the game is still no-go for you. After all the trouble of installing Arch and stuff...

can you provide any terminal output/log which could help Wine devs to sort out the issue?

Basically, run wine with a command like

wine WINEPREFIX=<yourprefixpath> WINEARCH=win64 Steam.exe &> $HOME/grip_logfile

or additionally with debug parameter WINEDEBUG=-all,d3d11 (add any relevant DLL component here)

I can fill a new Wine bug report if needed. You can use pastebin to attach the log file.

EDIT:

I dropped app rating to "Silver" on Wine AppDB page. Further testing has been indicated that minor issues still exist though I'm able to play the game etc. And, testing done by vreten with Radeon card has also affected to my app rating.
Última edición por Fincer; 7 MAY 2017 a las 8:37 a. m.
Fincer 17 MAY 2017 a las 1:47 p. m. 
I deleted those videos because they are very misleading at the moment. Graphics are rendered correctly (exception for effects) using Nvidia card. Some viewers may assume that the graphics shown in the videos represent the current Wine DX11 implementation state which is very incorrect assumption in the case of GRIP.

I'm too lazy to record new gameplay videos right now. Sorry. :P
< >
Mostrando 31-45 de 68 comentarios
Por página: 1530 50

Publicado el: 1 DIC 2016 a las 4:01 a. m.
Mensajes: 68