Upgraded project to 2017 from 5.5.2
TMP doesn’t work, k…
Find online the “fixed” dll for 2017, replaced it
Seems to compile and work
Open scene with metric tons of TMP gui texts
Every text is corrupted.
Missing script
Click on select script button, select TMPugui, all fields are blank
Realise i will have to manually redo the whole damn projects text
Realize i will not do that
Come here in search for a solution.
As per the Release and Upgrade notes, prior to upgrading to a new release, you have to first remove the previous version by deleting the “TextMesh Pro” folder. Then you import the appropriate version for the version of Unity that you are using.
Always be sure to back up your project first as well as any files you may have saved in the TextMesh Pro folder hierarchy. Be sure to also review the TMP Settings file, Stylesheet and other TMP assets you may have modified.
If you were using the Source Code (Paid) version of TMP, as per the IMPORTANT NOTE on the Asset Store page, you will need to get the updated Source Code version of TMP from the TextMesh Pro user forum. This is necessary as the GUIDS of all scripts and assets is different between those two version due to how dlls are handled. Ie. If you are using the free version, stay with the free versions. If you were using the paid version than stay with the paid / source code version.
Provided you follow these steps the upgrade process should work without any issues.
Yeah you’re right i just retraced everything but this time deleted tmp folder before updating and it works.
Can you tell me if after the integration will you replace unity Text with yours?
Or we will have 2 versions of text.
For legacy / compatibility reasons, the old text components will likely remain for a while.
So projects using TextMesh, UI.Text should remain untouched. With respect to the current TMP components, I would like to automatically switch those over to the new integrated version provided we can get 100% conversion. Otherwise, users may have to manually make some changes / tweaks.
Ah yeah lol you have access now to unity updater. Should automatically rename everything. Any eta?
Besides continuing to provide support to TMP users, my primary focus is on this new integrated version / new text system for Unity. I don’t have an ETA yet other than not before the end of the year.
Having said that, if there are opportunities along the way to release / add some of the new core pieces to the current incarnation of TMP, I would like to do that. This would allow for the transition to the new system to happen over time as opposed to all at once which could / hopefully make this smoother.
Unity you guys need to find a better way because messing up years of work like this is not ok. Seriously, I’m so annoyed right now. and I’m only updating because stuff in the existing version doesn’t work. Here’s a novel concept: FIX EVERYTHING THAT’S BROKEN AND THEN WORK ON MORE STUFF. Ok? great.
What specific issue are you having?
I upgraded to see if there was any performance tweaks on volume lighting because i can’t crack 40fps in full view, and the update was actually worse (not for lights, but for turning off 4k+ meshes with the cloth component). So I entered a new issue while trying to see if another was solved.
In 2019.3 cloth was perfect, but now in 2019.4, there’s a noticeable lag where the system freezes for a bit and then loads the cloth component. It’s very annoying when I swap models during gameplay, so I’m going to have to rethink how i approach that.
But when I noticed things were worse, I tried going back to 2019.3 and I ignored the warning because “how much harm could it do?” and it harmed everything, i can’t even press play because it says things like the gui system is unknown–am I missing an assembly reference? That kinda thing. The same lag for enabling cloth was found in alpha versions 2020.1/2. I had recent saves on my computer, but none that could bring me back to 2019.3, so I’m living with the performance hit, now.
And also, upgrading from 2020.1 to 2020.2 asks if your external plugins are missing assembly references as well for common things like the animator component and gui system. This wasn’t due to a downgrade. It happened going from 2019.4 (as I tried to escape the performance hit) to 2020.1 (where the problem still was), to 2020.2 (which broke everything because apparently you can’t upgrade between alpha versions? I have no idea).
I used one of my backups to upgrade (I think with my last clean project folder for 2019.3 where things worked) straight to 2020.2, where the assembly reference errors were when upgrading from 2020.1. Once in 2020.2 I saw the performance hit was still there when enabling and disabling the cloth component. I know 2019.3 didn’t have this issue because I have very old backups I refuse to go back to (because I’d have to redo weeks/months of work) which I’m able to compare things with.
There’s no warning of not being able to upgrade between alpha versions. It’s crazy just how carefully you gotta navigate this stuff. And it’s not quick to copy a project you’ve been adding crazy amounts of content to, or esp upload it all to submit a bug report that never gets responded to. Nor are subtle demons like upgrading between alpha versions destroying an entire project because of some assembly reference nightmare ever prepared for those of us who are not psychic. I’ve gotta copy my project folder and wait an hour for the content to transfer before I can try ANYTHING new.
And after transferring my project to a new computer after my graphics card on my desktop died while running unity, the intellisense feature in visual studio code doesn’t work by default. I have to open the c# project from the assets menu and then disable > enable the ms c# plugin for vs code. Color me annoyed at this point. I’d probably be done with this project by now if unity played it as safe as I’m forced to.