Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LG and plasma RE_RegisterShader error #51

Open
robertsi opened this issue Sep 1, 2023 · 4 comments
Open

LG and plasma RE_RegisterShader error #51

robertsi opened this issue Sep 1, 2023 · 4 comments

Comments

@robertsi
Copy link

robertsi commented Sep 1, 2023

Is this a bug in the latest version. Tried with q3a paks and ql paks...everything default...

https://cdn.discordapp.com/attachments/228028739991109634/1146456787940282368/image.png

https://cdn.discordapp.com/attachments/228028739991109634/1146456854298378350/image.png

Alaso I have some very old q3 .dm3 demos, which wolfcam can't play can you maybe make this work in some future version?
image

KR,
Robert

@em92
Copy link
Contributor

em92 commented Sep 2, 2023

Alaso I have some very old q3 .dm3 demos

You need to upload them here in order to reproduce

@robertsi
Copy link
Author

robertsi commented Sep 3, 2023

here is the demo si_ita_dm7_ripper.zip

what about the lg shader issue?

@brugal
Copy link
Owner

brugal commented Sep 7, 2023

That shader error can happen if you have both ql and q3 pks in baesq3. Ex:

pak00.pk3

pak0.pk3
pak1.pk3
pak2.pk3
pak4.pk3
pak5.pk3
pak6.pk3
pak8.pk3


pak00.pk3 is the Quake Live one

They get loaded in alphabetical and numeric order so (q3) pak6.pk3, for example, would replace the files in (ql) pak00.pk3. In the scripts/lightningnew.shader file Quake Live changed the lightning bolt shader name and that's the one we're looking for.

One work around is to rename the ql pk3 so that it is loaded later. Ex: pak00.pk3 -> zpak00.pk3

@robertsi
Copy link
Author

robertsi commented Sep 8, 2023

Hmm im pretty sure I had just ql paks at first....and q3 paks in subfolder...anyways the workaround works! thnx!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants