my program supports instantiation, but all the instances have to use the same texture. it really shouldn’t have that limitation but since it does, each and every one of those cranes is a separate model. which sucks…
29 Comments
Leave a ReplyLeave a Reply
You must be logged in to post a comment.
By reading some good books, I learn nice words and slogans.
and some good ideas, if you read the right books…
Vanity and pride do more harm for progress,
you just said a mouthfull…
You have a good point there.
by refusing to admit fault, you are denying yourself the opportunity to improve
That is one area I am working on.
look at it this way, if you spend all your time lying about your faults and passing the blame, when do you have room to improve?
That is a very good bit of advice.
own your shortcomings and mistakes
As the old saying from the late Vince Lombardi goes “Striving to be perfect makes us excellent.”
it can. but you’ll never even reach excellent pretending to be perfect and ignoring your shortcomings
Because none of us is perfect.
nor should we pretend to be
Owning up to mistakes is part of becoming a better person.
absolutely, it is an essential part
I agree with you right there.
admitting fault is one thing…
I would not blame you if you did not release it for viewing.
I don’t see the point of broadcasting my failures
It will look even better when finished.
if it doesn’t, you’ll never see it
Nice one here, sounds very time consuming
less of a time issue, more of a resource issue. even with instantiation I still have to place the instances…
Sounds like extra work, but worth the effort. ?
it isn’t about the effort, it is about the memory footprint. I should only need one instance of that geometry adding to my overhead
The shadows from the cranes look great.
should look even better with some postwork
That is a lot better and I like the shadows from the cranes