I believe I have a possessed model
-
I hate these guessing games. But are you using layers correctly, have you somehow got raw geometry on something other than layer0 or have you made another layer the active layer.
Have you imported a cad file that could be throwing things off.
Any other non standard things you may have done? -
@box said:
I hate these guessing games. But are you using layers correctly, have you somehow got raw geometry on something other than layer0 or have you made another layer the active layer.
Have you imported a cad file that could be throwing things off.
Any other non standard things you may have done?You're absolutely right, if I'm not willing to post the model I shouldn't have even started this thread. My apologies.
There is nothing different about this model from any other model I've made, it's just a model. I've never used cad files.
What I don't understand is why does everything work fine after I copy and paste everything into a fresh copy of SU, and then slowly it goes to hell again? Makes no sense to me, but nothing about this makes sense to me
-
Maybe some malwares ?
-
@pilou said:
Maybe some malwares ?
I'm very scrupulous about protecting myself when online, and regularly check my computers for anything that shouldn't be there. And while I realize that even the best efforts cannot completely protect you, how would a malware affect only one model?
-
As a premium member you have the ability to set up a private room where you can get advice and discuss things privately.
-
@box said:
As a premium member you have the ability to set up a private room where you can get advice and discuss things privately.
Yes, I know that, but what would be the advantage of going that route? Seems to me like it would only serve to restrict the visibility of the thread. Am I wrong?
-
It would give you the option to share the model with only those that you choose.
Without seeing the model all answers are guesses. If you let someone see it perhaps they can spot a flaw in you work flow or a bug. -
Materials can sometimes cause odd selection behaviour for me...
-
have you any component definitions that need to have their scale defined/reset?
i encountered an issue with SU2015 lately that the entity info box is not picking up on selections and that picked selections remained highlighted as picked even after dropping the selection.
not as severe as your model but still a graphical irregularity that just occurs.
-
-
I had a similar problem when tried to model solar system in SU...
All planets are so far apart that SU started to go crazy - never managed to finish -
Last week I copied and pasted a Group and realized that after pasting I moved by a fraction... The move was so small that I couldn't even measure or see but, after exploding I could delete overlapping faces as separate elements.
SU didn't like it and crashed few times before I started to inspect the faces.
I also use ThomThom's solid inspector.
-
-
I appreciate all the input and suggestions, but no one seems to be addressing the fact that after I copy and paste the model to a fresh instance of SU, all problems are solved, it behaves perfectly normal until after a time it slowly starts to go bad again. I don't think anything that has been suggested so far would allow that to happen, the problem(s) would be just be copied along with the model.
I don't claim to know that much about how SU works, but that seems logical to me. Maybe not Spock logical, but at least Steve logical
-
@hellnbak said:
I appreciate all the input and suggestions, but no one seems to be addressing the fact that after I copy and paste the model to a fresh instance of SU, all problems are solved, it behaves perfectly normal until after a time it slowly starts to go bad again. I don't think anything that has been suggested so far would allow that to happen, the problem(s) would be just be copied along with the model.
I don't claim to know that much about how SU works, but that seems logical to me. Maybe not Spock logical, but at least Steve logical
With Box's suggestion to share the model here with a few other SU users they could at least rule out the fact that a copy gets skrewed up again after a while, .... or also for them the model gets "unstable", (so not your computer related).
-
@rich o brien said:
have you any component definitions that need to have their scale defined/reset?
i encountered an issue with SU2015 lately that the entity info box is not picking up on selections and that picked selections remained highlighted as picked even after dropping the selection.
not as severe as your model but still a graphical irregularity that just occurs.
funny to mention that - I've encountered this too. I just select the highlighted object again, and then deselect all. Wonder if this is worth a bug report anywhere.
Sorry Steve, not something I've encountered, with a model getting progressively worse. Though selection seems a bit finicky when things are ever so slightly off-axis and inference makes it so I just can't select the vertices I want.
-
@hellnbak said:
I appreciate all the input and suggestions, but no one seems to be addressing the fact that after I copy and paste the model to a fresh instance of SU, all problems are solved, it behaves perfectly normal until after a time it slowly starts to go bad again.
The behaviour you mention does sound like an issue where there is geometry miles from the origin. Perhaps you accidentally did something in the original file such as created hidden geometry, a hidden layer or imported a component with a small piece of hidden geometry miles from the origin. It might have been removed after pasting but then reintroduced at some stage?
I know that you said other models were fine in sk2015 but you could also try resaving and opening the model in Sk2014 to rule out any incompatibility of this particular model with sk2015.
-
Just a thought, but do you have any abnormally large textures that could be causing issues?
Otherwise, I'd say delete things until the weirdness stops (in a backup obviously), add things back in until it starts, and try to diagnose it that way.
As for why it's fine in a new model, I'd say perhaps the issue is within a group/component and doesn't kick off until it's accessed?
Advertisement