Is there any point to reporting bugs on a build on super experimental mode? I’ve managed to get a seemly working project with net code, visual scripting and on 2019.3 release candidate. As stated on the visual scripting thread, anything but the given project is not given support. Especially since it’s very probable that the mishmash of unexpected package versions is the cause of the bugs and I wouldn’t even know which of the experimental packages is the faulty one
The point of this project is to get started on a 100% pure ecs project from start to finish, and at the same time, get used to using the experimental packages and features on something that will eventually become a real project.
Currently, however, the project is on a stand still for these two reasons:
When Burst is enabled: Mono: successfully reloaded assembly- Completed reload, in 9.024 secondsPla - Pastebin.com
When Burst is disabled: Mono: successfully reloaded assembly- Completed reload, in 9.079 secondsPla - Pastebin.com
Project: https://www.mediafire.com/file/ivlvvkr5d2508s2/Untituled_DOTS_MMO.zip/file
manifest.json: manifest.json.txt
On a side note, some materials that should’t be, are pink, even though they show normally in preview
The code preview from the visual scripting seems to not be updating, or the visual scripting will always remove all unused nodes, therefore the code preview wouldn’t change because the compiled code didn’t, even though I added/removed some nodes that lead nowhere and never wrote anything to anywhere
Seriously, update the forum, I can’t upload a .json file? What about when the nothtml+notcss UI editor gets released? I won’t be able to upload those files either?
5289372–530742–manifest.json.txt (2.08 KB)