This is probably posted in the wrong section for which I apologize, but I feel it should be known by someone in control of such a thing. In Unit 4 of Create With Code 2 for Unity 6, there are two different links to two different Unity packages for Prototype 4, neither of which are correct. One of them is 730 KB which has no scene apart from the sample scene and already has the scripts presumably completed. The other is almost 25 MB and seems to contain assets from all 4 Units, maybe more, and doesn’t have any scenes at all. I’m not sure what happened there, but it certainly doesn’t seem intentional. Anyways, as I said, this is probably posted in the wrong section, so I apologize for that, but I felt that someone should be made aware in case it was an error as seems to be the case. I suppose I’ll use an older version of Unity though to get through this Unit. If it’s somehow operator error on my part, then feel free to disregard.
I have run into the same issue just now. The solution was to delete the project, create a new one and use this package, which I found linked in this PDF of the Create With Code course.
Some materials looked pink (like the island/platform) and the solution was to select them and click Edit → Rendering → Materials → Convert Selected Built-in Materials to URP.
Still very weird that the packages linked in the course itself are unusable. Hope they fix it soon
Thank you so much i was getting ready to throw myself out the window but this worked 100%
I just ran into the same problem on Unit 4 of the Junior Programmer Pathway. It prompts me to download the 25 MB Unity package that contains no scenes. Thanks so much @irasac!!
Hi there! I’m so sorry for the confusion this has caused. We’ve resolved this issue now and the updated files can be found back at this tutorial:
The Scene is still not there. I am using Unity 6 version.
It does not appear that this has been corrected yet. The starter package for unity 6 is still a bunch of random alphanumeric folders when unzipped
Oh boy — I’m so sorry about that. It looks like we might have been having some issues on the back-end. Could you please try it again when you have a moment? It seems to be resolved now when I just tested it:
Thanks. Yes the issues appears to be resolved.