Bug 103062 - Error starting game FS17
Summary: Error starting game FS17
Status: RESOLVED NOTABUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: glsl-compiler (show other bugs)
Version: 17.2
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: mesa-dev
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-10-02 14:33 UTC by alexander
Modified: 2018-03-06 11:53 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Log FS17 (1.93 KB, text/plain)
2017-10-02 15:36 UTC, alexander
Details

Description alexander 2017-10-02 14:33:19 UTC
Hello, I cannot start Farming Simulator 17 to mesa. Gives a window "failed to initialize 3D system. No shader 2.0. To update your graphics driver." But if the driver is the newest?! Must only work on proprietary drivers, find this error failed to log the previous game Farming Simulator 15, though the game works, but there's an error with shaders: Shader Version: 1.30
GL_NV_texture_compression_vtc not supported
How to upgrade the version of the Shader ? Fix this bug please.
Comment 1 alexander 2017-10-02 14:35:08 UTC
And the proprietary driver cannot be installed (does Not work).
Comment 2 Emil Velikov 2017-10-02 14:53:01 UTC
What hardware are you using? Can you attach the FS17 log (as plain text). 

Implementing GL_NV_texture_compression_vtc in Mesa might be problematic since the extension IP status is "NVIDIA Proprietary".

Then again, the log should give us a bit more context.


https://www.khronos.org/registry/OpenGL/extensions/NV/NV_texture_compression_vtc.txt
Comment 3 alexander 2017-10-02 15:36:14 UTC
Created attachment 134620 [details]
Log FS17

Wine FS17 incorrectly defines my CPU. In fact AMD-A8 6410 with AMD Radeon R5 Graphics 4 core. I have an HP laptop.
Comment 4 alexander 2017-10-02 15:39:17 UTC
(In reply to Emil Velikov from comment #2)
> Implementing GL_NV_texture_compression_vtc in Mesa might be problematic
> since the extension IP status is "NVIDIA Proprietary".
How to upgrade the version of the Shader?
Comment 5 Emil Velikov 2017-10-02 15:58:35 UTC
(In reply to alexander from comment #4)
> How to upgrade the version of the Shader?

That's not it works. Can you provide a more complete log/output from the game?
Alternatively getting some connection between the game <> Mesa devs is a nice idea.

Some questions for the FS17 devs:
 - does the game use OpenGL 3.2 or later with Compat context?
If so I strongly recommend using a Core one.
Comment 6 alexander 2017-10-04 06:57:55 UTC
(In reply to Emil Velikov from comment #5)
> That's not it works. Can you provide a more complete log/output from the
> game?
I'm in the conclusion of starting the game I downloaded the new version.
The game now asks Shader 3.0 Because of this, it does not start.
> AlI'm in the conclusion of starting ternatively getting I'm in the conclusion some connection between the game <> Mesa devs is a
> nice idea.
It's really good. But look:
https://forum.giants-software.com/viewtopic.php?f=936&t=114460
They themselves made the problem solved, supposedly we can not help (we do not support wine).
> Some questions for the FS17 devs:
>  - does the game use OpenGL 3.2 or later with Compat context?
> If so I strongly recommend using a Core one.

And there is. Supported by OpenGL is not lower than 4.0
I made the command MESA_GL_VERSION_OVVERIDE = 4.5COMPAT, but still. Maybe because of this error (error not supported)?
 Do not understand what I should do to run the game.
Comment 7 Emil Velikov 2017-10-11 10:27:55 UTC
> > AlI'm in the conclusion of starting ternatively getting I'm in the conclusion some connection between the game <> Mesa devs is a
> > nice idea.
> It's really good. But look:
> https://forum.giants-software.com/viewtopic.php?f=936&t=114460
> They themselves made the problem solved, supposedly we can not help (we do
> not support wine).

The thread has nothing to do with using Core vs Compat GL context.
I suggest focusing on that - it's the first key obstacle.
Comment 8 alexander 2017-10-14 03:32:34 UTC
> The thread has nothing to do with using Core vs Compat GL context.
> I suggest focusing on that - it's the first key obstacle.

Compat for compatibility with older devices.
In Innovations added to Mesa core.
4.5 COMPAT there is support for OpenGL 4.5, Shader 4.50.
Comment 9 alexander 2017-10-14 03:35:52 UTC
And another OpenGL context for compatibility me 3.0 and Shader 1.30.
Comment 10 Emil Velikov 2017-10-16 16:25:44 UTC
Alexander, I'm struggling to understand what you mean.

Compatibility GL Profile is _not_ aimed at old hardware, but at old software. Newly written applications should not use it, without a very compelling reason.
Comment 11 alexander 2017-10-17 06:18:37 UTC
It will be possible to download an older version of FS17.
Comment 12 Timothy Arceri 2018-03-06 00:29:03 UTC
The user seems to be trying to run Farming Simulator 17 via wine. I believe Wine uses compat profile by default and so the game fails to start due to mesas limited support for compat. Apparently Wine staging defaults to core for Mesa drivers.

Either way this doesn't seem like there is any real bug with mesa here, just missing support for compat which is well known and doesn't require us to track bugs like this.

Closing.
Comment 13 Henri Verbeet 2018-03-06 10:01:05 UTC
(In reply to Timothy Arceri from comment #12)
> The user seems to be trying to run Farming Simulator 17 via wine. I believe
> Wine uses compat profile by default and so the game fails to start due to
> mesas limited support for compat. Apparently Wine staging defaults to core
> for Mesa drivers.
> 
I don't know what this bug report is about either, but for reference, the Direct3D implementation in Wine's 3.x series will default to core profiles for Direct3D 10 and 11 applications on Intel and AMD GPUs. It will currently default to compat profiles for Direct3D 9 and earlier, and on NVIDIA hardware.
Comment 14 Emil Velikov 2018-03-06 11:53:56 UTC
Some information, which is not immediately obvious:
 
 - game supports both DirectX10/11 and OpenGL (compat) renderer
Alexander toggle back to the DirectX one
 
 - report was done before wine 3.x was released
Alexander try with latest Wine

 - there's OpenGL 3.1 + ARB_compatibility support for gallium drivers in mesa git, would be Mesa 18.1


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.