G3 E.A. crashes as soon as I try to export a macro:
G3 E.A. crashes as soon as I try to export a macro:
I also get crashes when trying to export a macro. I hadnât made one yet, so I was making the âfloorlinâ that Dax mentions in the Gaea 3 EA Video.
I have a question though, whatâs plugged into the âinâ macroport you have?
I went through the documentation (as I hadnât made a macro yet since I was waiting for Gaea 3), it also shows something going into the âinâ macroport, but doesnât explain what that is.
Due to the production lean on G3, there are still pending changes on the docs online.l, theyâre done just in wait.
For macros workflow youâd build the idea that you want the macro to do ( try thinking one thing to not overcomplicate it)
Say you wanted to make another kind of scatter node.
You would have some kind of in like. Primitive radial gradient, macro in { yourScatter} macro out.
When it comes to building the macro for export though youâll only want the macro in our and the stuff between.
So the incoming data is just for your reference initially while building and testing.
Hope that helps
Iâll double check this too tomorrow, I may have had success on a different build and it may not be fully implemented yet.
Thatâs what I thought:
MacroPort (set to input) > The thing being turned into a macro > Macroport (set to output)
The crash occurs too without the incoming data = with only Macroport in, the thing being turned into a macro and MacroPort out.
Hey @MarcSaunier @GTJohn,
Iâve managed to have a look, and for EAP the following applies:
| Macro Functions | Functional in EAP |
|---|---|
| Create Macros | Yes |
| Export Macros | Yes |
| Import Macros | Yes |
| Use Macros | No |
The workflow hasnât changed since Gaea 2 Docs.
What this means for EAP, though, is that when you go to insert a macro from your toolbox etc., it will have a version restriction message:
EAP Helper
G3EAP_MacroHelper.terrain (19.6 KB)
You can still create build and export in G3 EAP, but you have to ensure on export that your end results validates the bottom green groups requirements. ( this is the main issue youâre both currently facing based on your above videos/discussion).
Docs (to be published)
Hope this helps you both.
Thank you Ty.
I have 2 macros ports, one âinâ and one âoutâ, both displays set to âHighfieldâ.
macro port âinâ is plugged into the in of an erosion 2 whose out is plugged into the macro port âoutâ.
Most of erosion 2 parameters have been bound to a new variable.
âyou have to ensure on export that your end results validates the bottom green groups requirements.â:
Here, I unfortunately dont understand/see what itâs about ![]()
Here is the file
G3Macro003.terrain (14.3 KB)
Thanks @MarcSaunier ,
The notes here is what I meant, sorry if that wasnât clear.
[!important]
Macroâs require the MacroPort to have both
- Node names to exist
InOut- Properties set
- Direction - Input
- Direction - Output
[!error]
In your initial video poost
and the terrain fileYou had missed setting the out node to output.
In Gaea 2 and 3, you can set this up semi-automatically in the Variables Tab for a quicker, error-free setup:
Hope that better clarifies.
Iâm able to export the macro this morning. As you said though, canât be used with this version of Gaea.
Thanks for your patience ! Itâs all good now.