koobas.hobune.stream
None of my Blend files are reading anymore
I just downloaded the new version of unity and every single mesh I had imported is no longer working. Is this an intended issue with the new version of unity or is this something that is broken and is being fixed? I don't understand how it was working fine in the last version and all of sudden it doesn't at all anymore. I get upgrading your engine to make it better and more efficient, but is it really necessary to keep removing old systems that people relied on? I had just mustered the willpower to take on the monumental task of learning C# and rewriting all of my scripts and have been busting my ass over the last few months getting that done and now this? I hate to just sound angry and bitter, but this is just... not sustainable. Am I supposed to not upgrade Unity at all? Because I did that for a while and I was unable to even build and run the game outside of the editor anymore. I guess the question is, is this issue with my blend files not reading all of a sudden a known issue that is being patched and fixed or am I really going to forced to re-import every single mesh I have imported? Because if it's the latter I don't think I can keep doing this...
That is pretty lame. Can you post a screenshot of the behavior you're getting from the newest editor? What are you doing manually to resolve it?
Yeah, well I screwed things up way worse. I panicked and uninstalled the most recent version and reinstalled the last one and now the compiler is all screwed up. The blend files are all working again. Now Im wondering if I should reinstall the newer version and reimport it to fix the compiler. That would probably be better for sending a bug report, as what I would have to send them now doesn't even have the original issue. Blah, screw it I still have all the blend files set up correctly on a different computer from while I was still able to use action script. I'll save the new C# scripts Ive done and hope it reinstalling and reimporting does botch things up worse than the original upgrade did.
There are probably some lingering 2019-relevant files and settings. You can try deleting the following and letting Unity reconfigure your project to target the current editor version, just make a backup first:
Builds/
Library/
obj/
Temp/
Assembly-CSharp.csproj
Assembly-CSharp-Editor.csproj
[Solution Name].sln
I would send in a detailed bug report of this issue to get confirmation if this is intentional or just a bug. I would personally be kind of upset if blend file support was removed. Please post back with the response from the bug report. I don’t know if you have ever sent a report in, but unity is quite quick to respond in my experience with reporting bugs
Same here, I have a the same question open atm. Ill share if ever I get the answer first. Note that many people suggest simply exporting the fbx file from blender and replacing it in Unity if you wanna solve it quickly. But we both wanna stay with the good old blender files, ey?
Heres the link to $$anonymous$$e : https://answers.unity.com/questions/1622769/blender-could-not-convert-the-blend-file-to-fbx-fi-1.html
One more thing for you to keep in $$anonymous$$d before updating Unity: BAC$$anonymous$$ UP all of your prefabs. On my recent update, all project's prefabs got reset to 0. Spent a few weeks recovering the setups (had to install older Unity I had project backup for, and lookup each prefab setting)
As a new user to Unity, I also wonder if it's advisable or not to update Unity while we're working on something. $$anonymous$$any older tutorials don't work anymore, and I assume if I had an old project it wouldn't work now either. Consequently I have to assume that whatever project I'm working on now, will have to be updated as well at some point, as the requirements of Unity change. Is using an outdated version of Unity even an option?
Worst thing in new Unity versions is Prefab editing. Before that it was UnityJava removal. Then internal build was gone. Then there's no $$anonymous$$onoDevelop shipped with Unity and much more. So: when you start a new project, make sure you label current version of unity it's started in, and burn that unity version to a DVD, to use with the project. Update unity, no problem, but after updated, install the other one, to run older projects on it. I have 5 Unity versions installed :)
Here you go buddy : https://answers.unity.com/questions/1622769/blender-could-not-convert-the-blend-file-to-fbx-fi-1.html
Turns out you need blender beta for to be compatible. DO NOT REMOVE YOUR CURRENT BLENDER, Unity 2019 is only compatible with the Beta, but every other version of unity cannot use Blender Beta.
Whelp... all of my models have imported, now Im running into a slew of new problems. I know before I ask that there isn't going to be an easy solution to any of this, but all by prefabs have been disconnected from their root models, so anything I had animations on now aren't reading any animation files (yes Im using legacy). $$anonymous$$ost of the materials have been removed as well, but strangely some are randomly still there... I think it has to do with the stuff where I changed the materials they were imported with after they were imported, which I don't see having a fix for. Pffftt, this is gonna be a lot of work... Jesus aren't you supposed to look forward to updates and be excited about the new features? I dread every time I update Unity cause its crap shoot on whether my project is gonna even work after.
