KatsBits Community

Game Editing => IMVU Creator Community => Topic started by: kat on September 29, 2020, 05:26:44 AM

Title: Blender 2.83 LTS vs Blender 2.9+ for IMVU Creating
Post by: kat on September 29, 2020, 05:26:44 AM

Question: Which version of Blender should I use for IMVU Creating.

Answer: at time of writing download and use Blender 2.83 LTS (https://www.blender.org/download/releases/2-83/)

• • •

For those that don't know Blender is now available in two flavours (https://www.katsbits.com/codex/blender-vs-blender/) Blender LTS (Long Term Support) and normal Blender.

Without getting overly technical although the two versions are broadly the same, for IMVU Creating because Blender is aggressively improved and updated, the latest release, currently Blender 2.9+, should be considered 'experimental' and may cause issues when used, especially during export to FBX (https://www.katsbits.com/codex/imvu-export/) and import into IMVU.

As a result preference should be given to using Blender 2.83 LTS which is subject to long term support from the Blender Foundation (2 years or so), stable, and known to work without issue for IMVU (https://www.katsbits.com/codex/tag/imvu/) (assuming there are no issues with content being exported or the steps taken to do that). All the IMVU Starter Files (https://www.katsbits.com/codex/imvu-starter-files/) currently work without issue in Blender 2.83 LTS.

Title: Re: Blender 2.83 LTS vs Blender 2.9+ for IMVU Creating
Post by: whatsortssintorm on July 01, 2021, 06:08:39 PM

Just a quick note about this i wasted a day on trying to work out why when exporting fbx from 2.9  to imvu it was layed down . went back to 2.8 and voila  all in the right place :)

Title: Re: Blender 2.83 LTS vs Blender 2.9+ for IMVU Creating
Post by: kat on July 01, 2021, 06:27:02 PM

Post some screenshots of what you see in Blender and IMVU if you can as that's odd, FBX should export the meshes 'in situ' without needing to be 'corrected' like that, typically positional issues are caused by selecting the wrong skeleton on import so double-check that.