3 ms·
This essentially seems like you're ticked off at one feature and everything else is beside the point. If you follow one of the links in this thread: http://fee
by podperson 14y ago
This essentially seems like you're ticked off at one feature and everything else is beside the point. If you follow one of the links in this thread:
http://feedback.unity3d.com/unity/all-categories/1/hot/active/allow-symlinks-on-windows-and-os http://feedback.unity3d.com/unity/all-categories/1/hot/activ...
You'll find that the Unity folk disabled symlinks to avoid thorny edge-cases and are trying to figure out a way to give you what you want, including simply allowing sym links but generating a warning message (and Windows devs are suggesting using a junction link -- no clue what that is).
It seems to me that the best option would be for Unity to expressly support the inclusion of folders outside the project tree in projects.
The engine being "six years old" is somewhat beside the point. Major changes and improvements have been made to the engine have taken place, and in some cases these have been as dramatic as "from scratch" rewrites.
- reitzensteinm 14y agoWhat I'm saying is that after six years, there is still no support for something as basic as classpaths, which I'd consider part of the MVP to be using something like this full time. It seems you disagree, but many people have popped up in this thread with the same complaint, and workarounds they should not have to be making. I have no problem with the 3D rendering part of Unity, it's fully featured and works well. Especially for the price tag. Agreed that age being bad is a nonsense metric. I was saying the opposite - it should indicate polished workflow. Ticked off at one feature is not an accurate assessment at all. If lack of classpaths were my only problem, I'd be in love with the product. I don't think it's a bad engine either. I was just expressing my concern for where they're choosing to spend their effort.