UFO: Alien Invasion Issue Tracker
UFO: Alien Invasion
Go to the previous open issue
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
icon_project.png UFO: Alien Invasion / Closed Bug report #2932 Transparent 3D geoscape with GLSL shaders turned on
Go to the next issue (open or closed)
Go to the next open issue
This issue has been closed with status "Closed" and resolution "Not determined".
Issue basics
  • Type of issue
    Bug report
  • Category
    Campaign
  • Targetted for
    Not determined
  • Status
    Closed
  • Priority
    6. Vital
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (1)
People involved
Times and dates
  • Posted at
  • Last updated
  • Estimated time
    Not estimated
Issue details
  • Resolution
    Not determined
  • Reproducability
    Not determined
  • Severity
    Not determined
  • Complexity
    Not determined
  • Platform
    Not determined
  • Architecture
    Not determined
Attachments (0)
There is nothing attached to this issue
Duplicate issues (0)
This issue does not have any duplicates
Description
[http://sourceforge.net/p/ufoai/bugs/2932 Item 2932] imported from sourceforge.net tracker on 2013-01-28 19:54:51

What happens:
Globe is transparent. I can't see anything on it but installations, globe outline and territory outline. Screenshot attached. Could be related to #2987922

How to reproduce:
Turn on 3D geoscape, turn on GLSL shaders and check geoscape.

Build:
27 June 2011, nightly from http://ufoai.ninex.info/wiki/index.php/Download (complete installer)

My spec:
Windows 7 64 bit, Radeon HD 4870, DxDiag attached.
===== Comments Ported from Sourceforge =====

====== *anonymous (2011-06-28 17:06:46) ======

older build, but looks the same
====== *anonymous (2011-06-28 17:07:06) ======


====== *anonymous (2011-06-28 17:07:16) ======


====== *anonymous (2011-06-28 17:07:27) ======


====== tlh2000 (2011-06-29 06:31:54) ======

This artifact has been marked as a duplicate of artifact 2987922 with reason:
No explanation provided.
====== tlh2000 (2011-06-29 06:32:44) ======

added the old ticket as a reference
====== tlh2000 (2011-06-29 06:33:09) ======

maybe you have a look at it sandros?
====== alextishin (2011-06-29 12:02:45) ======

That's an easy one:

r_glsl_version "1.10"

Our shaders are strictly 1.10 and no #defines will make them 1.50, 2.00, 3.30 or 4.10, because later versions dropped FFP compatibility stuff. Which is massively used by the current code. Not only by shaders, but by the actual UFO:AI engine.
So -- stick to the version 1.10

Also, attached config.cfg sets r_glsl_version to 4.10, but console log reports max supported version of 3.30 -- how did that happen?

====== tlh2000 (2011-06-29 13:42:28) ======

so the error is that the cvar somehow got the wrong value? or it was allowed to change it? should we set the cvar to read only? and remove the option from the video menu?
====== *anonymous (2011-06-29 13:49:47) ======

Yes, I could change GLSL version to whatever I wanted. Had no idea my hardware/software doesn't support 4.10. When I set it to 3.30, 3d geoscape now is not transparent.
====== tlh2000 (2011-06-29 14:07:48) ======

this should be fixed for 2.4 then - otherwise we would get a lot of reports about this after we've released it
====== alextishin (2011-07-01 17:36:33) ======

On rethinking the issue: actually, there seems to be a whole nest of bugs:

1) FFP fallback code doesn't kick in when "incompatible GLSL version" error is encountered (that's what causes transparent globe actually)
2) It is possible to set r_glsl_version cvar to the value above max supported by driver
3) It is possible for user to set GLSL version which is not compatible with our shaders
4) Our shaders use 10 years old FFP compatibilty profile (a.k.a. version 1.10) of GLSL, which is BROKEN in current ATI drivers, causing the dynamic lighting bugs

My suggestions:
Fix 1)-2) ASAP
Remove that user control until our shaders will really support newer versions of GLSL
Keep the cvar at least in dev version of the game, so it will be possible to work on shaders that support GLSL 1.50 and beyond
Work on said shaders, when time permits

PS: Ɓukasz, you should set GLSL version to 1.10 for shaders to work :) With 3.30 you are actually getting the fixed function path renderer, which is not that pretty -- check it for yourself
====== tlh2000 (2011-07-02 07:39:05) ======

the 2) is fixed in 726581c3ae6908837cb77554cd541edd53a1aa15
====== tlh2000 (2011-07-02 07:42:40) ======

the selectbox is disabled now - see d5d807cbef5f1857034dba8a0aa383585ea1d32d
====== tlh2000 (2011-07-02 07:51:59) ======

1) is fixed in 3c332a8535362dfbb14eaae5642ea75244d73718
====== tlh2000 (2011-07-02 07:53:42) ======

setting this to pending now - as the geoscape is no longer rendered in black now - the shaders issues that Alexander talked about are not yet fixed - but should also not be part of this ticket
====== sf-robot (2011-07-16 08:20:04) ======

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).
Steps to reproduce this issue
Nothing entered.
Todos (0 / 0)
Issue created
footer_logo.png The Bug Genie 4.3.1 | Support | Feedback spinning_16.gif