Nimi

Perhaps download the .zip for Mine-imator and replace the world importer you're currently using for Mine-imator with the new one included in the download. If it doesn't work, you can send the error.

This may be a result of varying chunk formats in the world. The world importer only knows what version of Minecraft a world was last opened in, so it has to assume the entire world is in the same chunk format.(Which may cause issues.) You could try to optimize the world in Minecraft via the 'Edit' button in the world selection screen, which will update all chunks to the same and latest format.

@Psycho_Potat0 This is a common issue I have no control over. The program is completely fine-- try disabling any antivirus programs that may prevent it from running or allowing SmartScreen (If you're using windows 10) to allow running the program anyways.

No. Bloom is available in 1.2.0 and later versions, and can be enabled in any camera.

This will be fixed in 1.2.7 when the world importer gets 1.16 support.

A .obj exporter is planned for the next update of Modelbench. There's currently no release window for the update as of right now.

Yes. I don't keep old assets from older Minecraft versions. (Like the programmer textures.)

Can you give more info on what's all in the particle creator before it crashes?

Timeline markers: Planned for 1.3.0. "Sticky"/pinned timeline instances: Not currently planned for any version of Mine-imator. Timeline searching: Not currently planned for any version of Mine-imator. 1.3.0 is far from being done with development, as it still just recently began (though in all fairness, there hasn't much development since this dev update went out) and things that are/aren't planned may jump around a ton this early on. Things you may be hoping for now won't be released to the public till the first pre-release comes out for 1.3.0 sometime next year anyways.

That's outside of my control with Mine-imator using GameMaker.

Blockbench supports a wide variety of different model formats. The only model format you can import from Blockbench that's supported by Mine-imator are block JSON files. Are you trying to load a different type of model?

There's a settings.midata file in the 'Data' folder next to the .exe file.

I already have working assets up to 20w19a with models made by @mbanders.

The next update (Mine-imator 1.2.7) will include support for 1.16 assets and worlds.

As of recently, he's stepped down from being a dev. He has a pretty busy life and other projects going on and understandably didn't have time for Mine-imator development.

I don't think GameMaker is a joke at all, some great games have been made with it. It's just not built to be a base for a fully functional 3D animation software, let alone to the ambitious scale that Mine-imator is. Admittedly the joke here, is that Mine-imator (and Modelbench, even in the complete rewrite!) continues be developed with it. GML (GameMaker language) is the only real language I know to a proficient level other than GLSL ES for writing shaders for Mine-imator, so it's stuck in GameMaker for the foreseeable future. I plan on leaving development whether there's another dev or not after 1.3.0 or following bugfix patches as I would like to move onto other endeavors following the possible next year of development for the next major update. In the meantime, I'll be looking into possible optimizations throughout development since there are a handful of opportunities. So far, Mine-imator 1.3.0 has been updated to the latest GameMaker runtime (Was held off, as newer runtimes would usually break stuff due to possible runtime bugs.) which has given Mine-imator a somewhat-noticeable performance boost, which is very present on startup as it's been reduced by about 20 seconds on my computer. Mine-imator a single-threaded x32 application, as with almost all games made with GameMaker. Rendering all but one core on your CPU and anymore than 4GB of RAM useless in terms of performance. All mesh generation for objects, including bending body parts is done in the same thread as everything else in Mine-imator, causing a slow-down between rendering frames, ultimately dropping performance.

Did you get an error message of any sort you can share? Also, Mine-imator has a backup feature-- set your file extension to .mibackup when opening a project to see them in the window.

Did you mess around with your 1.15.1 assets at all? This line in the log seems to indicate that you have a texture that's at least x1024 in the blocks folder, making the block sheet huge-- resulting in a memory crash.

Looks like they broke when the flattening happened with 1.13, block IDs and texture names were changed in the process. This'll be fixed in the next update.

Probably not. No.

Can you provide a download to a .json file that doesn't work in recent versions?

Really glad to see the feedback so far from the dev update! While this seems like a lot, there's still a lot left to Mine-imator 1.3.0's development and release is still way down the road-- possibly even sometime next year. In the meantime I'll still be giving dev updates to show progress on the update and 1.2.7 may possibly be released to help with Minecraft 1.16 support along with some bugfixes that are currently in 1.3.0, including a fix for issues related to mip-mapping;