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

Missing marks #1101

Open
maek opened this Issue Dec 24, 2018 · 7 comments

Comments

Projects
None yet
3 participants
@maek
Copy link
Contributor

maek commented Dec 24, 2018

The engine does not draw any marks (shadows, creep, ...) on surfaces formed by several brushes that have coplanar faces and use the same shader (e.g. map-xyz_source.dpkdir.zip).

@maek

This comment has been minimized.

Copy link
Contributor

maek commented Dec 24, 2018

You can see the missing shadows if you load the map with devmap xyz and enable the 3rd person view with cg_thirdPerson 1. It is worth noting that both the shadows and the creep are correctly drawn on the raised brush.

@illwieckz

This comment has been minimized.

Copy link
Member

illwieckz commented Dec 26, 2018

Also, this simple map displays so much weirdness with lines (and is not bloom compatible at all 😁 )

@maek

This comment has been minimized.

Copy link
Contributor

maek commented Dec 27, 2018

@illwieckz I forgot to mention that I built just the bsp (no vis, no light) for the sake of brevity... anyway, I've included the .map so you can experiment as you like 😄

@slipher

This comment has been minimized.

Copy link
Contributor

slipher commented Jan 3, 2019

There's a cvar called r_noMarksOnTrisurfs which defaults to on. Does setting that to 0 do anything?

@maek

This comment has been minimized.

Copy link
Contributor

maek commented Jan 6, 2019

So if I set it to 0 then the issue goes away. Any idea about the reason?
Btw I'm testing with -homepath /tmp/.unvanquished/ so everything should be at default.

@slipher

This comment has been minimized.

Copy link
Contributor

slipher commented Jan 6, 2019

If you mean any idea about the reason this cvar exists (and can't be set to 0 without cheats enabled!), then no. I just randomly happened to see the cvar a few days ago.

@maek

This comment has been minimized.

Copy link
Contributor

maek commented Jan 6, 2019

Apparently that cvar is for allowing marks on models (md3, ...). The thing is why it's taking that path while with less brushes it is not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment