Studio: Mesh Display Issues

Hello,

I’m a relatively new member of the dev forums (having joined around 3 or 4 months ago) and forgive me if I’ve made any mistakes regarding where this should be posted or if there’s anything I haven’t included to make this descriptive enough. I’ve been experiencing this graphical issue on studio where the poly of the tree mesh I use in my game ‘Steam Age’ appears to glitch and go all the way to 0,0,0 in the workspace.

This doesn’t occur in-game online and it seems to be a studio-only thing in my case. I updated my graphics card drivers (I use a GTX 970M) only a couple of nights ago and this issue still seems to be reoccurring. Not only are meshes affected by this but also unions (as displayed below); it also appears that in the second image that some parts of the tracks are missing as well, it’s also like this on other parts across the map.

The only possible solution I’ve had to stick to in regards to this issue is to simply relaunch the place on studio and hope this issue doesn’t return again (to which unfortunately it does eventually).

There’s nothing I currently know of which reproduces the bug though a friend and I suspected that it could just be a graphics card related issue. Alongside all of this, the bug had only started happening very recently (around a couple of weeks ago). I hope this gives people an idea of the issue I’m currently experiencing and I’d be thankful for any support on this.

2 Likes

Seems like the same bug as this one:

This seems to happen because the engine cannot read/find the data attached to some vertex index (location, topology is preserved), so it gets put to (0,0,0) instead of the relative position it should be at.

Maybe the following information would be helpful to add:

  • More system specs (OS, graphics driver version)
  • How many times do you need to open the place (approximately) for it to happen once?
  • Does it only happen with one specific mesh?
  • When you insert the mesh on its own in a file and open that several times, can you still get the bug to happen?

It might also be helpful to send this place file (or just the file with the mesh on its own) in a private message (on the devforum) to @Silent137 along with a link to this thread so he knows what it is about.

Sorry for the late response. I’ve experienced this issue only at random given times that I’ve opened studio. Prior to addressing this bug, I had only last opened studio over a day ago. I believe that it does happen with the specific mesh (MiniForestHat mesh - Roblox) only and in relation to the forum post you referenced, it affects some unions as well; I also created a place with just the mesh on it and opened it several times - I couldn’t get the bug to reoccur.

My only guess is that it could be the multiple instances of the mesh causing it to happen or it could just be a graphics card related issue as noted in my first post.

Additional system specs:

  • Windows 10 (64-bit)
  • GTX 970M (version 378.66 - most recent one on Geforce’s website for the 970M)
1 Like

The corrupted polygons are all connecting to 0,0,0 and can be fixed temporarily by selecting the model or part.

I don’t quite see this problem anymore but you should only see it in Studio.