MODO | SMO GAME CONTENT Kit for Modo 12.X – Beta 1.30

Hi everyone.

SMO GAME CONTENT Kit  is Out.

This kit focus on creating Kitbash of assets and Game Content development for Unity.
(UE4 preset are currently in dev).

I want to point out also that it could help a lot your production on other stuff than Game Content.

  • ArchViz (it can help you to build large library of Assets as Mesh Presets)
  • Product Design (for creating variration of the MeshFusion or morphed animation)

I’ve built it up over years of daily work in Modo, to speedup my workflow as well as avoiding any issue when dealing with new release of Modo.

As always, nothing could be done without the support of all the community over the years. I want to thanks again, William V, Seneca M, Cristobal V, Adam O’H , Mario B, Yazan M, Richard Y, Ymmanuel F, James O’H and every other Kit Developers that have empowered Modo along the way. It is an inspiration for everyone.

For a short period of time and as it is still a Beta,the price tag will be at 15 $ till 4st April 2019,
then i will grow it up to is standard price at 20$.

The Main Animated MeshOp Exporter as FBX or LXL is at least Gold Ingot, but there is so much more in the Kit.

As usual, i’ll release it as a Beta, starting from release 1.30. I’m currently cleaning, adjusting and converting or removing scripts, depending on the interest of users as well as their perspicacity for this Master Kit. It’s the biggest kit for me in terms of content. It’s far more easy for me to do Meshops preset for sure, but the challenge worth it i think for the pleasure of everyone here.

For all updated information please have a look in this thread and contact me on Twitter or on the Foundry Slack server or on Foundry Forums  :  

Best regards, Franck.

 

It comes 3 different Key Topic in mind.

1: Improving the Procedural MeshOps integration to your pipeline.
Having the opportunity to speed up Asset modeling iteration via Procedural workflow can be really powerful, and give you more time and flexibility.

2: Understanding how Modo works, in order to tame it easily.
It include bunch of commented Fragmented Config file that will help you understand how Preference / Keymap / and UI works in Modo.

3: Improving Workflow via Pie Menus, Macro and Scripts.
A Master pie and a set of other sub Pie in it. All Key mapped, with loads of Script and Macro to speed up everything you may need during Assets Development
les and for LXL Mesh Preset files.

 

Update Log:
2019/03/15 – Beta 1.35 – Compatibility Improved
Test passed on Modo 12.0v1, 12.1v2, 12.2v2 and 13.0 RC0

2019/03/14 – Update: Installation walk through video

Fan boys Mode ON: Slack Modo theme.

For those who always wanted to get a better contrast and comfort when reading the slack channel of Foundry, you’ve probably wanted to get a Dark Mode. So here are the steps to follow.

darkmodeslack

First of all follow the video below. and take a moment to copy the code right here.

this is the Hexadecimal color chain for the Sidebar color preference.

#484848,#949ca4,#f49c1c,#FFFFFF,#3e3e3e,#FFFFFF,#2BAC76,#CD2553

