htharker1

Issue definitely not resolved. Latest driver and nothing has changed. What a shame!

Try deleting the ultra folder in the windows programdata folder, you’ll need to reimport your project but it should launch perfectly fine next time also by the looks of it the standard unlit and PBR shaders aren’t loading. Shutting down and restarting ultra should fix that

So I’ve had an issue ever since I first got Ultra. After modifying vertices or moving geometry, after ten to twenty minutes of the editor being open, the grid on the three 2D viewports corrupts and dissapears, making the engine pretty much unusable. Even stranger is selecting a face doesn’t show as selected when it is in this state, but actually is selected, but just invisible. Also makes copying and pasting something actually paste, but not appear anywhere in the viewports so it’s confusing to say the least. The behaviour returns to normal only after restarting the editor, but I’ll always get the issue again after around twenty minutes of use. The issue is very easy for me to replicate, as it happens nearly guaranteed if I vertex manipulate brushes manually. Likely a compatibility issue with AMD. I use an RX570. ———— Also occasionally getting a crash when selecting a vertex and attempting to move it. Very unpredictable but I think I’ve narrowed it down. It seems to happen because sometimes when dragging a vertex point, it’ll move itself further than I intended at complete random. I think the crash is caused by the vertex trying to move itself so far it crashes the editor. ———————— Also noticed exceptionally long save times recently in the beta. A map file that usually took around ten seconds now takes upwards of two minutes to fully save. —————— Finally, I’ve noticed some very strange texture application on non square brushes when edges are set to any number other than 0. Will attach an example map file tomorrow to show what I mean. —————- Sorry for the four bug reports in one, didn’t want to litter the forum aha.

Could be related, after being on the editor for over twenty minutes and being active moving and scaling geometry, sometimes the grid in all viewports disappears entirely until the editor is closed and reopened.

RTN.rar After altering a few lights on my map, I accidentally changed a value I didn't mean to, and as a result my file absolutely refuses to load. This was caused by altering the light range values, accidentally putting the start of the range to further than the end of the range. I don't suppose it's possible to manually remove the lights from the map file without loading it at all is it? Otherwise it'll be another case of having to restart the map from scratch.

So basically the RTN file was my first initial map. I tried to get rid of the offending geometry via text editing but in doing so I must have basically destroyed the JSON structure, so I'll have to restart anyway. Thanks for the fix, works like a charm!

After modifying geometry via vertex manipulation, maps no longer load, simply displaying "Assert Failed" and crashing to desktop. I've been able to reproduce this error in its most basic form, however to fix it would require manually finding the offending brush in a text editor and removing it, but on a larger map that is nearly impossible to pinpoint. To reproduce, create a box, use face manipulation to move one side of the box up or down, then modify one of the corners with the vertex tool, then try to duplicate the box. Please see attached, hoping there's an easy fix for this otherwise I'll lose a lot of progress! map_crash_test.rar