After launching Tropico 5, I can hear the game sound but there is no game window not even black window reported with Intel HD 4000 GPU. Tried setting env variable MESA_GL_VERSION_OVERRIDE=4.0 MESA_GLSL_VERSION_OVERRIDE=400 and vblank_mode=0 which works for Intel HD 4000. System: Kubuntu 14.10 Linux kernel 3.16.0-29-generic Mesa 10.5.0-devel (git-7a182d2) using oibaf ppa https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers X.Org X Server 1.16.0 tested GPUs Intel Bay Trail, device id: 0f31
terminal output: emamk@emamk-workstation-PC:/media/emamk/Data/Tropico 5$ ./Tropico5 Platform: { developer = false, editor = true, goldmaster = true, linux = true, steam = true, } [SDLXInput] 0 controller(s) found Lua revision: 185260 Assets revision: 19222 Steam AppID: 245620 Loading account storage... Account storage loaded successfully in 263 ms VideoImpl::ReadFrame: read frame header size dont match IVF_FRAME_HDR_SZ. end of movie maybe... VideoImpl::ReadFrame: read frame header size dont match IVF_FRAME_HDR_SZ. end of movie maybe... New UI mode "Game" set in 0 ms VideoImpl::ReadAndDecodeFrame: skipped frames: 15 VideoImpl::ReadAndDecodeFrame: skipped frames: 124 VideoImpl::ReadAndDecodeFrame: skipped frames: 113 VideoImpl::ReadAndDecodeFrame: skipped frames: 16 VideoImpl::ReadAndDecodeFrame: skipped frames: 25 VideoImpl::ReadAndDecodeFrame: skipped frames: 6 VideoImpl::ReadAndDecodeFrame: skipped frames: 109
Okay if the run the game on nVidia graphics and then again run the game on Intel graphics then it works on Intel graphics with MESA_GL_VERSION_OVERRIDE=4.0 MESA_GLSL_VERSION_OVERRIDE=400 environment variables. So it seems like nVidia graphics able to compile some shaders and save the shaders in the game folder and then Intel graphics able to run the game. For example if I remove the game folder and install a fresh copy of the game and first try with Intel graphics the game will not run. Once I run the game with nVidia grapics later I can run the game with Intel graphics strange!
(In reply to Md Imam Hossain from comment #2) > Okay if the run the game on nVidia graphics and then again run the game on > Intel graphics then it works on Intel graphics with > MESA_GL_VERSION_OVERRIDE=4.0 MESA_GLSL_VERSION_OVERRIDE=400 environment > variables. So it seems like nVidia graphics able to compile some shaders and > save the shaders in the game folder and then Intel graphics able to run the > game. For example if I remove the game folder and install a fresh copy of > the game and first try with Intel graphics the game will not run. Once I run > the game with nVidia grapics later I can run the game with Intel graphics > strange! That is weird. It seems unlikely to be related to shaders... Intel GPUs wouldn't be able to use shaders compiled for an NVIDIA GPU. Is there any other output logged by the game on a fresh install?
tested with latest mesa master Mesa 10.6.0-devel (git-09d6ea9 2015-02-11 utopic-oibaf-ppa) The game working fine on Intel Haswell 4600 GPU but the main problem remains. With Intel Bay Trail there is no game window but I can hear game sound. Terminal output: emamk@emamk-Notebook-PC:/media/emamk/Data/Tropico 5$ ./activated.sh Platform: { developer = false, editor = true, goldmaster = true, linux = true, steam = true, } [SDLXInput] 0 controller(s) found Lua revision: 185260 Assets revision: 19222 Steam AppID: 245620 Loading account storage... Account storage loaded successfully in 306 ms VideoImpl::ReadAndDecodeFrame: skipped frames: 3 VideoImpl::ReadAndDecodeFrame: skipped frames: 118 VideoImpl::ReadAndDecodeFrame: skipped frames: 119 VideoImpl::ReadFrame: read frame header size dont match IVF_FRAME_HDR_SZ. end of movie maybe... ^[VideoImpl::ReadFrame: read frame header size dont match IVF_FRAME_HDR_SZ. end of movie maybe... New UI mode "Game" set in 1 ms
Tropico 5 should work now - we actually support GL 4.x on Gen7+, and people have added drirc hacks to deal with the compatibility profile issues.
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.