Now that we’ve changed the main color theme, we need to edit a JavaScript , because well Slack doesn’t offer right in the bat solution for a dark mode.

  • 1. Open your installation folder of Slack:
    (located under C:\Users\___YOUR_NAME___\AppData\Local\slack )
  • 2. Then search for that File: ssb-interop.js
  • 3. Edit it with Notepad++ or any Text editing software.
  • 4. Now add that code bellow to the end of the that file.
  • 5. Close Slack (don’t forget to close it totally by Quitting the app in lower right side of your Taskbar.
  • 6. Restart slack.
    enjoy

For their Awesome blog post thanks a lot to siecledigital.fr

Good job.

DyneRR Update 1.72

DyneRR Update 1.72

  • Fixed the Aspect ratio bug if you were using a ratio of 1.5 for the render  (1920 x 1280 pix). So now you can use any resolution you want.
  • Fixed a Bug in the Render Margin that was not updating the RenderRegion in Vertical values.
  • Discounted by 20% here
  • New tutorial in FullHD here:

DyneRR – Dynamic RenderRegion for Modo – Released

Hi everyone.

Here is an assembly that may speed up your rendering with ease and with affordability.

Available on my Gumroad page.

(New tools will come soon aside of this first product.)

Lire la suite

my humble contribution through bug reports on Modo 11.

Foundry Dev Team is aware of those things, just to keep informed Modo users. I hope they will be fixed soon.

Bug 55319 – Let users add grouped mesh items to the sources of MergeMeshOps

Bug 55386 – [Regression] Bake to Render Output from Shared UV Map causes Incorrect Results via Network Rendering

Bug 55429 – Hard Edge Smoothing is not Preserved onto a Procedural Layer when the Source Meshes have Rotations Applied

Bug 55477 – Using a procedural Boolean operation after a Transform operation causes Display Errors in the resulting mesh

Bug 55478 – Snapping to Intersecting or Overlapping Components Does Not Work Reliably

Bug 55517 – Boolean subtract of intersecting meshes produces bad result

Bug 55522 – Baking AO via Network Rendering does not Work

Bug 55550 – Snapping to Components in a Scene with Dense Items can cause Erratic Snapping Behavior.

Bug 55554 – [ER] Allow Replicas contained in a Replicator to be defined as the source of a MergeMesh operation

Bug 55663 – Motion Blur on a curve inside a MeshOps no longer works

Bug 55744 – pMods Simulation is very slow when driving an animated MeshOp, even when there is no collision

Bug 55745 – [Feature] Allow the Curve Rebuild Procedural to rebuild the strips of a Mesh Fusion item as a curve.

Bug 55755 – Clone on Curve Procedure does not update live if the source mesh is altered

Working at Extriple: infuse a new step to AR/VR creativity

First of all, i’ve didn’t talk a lot about my new job at Extriple and that’s all about i’m posting today. I’ve join the team in June 2015 at first for a Freelance work and then started a full time job to their office 3 month later.

c1e70929e10824273ff29e8c58da1753

our Industrial Helmet Concept

Working in a Korean company is a great way to discover the Korean citizen, that you usually may have some prejudiced or biased against them as you’re a citizen of Europe or any western country. If you’ve never thank that you’ve being a stranger in a country before, you couldn’t feel that unforgettable feeling. It make me breath now as a human more than a french guy that you can see coming a mile off.

Living not as an expatriate and be a part of a company that have not tried to recruit you just for international business or expansion strategy was a breath to me. Even if i should assume that my Korean level is not actually as good as my english, i must thanks them for their listening. Hopefully i understand most of their needs and meetings, so i can’t say that i’m just lucky. Hard work of studying at the ChangWon University to learn korean (not as many as i should, i must say), was also the good choice. I’ve give up a few times but didn’t stop to trust in my capability to communicate and work in a team as a foreigner.

I’m really glad to thanks 노진송 the CEO for is faith & also the support of all of my friends from the CW University as 박동규 professor &  안태현.

From research on AR (aka augmented reality), MR (mixed reality), to Product/Brand Design and Mobile Application, it have let me explore more possibilities in 3D, from Rendering for Archviz to Animation and Real Time content creation for Unity Engine, PBR and many other stuff around.

 

Development on Microsoft Hololens are now on the way, with the help of Unity. It’s pretty impressive what we can offer already for industries who want’s to communicate their visions to the audience, or have some tools for Production Data Management. It’s really a new era that is coming out from the ash of VR research and product in of the 90’s. As i’ve said before on Twitter, if you look to the marketing around them, you’ll may be disturb by the gap between people expectation and reality, but the wild horse is on the way and we couldn’t see it stopped by anything, because actually the environment is ready for huge improvement on the software as well as the hardware further generation of Hololens and competing solution.

I must say also thanks to my daily co-workers: 김용벡, 윤채영, 김경민, 김동현, 서혜정  that makes life easier in the company. I’m sure we’ve shared good moments (and also bad moments, but we’ve bypassed them with glory and humility) and i’m sure there’s much more to come for our pleasure. Challenge are there, but by then it have been great to work together improving our skills and company.

Industrial Data Visualization and Management product

About the Decisive Importance of Baking 16 Bit Normal Map in Modo when working with Quixel Suite or for any PBR oriented Workflow

So I’ve dig a bit more on the workflow to make good PBR ready Assets to be used in Unity or any tool as MarmosetToolbag. QuixelSuite 2 have came out since a few days at that time.

As far as i remember, I’ve got plenty of bugs and issue trying to use correctly Normalmap. and in those issue, their is one that have kick my head for a long time. And now as I’ve fixed it, i must share it.

Keep in mind that, this nDo Project was made in 8 Bit. Not in 16 Bit, that could explain those errors by loading an 8 bit file into a 16 bit project…Ughhh)

So here you could see 2 different maps that I’ve imported into the nDo PSD file project. You may not see any difference, but there is.

One was made by overlaying independently an 8Bit & a 16Bit NormalMap baked into Modo using the simple BakingUI Script on a simple mesh. Notice that I’m using a Cage MorphMap during the baking to prevent any RayTracing missed error.

16&8_Bit_NM_FromModo_in_nDo_Compared
As you might see here with a magnified view in the 3Do viewer, there is some weird Artefact that appear on the 8 Bit instead of in the 16 Bit.

Even if we are working in 8 Bit in that nDo Project, flat areas in the model got too many artifact and that’s really annoying. especially for HardSurface Model.

8Bit_Baked_NormalMap_From_Modo

8Bit Baked Normalmap (Yes Artifact and not Artefact ;^)

16Bit_Baked_NormalMap_From_Modo

16Bit Baked Normalmap (Yes Artifact and not Artefact ;^)

So, to conclude:

Take in mind, that you Should Bake all your Normalmaps in 16 Bit ANYTIME (PNG or TIF file format), even if you want to produce 8 Bit Normalmap at the end of you process.

Artefact_8Bit_16Bit_SetupModoBake

Clic here to view larger image