Dev update #20: 2020 wrap-up and 1.3 progress update

[Nimi 7604]

Greetings animators. And happy holidays!

I know this year has not been easy for any of us-- from million-acre forest fires, a worldwide pandemic, and everything in-between. I am sure the long wait for 1.3.0 has not helped either. To end this year on a high note, I'll be sharing a progress report of what's been going on with 1.3.0's development, showing how it'll play out until release explaining why this update is taking a while.

Inventory

In the previous Dev update, I mentioned Inventory, the new design language designed by @Voxy planned to be in the next update. I have been working solely on Inventory's addition since early September (Before the last dev update!) and still working on it. Since Modelbench's full release, Voxy has been hard at work refining the design language. Nothing too extreme, these changes are far more visually appealing and coherent than ever before. I plan on finishing Inventory sometime before next Spring.

The endgame

After 5-7 months of Inventory's development, I'll be moving onto more graphical features I still have planned. Afterwards, I'll be looking into optimizations to help with render times like frustum culling which will help with off-screen objects. After all this, I think it will be Summer and close to the next Minecraft update. I will be taking the remaining time to refine and polish the update for public pre-releases soon after Caves & Cliffs releases in late Summer. It will be a long wait for sure, but I am sure it will be well worth it!

That's all I have this time around; I don't have new features to show since Inventory is my top priority till Spring. Until next time, I hope you all stay safe and have a happy new year!

[Diogo 3]

Ok

First

[Creeperzio 0]

Ok thx FoR YOUR hard work

[Leonjr4TheGamer 0]

nice

[BladerInc 138]

Keep it up!

[Diamond Darrien 5]

good thing we're patient to wait. keep up the good work, Nimi!

[Kwazedilla 1438]

gg

[Asnail88 39]

Thanks for update, Happy New Years!

[LacaMenDRY 268]

Happy New Years Everyone! And It's my birthday. 

[HeYoNia 1509]

5 hours ago, Nimi said:

Afterwards, I'll be looking into optimizations to help with render times like frustum culling which will help with off-screen objects.

Now this is epic.

[KEJWII 1]

I wonder if there could be a Mine Imator "Early Access" version

What is it
"Frustum culling"
Bullet frustration?

I really don't know, can someone explain?

Edited December 31, 2020 by KEJWII

[AJFM AnimateMC 4]

3 hours ago, LacaMenDRY said:

Happy New Years Everyone! And It's my birthday. 

Happy Birthday Fellow Animator and Happy New year To all of you

[LeafCold 2]

thx，happy new years

[MoltenLapizza 216]

13 hours ago, Nimi said:

frustum culling

Oh my god

[_Xean_ 232]

Happy new year all!

[moniker 36]

"Frustum culling"

So we will finally be able to work with smooth FPS while having loaded big schematics and cubes/objects? As it stands Mineimator FPS slow downs so easy after you add an schematic, some cubes and objects for the finishing touches + have 2 or 3 minutes of keyframes. Also having the Camera window and "Toggle controls, wireframes and highighs in this view" enabled makes it worse.

 

Btw I have found a strange Memory leak:

 

Something on that rig causes Mineimator to consume an infinite amount of RAM (it keeps going up until it collapses). Tested on both 1.2.6 and 1.2.7.

Edited January 2 by moniker

[CRAZYKOKEBROZ 43]

4 hours ago, moniker said:

"Frustum culling"

So we will finally be able to work with smooth FPS while having loaded big schematics and cubes/objects? As it stands Mineimator FPS slow downs so easy after you add an schematic, some cubes and objects for the finishing touches + have 2 or 3 minutes of keyframes. Also having the Camera window and "Toggle controls, wireframes and highighs in this view" enabled makes it worse.

 

Btw I have found a strange Memory leak:

 

Something on that rig causes Mineimator to consume an infinite amount of RAM (it keeps going up until it collapses). Tested on both 1.2.6 and 1.2.7.

If it’s a rig causing it then I wouldn’t entirely say the software itself is the problem.

[moniker 36]

On 1/3/2021 at 1:30 AM, CRAZYKOKEBROZ said:

If it’s a rig causing it then I wouldn’t entirely say the software itself is the problem.

The memory leak is happening inside Mine-imator.exe, hard to argue it isn't the software.

[CRAZYKOKEBROZ 43]

6 hours ago, moniker said:

The memory leak is happening inside Mine-imator.exe, hard to argue it isn't the software.

It came from the software because it was being overdone by the rig!

[Aric Horn 0]

hey nimi before you release this in the summer time, i want you to add this feature in the resolution..

"QLED 8K" this feature will make renders look fantastic in 8K resolution, people has been requesting this for almost 2 years, this feature might be perfect for the 1.3.0 lighting and graphics

[Nimi 7604]

1 hour ago, Aric Horn said:

hey nimi before you release this in the summer time, i want you to add this feature in the resolution..

"QLED 8K" this feature will make renders look fantastic in 8K resolution, people has been requesting this for almost 2 years, this feature might be perfect for the 1.3.0 lighting and graphics

Due to the new graphical features, exporting 4k renders and animations will be difficult for the program.(Depending on computer specs and what settings are enabled.) I can't imagine Mine-imator handling 8k exporting due to the memory requirements of the resolution. Besides, you can set a custom resolution if you need or want to try 8k exporting.

[AJFM AnimateMC 4]

7 hours ago, Nimi said:

Due to the new graphical features, exporting 4k renders and animations will be difficult for the program.(Depending on computer specs and what settings are enabled.) I can't imagine Mine-imator handling 8k exporting due to the memory requirements of the resolution. Besides, you can set a custom resolution if you need or want to try 8k exporting.

in short we can just use the custom resolution on the camera to make it 8k. Right?

[moniker 36]

On 1/5/2021 at 1:10 AM, CRAZYKOKEBROZ said:

It came from the software because it was being overdone by the rig!

The rig is not some super complex thing, it's just a medkit with some stuff inside. There's clearly something wrong going on in there.

[CRAZYKOKEBROZ 43]

4 hours ago, moniker said:

The rig is not some super complex thing, it's just a medkit with some stuff inside. There's clearly something wrong going on in there.

Because there is a component (or two) within that medkit that is consuming all of the data. This causes Mine-Imator to act slow and then crash. There is literally nothing wrong with the software.

[moniker 36]

On 1/8/2021 at 12:54 AM, CRAZYKOKEBROZ said:

Because there is a component (or two) within that medkit that is consuming all of the data. This causes Mine-Imator to act slow and then crash. There is literally nothing wrong with the software.

This is not how software development work. You have to put barriers in your software so memory leaks never happen.