Star Citizen

538 readers

2 users here now

This is your community for everything related to Star Citizen - an up and coming epic space sim MMO being developed by Chris Roberts and Cloud Imperium Games.

Rules

All c/starcitizen content must be related to Star Citizen. Content with an indirect relationship must attempt to provide meaningful discussion of Star Citizen.
Be respectful. No personal insults/bashing. Don’t be a dick.
Follow these posting restrictions:

No Grey Market Trading.
- Trading items using in-game currency is fine, but no trading hangar items (ships, game packages, etc.) using real world currency.
No blog spam, stream spam, or re-hosted content
- Posting your own content is welcome, the frequency of posting should not be excessive.
No Cheat Accusations.
- Posting about someone cheating is okay as long as any identifying information or username is removed/obscured.
No links to or advertisement of cheat products.
Do not post or advertise your Referral Code for Star Citizen. Use the referral code randomizer.
When posting video links please include a short description in the post (titles aren't always descriptive enough).

Useful links/tools/info

Official Links:

Other Links:

Current Bug Avoidance Thread
Star Citizen Wiki
Star Citizen Characters
Universal Item Finder
Linux Users Group Helper Script
Dev Tracker (Only works with Spectrum at the moment)
Starchives (Query/Search all closed captions throughout all official videos)

Loadout Tools:

Vehicle Loadout Tool (Erkul)
Ship Performance Viewer (Includes a "RADAR detection calculator" which is great for checking stealth builds).
FPS Loadout Finder/Loot Drop Calculator
FPS Weapon Stats

Industrial Tools:

This is an unofficial Star Citizen fansite, not affiliated with the Cloud Imperium group of companies. All content on this site not authored by its host or users are property of their respective owners.

founded 2 years ago

MODERATORS

QuadratureSurfer@lemmy.world

starcitizenfan@lemmy.world

Game launcher shader mechanism? (lemmy.world)

submitted 1 week ago* (last edited 1 week ago) by ProjectPatatoe@lemmy.world to c/starcitizen@lemmy.world

1 comments fedilink hide all child comments

Does anybody know if current launcher is switching shader folders because of a different game version/build only or is it actually checking the rendering pipeline to see if it needs to? Because different drivers can change the shader compilation enough that it needs to be regenerated. Depending on the how the launcher is doing it, it might not realize that shaders need to be regen'ed.

Ran into this previously on an Nvidia driver update wondering why performance was so bad sometimes. I noticed that some games recompiled shaders on something as simple as a windows update and it made me kinda pay more attention to what triggered it. Realized the pattern of basically any combination of bios, vbios, cpu, gpu, drivers, windows updates, settings, can affect the way shaders are generated.

I copied the above from a post reply i made on Reddit but realized that maybe someone here would actually know the answer? I haven't looked deeply into the whole shader management recently. I just know it went from nothing to making new folders when there's an update (... why not delete?!?!)

you are viewing a single comment's thread
view the rest of the comments

[–] QuadratureSurfer@lemmy.world 2 points 1 week ago* (last edited 1 week ago)

It depends on how big of a jump from one version to the next.

Edit: TL/DR shader folders are based on the Star Citizen game version, not the Nvidia driver versions as far as I've seen.

You can find the shader folders under "%localappdata%\Star Citizen"

Alternatively the full path:
"C:\Users<username>\AppData\Local\Star Citizen"

On any major version changes, there is a completely different folder for shaders (ex: 4.3.2 -> 4.4.0)

On minor version changes/updates the shaders folder is rarely shared with the previous version (ex: 4.3.1 -> 4.3.2). Although I haven't noticed this happen in a long time.

I've noticed that usually very minor version changes/hotfixes that come out within a few days of a previous update will share the same shader folder with a previous version (ex: 4.3.2-live.10452200 -> 4.3.2-live.10591185).

The worst issue I've seen happen because of this was when they first introduced caves. I was standing inside of a cave, and a friend could not see the cave even when he tripped and fell right inside of it. He needed to exit and clear his shader folder before he was able to see the caves.