Hello all
Modo users might find this useful :poly121:
It sorts out the grid size issues in relation to UDK and I have created a pie menu with F1 as the hot key.
This is the menu:
Modo (turns grid snapping off)
1024
512
256
64
8
4
1
I added the LXM files along with the cfg file so you can create your own menus.
You can edit the LXM files to make this work with Unity.
Meters Per Game Unit must be set to 0.01 (UDK equivalent) for this to work properly.
This works on 601 without issues and don't know if it will work on 701 or 501 and lower.
https://www.dropbox.com/l/fVaEFtePqxHd1LW21q2CQ9
Happy snapping
pete
Replies
I am not sure what you mean by a base 2 grid. Are you setting the coordinate rounding to fixed with a fixed increment of 2?
For a 1024x1024x1024 cube with the coordinate rounding set to Forced Fixed at a fixed increment of 102400 (translates in modo as 1024.0) you pull out a perfect cube with snapping at that grid size no matter how far you zoom in or out. Each segment of the grid is exactly 1024x1024 and forced to that size, the same goes for 512,256 and so on.
the macro looks like this:
#LXMacro#
tool.set snap.grid on
pref.select input/units set
pref.value opengl.gridSnap force
pref.value opengl.gridFixed 1024.0
Normal modo grid:
Forced fixed grid:
how do you use this ?
I copy all the files in my script folder, then assign the F1 shortcut to the command. and I'm sure I'm doing it wrong cuz nothing happened.
modo 701
Also add the macros to your user scripts folder to test them. Just select "run script" and pick one of the LXM files.
If that fails then you have to record the macros yourself and create your own pie menu. Give me a shout if you have any problems with this and we will sort it out :poly121:
Oh I got it now, the first time I assigned modo.lxm to F1 so nothing happened :poly117:
I successfully created the pie menu, assigned it to F1, checked my unit in modo and UDK it's all good in 701.
Thanks a lot sir.
Are you inputting the x y z size by hand ?
That modo grid you are using is off and you are relying on the zoom to draw out the 25600 box, a tedious workflow imo.
Below is UDK's start scene
As you can see the modo grid is off even if is set to game units. It would have been prudent if you had at least tried the snapping tool first and then you would see how useful it really is. Is it not more logical to be locked to a square number that you can choose from rather than depend on modos zoom function?
I set my snapping tool to 1024 and that's what I get even in perspective view, no messing around with zooms or having to manually type in the size.
Mystery solved :thumbup:
Now as best as I can tell this is your problem and solution:
Modo's grid by default does not increase/decrease by the numbers you want, 1,2,4,8,16 and so on. So you have created a menu that turns modo's fixed grid on at those numbers, which you manually change up/down when working.
If that is correct then you are missing something, because you do not need to use such a menu. If you set grid increments correctly (10, 25, 50) and units to game units, modo's grid will automatically change to 1/2/4/8/16/etc when zooming. I can guarantee this 100% works; it's what I've had modo set to for ages.
Here's where I think you made a mistake and got confused: In your screenshots and posts you for some reason mentioned that you entered 102400 as a fixed grid number. I can see from the screenshot you posted your fixed grid is set to 102400 not 1024. 102400 does not fit the binary pattern of 1/2/4/8/etc. Maybe the imported cube from udk gets size up x100, hence the extra two zeros on the end that is throwing you off (since anything that's x100 won't match the established pattern). So you have mistaken 409600 as a number in our binary pattern, when really it's just because the imported cube has been sized up x100. If you scale your 409600 cube down to 1%, it will match the grid.
As you can see in this image; I've drawn out a 64^2 square and a 128^2, all snapped to grid. I can zoom in or out as much as I want and it will match (although obviously when the grid gets too big to represent something it won't have an exact point, but it will still be matching)
I hope that has been a fair and accurate understanding of your problem/solution.
Just a question, would there be a way to add something to revert to Modo's original setting 'on the fly' without having to go in the preferences ?
Remember every preference setting change can be recorded to a macro.
You can then set somewhere in a form to that command. If your replace the argument with ? then you'll be able to change it from there.
So the command for your form would probably be something like
pref.value units.gameUnits ?
(I don't know what the actual command is off-hand).
If i want to revert to the Modo settings it doesn't seem to work, how do you record a macro again ?
Yes i looked at the command history, it looks like this @{C:/Users\****\Documents\Luxology\Content\Kits\Game Unit snapping\modo.LXM} is this what you are referring to ?
When i run the modo.LXM it doesn't seem to produce anything other than an error message ... how do you edit LXM files ?
Save the macro file with "Save to file" and put it on your desktop. Open it with the notepad if you want to add or remove commands. You can edit any LXM file just like a text file as long as it ends with .LXM.
Thanks for the reply repete, i will make a macro for this function since manual install seems to not be working. All the credit goes to you man
Are you still on 601 ?
This is confusing both path look the same but act differently .... It works now !!
I will edit the new form I made for 801 to UE4 (I use it for modular things) and fire it off to you, tomorrow probably.
It's easy as pie (pun intended)
PS working on a new modo to UE4 grid form as the power of 2 grid in UE4 could be a thing of the past in the future (no idea why but there it is).
Example: I like to work in meters so if you type 100cm Modo will write down 1m (took me a while to get it aaaaah!!)
Do you care to elaborate, isn't the power of 2 for texturing or may have i misunderstood something ?
On edit: do you mean while modeling/assembling ?