I'm getting to know the old editor. I figure if @bob.blunderton can make Los Injurus with it, I can do something simple. But for some reason I cannot rotate the view. All of the other movement controls are the same as in game, but I seem to be stuck looking at the terrain from one direction, which puts a damper on creating anything that's not in a narrow straight line. I can't find it in the docs. What am I missing?
I'd suggest to use the new one as sooner or later the old one with be deprecated so your learning of it will be just a waste of time
The way Bob tells it, the new version has some serious shortcomings. The Beam team would be well advised to listen to the extreme power users before deprecating a useful tool if its replacement doesn't measure up.
I have said this before and I'll say it again: it's extremely dumb to give us the unfinished, non-intuitive and buggy new editor while also keeping the old one for such a long time but not supporting it which makes it even more buggy, practically we don't have a fully working editor and we have to switch between the new and old one, while the original idea was to have 2 fully working ones for a short time before people get used to new editor and then deleting the old one, and some of the bugs are ridiculous such as spawn points not working at all or the new editor messing with car and camera controls, everyone is afraid to use it because of how broken and hard to use it is, and it also crashes a lot (at least for me). Don't get me wrong, I'm not one of these new editor haters who refuse to use it, I use it more than the old one, but some things seem impossible to do with it or the options for that are too hard to find, and each game update fixes one thing but breaks something else in it. Why can't we just have the new editor with the UI based on the old one so it's equally easy to use??
I agree completely. I got my navigation controls figured out, but now I've got a mesh road that rendered itself when I created it, but un-rendered when I exited the editor, so I have an invisible mesh with no collision properties. Editor 1 docs (which are pretty detailed) say nothing about troubleshooting this. --- Post updated --- Problem solved. I was playing around with one of the official maps, so I figured whatever texture I picked would actually exist. Turns out that's not a solid assumption.
