Jump to content
AutoDesSys

Undo Paste leaves behind wireframe geometry and/or materials


Recommended Posts

Strange things happen when you Undo a paste of geometry and materials.  Sometimes it leaves a unselectable wireframe of the pasted geometry after undo.  Other times it leaves behind the materials from the 'Undo' pasted geometry.

 

To repeat the bug, open an existing file with geometry and materials.  Copy geometry with multiple materials.  Open a new file.  Paste.  Undo.  See strangeness.

 

Link to comment
Share on other sites

Hey Justin

I have always found that undoing  a paste will leave the materials behind.  As for the unselectable geometry that is something that I have been noticing for a while as well.  I do find at times that switching between shaded view, wireframe and even full shaded will eliminate the geometry in the view.  I have felt for quite some time that there is some sort of memory leak in the program that leaves graphic information behind.    Not sure if it is graphic card related.  If I render a scene and then go back to change the model and then hit render again the old scene pops up for a few seconds before the new one starts.  At times if I close a model the old rendered scene pops up again for a few seconds.  And here is a weird one:  Sometimes if I scale an object in one direction while in shaded view the  object is shown as wireframe at its new size(while still in shaded view)  and still shaded view at its old size.  Switching to full shaded shows the correct object size. 

Is anyone else experiencing this? 

 nvidea gtx 1080

 

Tech, is there any chance of getting the old option back to "clear rendering memory"?  I used to use that a lot.

Link to comment
Share on other sites

Hey Andrew

 

Yes, I also get the weird shaded display bug after scaling an object in wireframe, then switching to Shaded, the object is not shown correctly scaled.  However, like you mentioned, switching to Shaded Full and back to Shaded fixes it.  I think the Shaded needs a memory reset when switching from Wireframe.  

 

I also miss the 'Clear Rendering Memory', it seemed to fix a lot of the weird things FormZ would show.

 

I've been working on a bugs list since helping test this new renderer... _Ray, and I think I can more easily track down repeatable causes.  This is what is needed for them to find the bug and fix it.

Link to comment
Share on other sites

Hey Andrew,

Just like Justin, I also get the shaded/wireframe bug when scaling objects, and having to turn shaded mode on, or turning the objects layer on/off for fixing it.

I also experience that despite changing materials, the object will still display the original material/color untill I switch to Shaded Full and back again.

 

Link to comment
Share on other sites

i can confirm, this has been going on for a long time now. i cannot reproduce 100% but it happens many times. it is also true that opengl buffers are not updated correctly, as m_kisch reported. same behaviour here... nvidia 980ti card here runing on a  macpro 5,1 with osx 10.12.5.

Link to comment
Share on other sites

  • 2 weeks later...

I need to expand on this issue one more time.  I think I have another related issue to memory caching (or whatever this is).  Sometimes when I change a material texture map it does not show up correctly on my model.  The program keeps the old texture in all display modes.  I used to be able to go to File- Project Info-linked files-relink texture map.  That no longer works.  The only way to get the texture to appear correctly is to close the file and then reopen it. 

Clear Rendering Memory?

Link to comment
Share on other sites

I need to expand on this issue one more time.  I think I have another related issue to memory caching (or whatever this is).  Sometimes when I change a material texture map it does not show up correctly on my model.  The program keeps the old texture in all display modes.  I used to be able to go to File- Project Info-linked files-relink texture map.  That no longer works.  The only way to get the texture to appear correctly is to close the file and then reopen it. 

Clear Rendering Memory?

 

I have the same problem/solution.

Link to comment
Share on other sites

  • 2 weeks later...

I found another work around for this issue.  Rather than Closing and Opening the file if I have a problem texture map I duplicate the material- delete the original material-when the program tells me that the material is in use I choose the new duplicate material to replace it.    A little faster but still a glitch.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...