Jump to content

Recommended Posts

Posted

Hi,

 

I used X-Plane 10 and it worked fine many times, but suddenly (I think after trying to install Paris environment) it started

to crash on startup giving 

 

There was a problem processing a GLSL pixel shader.
You may need to rerun the installer or update your graphics drivers.
Resources//shaders/terrain_vert.glsl
Resources//shaders/terrain_frag.glsl

 

I reinstalled and updated X-Plane many times, and as there are currently no updates available for my graphics drivers,

I tried to start X-Plane using the no_glsl option. I read (http://forums.x-pilot.com/topic/2349-odd-x-plane-start-up-problem/

) that this should work fine, but in particular,

 

X-Plane-32bit.exe --no_glsl | more

 

gives

 

 

Found sim dataref sim/time/local_time_sec
Found sim dataref sim/cockpit2/clock_timer/local_time_hours
Found sim dataref sim/cockpit2/clock_timer/local_time_minutes
Found sim dataref sim/cockpit2/clock_timer/local_time_seconds
Found sim dataref sim/graphics/misc/light_attenuation
Found sim dataref sim/graphics/animation/draw_light_level
Found sim dataref sim/weather/temperature_sealevel_c
Found sim dataref sim/graphics/animation/draw_object_x
Found sim dataref sim/graphics/animation/draw_object_z
Starting thread loader.
Lighting slot 14,0 is unused.
Lighting slot 15,0 is unused.
Lighting slot 14,1 is unused.
Lighting slot 15,1 is unused.
Lighting slot 7,5 is unused.
VRAM needed: 2069064.  Trivial VRAM: 4054272.  Packed VRAM: 2359296.
Packed efficiency: 0.876984.  Unpacked efficiency: 0.510342.
Resources/shaders/terrain_frag.glsl: Fragment shader failed to compile with the
following errors:
Compiler error: unexpected operato
Resources/shaders/terrain_vert.glsl+Resources/shaders/terrain_frag.glsl: Fragmen
t shader(s) were not successfully compiled before glLinkProgram() was called.  L
ink failed.

 

as command line output. The no_glsl option doesn't seem to influence this at all (I get exactly the same output without this option).

Maybe this is due to using the x86-version (the command line options aren't included yet? --help works fine)?

Posted

Driver issue for sure, and sounds like you're on beta drivers at that. Assuming this is an Nvidia card, be sure to use 3.14 drivers: http://www.nvidia.com/object/win8-win7-winvista-64bit-314.22-whql-driver.html

 

If you're on Linux you should use 3.13.

 


The no_glsl option doesn't seem to influence this at all (I get exactly the same output without this option).
Maybe this is due to using the x86-version (the command line options aren't included yet? --help works fine)?

 

The no_glsl option actually doesn't work in X-Plane any longer.

Posted

Thanks, indeed I found a more recent version of my graphics driver. I installed it, the error has disappeared but

now it yields

Could not load facade!

Resources\default scenery\1000 autogen\US\urban_high\objects\FacScrp1.fac

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...