Does the piecechecker normals error have to be at the default warning level?
Moderator: Moderators
Does the piecechecker normals error have to be at the default warning level?
Is it something that outside of potential visual issues would create problems? Because having it on by default is pretty annoying and it is mostly crying about fire points. There are a few parts it is complaining about but I see no visual issues.
Re: Does the piecechecker normals error have to be at the default warning level?
is there a way to suppress this warning?
Re: Does the piecechecker normals error have to be at the default warning level?
I am going to keep asking what is the deal with this? I am getting it on 3dos, "but 3dos are old and busted anyway." that's nice, I get them on s3os, "recalc your normals in upspring." anyone telling me to use an auto-normal tool doesn't understand the point of setting them.
it floods my infolog, and I have been asking about this "normals error" warning for weeks now. Are most of the devs on vacation right now? I mean I can understand that. Just seems like a lot of the errors are somewhat unclear. Others like this one are rather peculiar. Why would this be at the default warning error. I am pretty sure I made a post about that and it was deleted, or my phone ate it(some reason my phone kicks out errors posting here). I dunno.
What is going on? do I need to be concerned? Is there a way to suppress this error?
it floods my infolog, and I have been asking about this "normals error" warning for weeks now. Are most of the devs on vacation right now? I mean I can understand that. Just seems like a lot of the errors are somewhat unclear. Others like this one are rather peculiar. Why would this be at the default warning error. I am pretty sure I made a post about that and it was deleted, or my phone ate it(some reason my phone kicks out errors posting here). I dunno.
What is going on? do I need to be concerned? Is there a way to suppress this error?
Re: Does the piecechecker normals error have to be at the default warning level?
There's probably a way to suppress it for yourself by setting LogSections https://springrts.com/wiki/Springsettin ... ogSections but I don't know which bit needs disabling.
+1 that this should be a 'I want to check this and turn it on' vs. a 'every man and his dog needs to be told about this every single game'
+1 that this should be a 'I want to check this and turn it on' vs. a 'every man and his dog needs to be told about this every single game'
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: Does the piecechecker normals error have to be at the default warning level?
assuming I can tonight, I will look into it. Thank you for the suggestion!FLOZi wrote:There's probably a way to suppress it for yourself by setting LogSections https://springrts.com/wiki/Springsettin ... ogSections but I don't know which bit needs disabling.
Re: Does the piecechecker normals error have to be at the default warning level?
Having to scroll over miles of log section aint normal, but on Spring it is. Infolog, not even once!9
Error should show once per UnitType.
Error should show once per UnitType.
Re: Does the piecechecker normals error have to be at the default warning level?
It does.PicassoCT wrote:Error should show once per UnitType.
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: Does the piecechecker normals error have to be at the default warning level?
You sure? One of my projectile models was affected and it errored every time that unit shot.hokomoko wrote:It does.PicassoCT wrote:Error should show once per UnitType.
Re: Does the piecechecker normals error have to be at the default warning level?
hmm, I'll check that