Author Topic: UE4 Export Macro (Update: Folder and Macro Generator)  (Read 5998 times)

0 Members and 1 Guest are viewing this topic.

SaviorNT

  • Community Member
  • **
  • Posts: 6
    • View Profile
UE4 Export Macro (Update: Folder and Macro Generator)
« on: May 10, 2015, 09:46:48 PM »
Update:

Since WM is giving me grief with creating 3+ "worlds" at a time, I took a bit of time off from design, and got back into VB. Created a simplistic program that will enable the user to specify the project name / main folder, and it will create sub-folders, as well as create a "master macro" that can be used to render everything out. This has saved me a crap ton of time, so I hope it's useful to you guys!

You can get it here: http://tinyurl.com/pbvfqjv

Screenshots:






So, that was the example, here is a quick screenshot of what I'm working on.. the first 25/100:





This probably does too much tbh, but it has a bunch of different outputs. Here are the screenshots for the macro:









WFab

  • World Machine Guru
  • ****
  • Posts: 359
    • View Profile
    • Blog
Re: UE4 Export Macro
« Reply #1 on: May 13, 2015, 12:22:49 PM »
Savior indeed! Thanks for this David!

SaviorNT

  • Community Member
  • **
  • Posts: 6
    • View Profile
Re: UE4 Export Macro
« Reply #2 on: May 13, 2015, 06:54:47 PM »
You're welcome. I understand its nothing overly complicated, but when you need to generate 100+ terrains and save them out.. lol

CB

  • Community Member
  • **
  • Posts: 3
    • View Profile
Re: UE4 Export Macro (Update: Folder and Macro Generator)
« Reply #3 on: July 03, 2015, 11:38:43 AM »
Do I need both files, the .dev and the .exe?

SaviorNT

  • Community Member
  • **
  • Posts: 6
    • View Profile
Re: UE4 Export Macro (Update: Folder and Macro Generator)
« Reply #4 on: July 09, 2015, 08:30:43 AM »
No. The automation + folder generator is just a utility program I wrote. The .dev is a macro for world machine that includes the nodes displayed. In fact, I would suggest you don't download the .exe and run it (even though I made it). You never know what it may contain as far as being malicious. As I don't want to open-source the code, but I don't want to charge for the program, I'm in a pickle with this :)  Of course, you could always run it in a VM, and do a before/after comparison to see changes to the different VM's.

Never run executables from someone you can't hurt, err.. I mean, from someone you don't know IRL is my motto :D

(edit: I come from a cyber security minded background, hence the warning. The code isn't malicious, however, you don't know me and I do not know you, so there can't be 100% trust)