Layout and other issues that drive me MAD!

#9

i too come from max to modo, my issues are similar.

when i save the file with a backdrop and load it up later it doesnt restore the backdrop. i have to load the images and set them in place all over again each time. this is a big time waster.

another thing i would like to see is modo recall the layout and viewport exactly as it was when i saved a model.

i get crashes just adjusting backdrops. its annoying. cause i have to set up the backdrop images.

sometimes when i start modo the backdrop images from the last session are still there, even tho the model is not there. this does not make any sense. oh the config file is probably the wierdest thing in modo y not just have it save and load in tandem with the model.

the crashes are unpredictable which is wierd cause i would bevel like a hundred edges and do some major poly hauling and modo will be fine, then i select a single poly and modo crashes. wierd shit like that. luckily modo loads quick and i go right back to where i left off.

save recovery feature like in max.
drag and drop script buttons like in max.

shell modifier like in max. cant describe this but its been called solidify also. sort of like an extrude but different.

i think the first version was more stable than 1.00, but then again i only started serious modelling with 1.02. and i like the bridge to much to go back.

otherwise i think modo is a great piece of software.

#10

I agree it would be nice to have that imbeded in the model and I think that I understant why it’s not, But you can just save the viewport. The next time you load your object to work on it, reload the layout and all the background images will be there.

#11

I dont come from Max, but went to max for some years after LW , and now on Modo, so I guess its much easier for me to adjust. :wink:

The closest thing in modo for recovery is the Auto save option, which you can turn on in the preferences. I also crank up the intervals to 12 just in case.

I havent messed around with changing the GUI, so I havent experienced the crashing.

Heres a link for folks who would like more info on solidfy.

original plug/ developer …tool is bundled in max currently called SHELL MODIFIER

http://www.gravitonic.com/software/3dsmax/downloads.php

description sorta:

Solidify is a MODIFIER [[i] drop down window pane where  plugins and other tools are listed, closet thing in modo is the Tool Pipe[/i] with command history] that takes your surfaces and makes them solid. An easier way to describe it would be to say that it does extrusion along vertex normals. No more wrestling with extrusion or double sided materials, Solidify makes it a snap to give your surfaces thickness, with as many segments as you need.

Solidify is a modifier plugin that takes your surfaces and makes them solid, making it a snap to give your surfaces thickness, with as many segments as you need.

Closest thing in Modo is the Poda Thicken Macro at:

www.Vertexmonkey.com

But, I think solidify can make edges hard before a cut, or after so if you remove or unconnect the Surrounding geometry the smoothed thickened mesh wont pull away from the vertices it was joined too.

#12

To bradpeebler: I hope you got my mail a few days ago…?
Anyway, I made a short video where I describe some of the major issues I’m having with modo. It’s not that modo is bad, it’s rather that I’m so much used to max and I’m finding it really hard to get used to modo… I’ll send you the link to the video as soon as I upload it on my ftp.

#13

i have no problems with backdrops…

#14

Then pretty please, with sugar on top, could you share your experience, or your settings or whatever to MAKE the damn backdrops to first SAVE with the file and secondly TO STAY IN THEIR VIEWPORTS as you set them up? :bounce:

#15

BG images do not save with your model. You have to save a custom viewport group. Set your images up the way you want them in all three orthogonal windows. Click on the widget in the upper right corner of any of the viewports. Go down the menu to the section Viewport controls. Select “save viewport group as…” Then save it as whatever. Now hit alt-F12 this will save your config. Now even if you crash it will be there next time you open modo. I believe that there is a small bug (bug or feature, you make the call) that will clear the images when you load a new object, and since there is no connection between the BG and your object this means every time. But once your object is in, just select that viewport set and woot, there it is. Also keep in mind the way that the view port settings are a sub-part of the layout. So if you change to a custom layout it will change your viewport settings to what was used last with that layout, so you may have to then change to your saved viewport settings again.

#16

I’m still having issues with Backdrops randomly loading at startup. I recently switdhed to UV edit mode and had a backdrop I had used months ago suddenly apear in the UV view. It’s not nearly as bad as the problem was before 1.02.

#17

And you’re trying to tell me, that this means NO PROBLEMS WITH BACKDROPS :scream: Man, this procedure SORTA works, SORTA doesn’t! It’s a havoc! I start to love viewports in max, even thou you can’t detach them! :argh:

I get a feeling that for every single project I’ll be working on I need a unique MODO!? Because, saving my UI!!!, because I need backdrops in the background is… STUPID!

Well, since I’m a max user and don’t know any other packages (well, not enough…), this way may be absolutely fine to the LW or MAYA or other packages users, but for maxers, this is faaaaar too “abstract”… :shrug:

Any other maxers to second me or at least share their xp with modo?

Btw: thanks drkollossus, at least now I know what to do to keep my backdrops there! :thumbsup:

#18

go to material>material editor, then drag and drop or load your images. close that, then, goto your front viewport, and goto backdrop, and choose the front image.

#19

heh loocus, this is a very poor design problem on modos part i have to agree. maya and lightwave save the image with the file. modo is the only one i know that does it this way. it sucks for sure. but its not too bad since you wont be needing to do this too much since it takes awhile to finish a project anyway hehe.

#20

Well… finishing a modeling session isn’t a matter of hours :smiley: If for yous, then I have to work even harder on my skills :cry: :thumbsup:

#21

I would guess that with everybody and their brother complaining about how Modo handles backdrops that they will change it in a future version.

Here’s my workaround. Texture map a plane with your templete - make it semi-transparent if you want. Then either lock it or put it in a background layer and adjust your viewport to show background layers in shaded mode.

It will save with your scene (obviously) and won’t add a million saved layouts. It will just take a second to setup. You could even have a macro setup to load the objects for you- just push a button for the macro after launching modo and change your images.

-Greg

#22

To leuey: Yeah, I’d hoped that this would have been fixed in modo 1.02 since it’s a pretty damn thing… but… Well, we, maxers, are used to this kinda behavior, aren’t we :wink: (damn not listening discreet!! :rolleyes: )

And the workaround you’re suggesting I use EVERY time in max, since it’s a bit more versatile solution than having the refs on the background. But in modo, I couldn’t get the bitmaps to show on my planes!! Damn! And if backdrops worked the way everybody expects, it’d be a holy-grail to setting up refs!

Well, I guess I’ll have to dig a bit deeper to modo to get use to it… So far, I’m totally unable to model anything decent in it! It’s a bit frustrating and one can get easily tired of re-inventing and re-learning things from scratch, since one has a very decent experience with 3d behind already… :cry:

#23

guess youll have to work in other progs besides modo…untill/if they fix this and other problems…

#24

To imsof: Well, the thing is that I don’t need modo at the moment at all. As I said, I’m a max user, so I can model/texture/animate/render in max, taht’s all allright… But I wanted to learn modo to have a bit higher chance of getting a job in the US, since they use a lot of MAYA and LW… I dislike maya’s interface and I love modo’s, so therefor I wanted to learn it, since I’m mainly a modeler.

Ok, another problem guys:

Ok, so I assign a material to my model. On the picture you can see that I have the reference planes in the background layer and the model itself in the active layer.

NOW:

As soon as I wanna do something (ANYTHING) with the model, it changes the freaking color so it’s impossible for me to read it!!! :banghead: DAMN IT! :argh:

This is modo ver: 102-10910

This bug happens only when I use a bg layer!

#25

did you try giving it another texture/material?

#26

hey check this out for saving backdrops…

what you gotta do is…

  1. load your backdrops in to a layout…

then…

  1. save the layout (prefereably with a new name so you dont save over the other layout.)

  2. so when you wanna use those backdrops just load the layout with the backdrops you want! but yo have to load the object file first .

what ya think…
works like a charm for me.

"You people at modo don’t you think this takes care of the problem… fix it so we can save the images with the file…sheesh, do we have to do everything for you modo? "

#27

yes this is wierd for max users, and most of all seems like just a time waster. i used to complain about max, but using modo has made me appreciate how good max is in some areas.

if modo is an advanced modeller, to my opinion lw must be a piece of crap.

#28

i hate the way modo sets up viewports layout etc.

in lightwave thats not a feature, its something u dont think of. 4 ports, 2 ports, fullscreen whatever. “d” panel know what i mean? i wish i had that exact panel in modo. then i could put my power on the track. some rubber on the tarmac…

in modo i have to read a manual in order to know how to split layouts fast etc.

i want quad view… for an “artist driven” app, modo seems terribly dificult for me.

i only use lightwave since lightrave (2.0),after sculpt and imagine, and did all the versions to 8 so i dunno. maybe its me.

its a shame such a powerful app with generous powerful engine and i cant even turn the ignition on. know what i mean? turns me off and reminds me i aint its master. i cant even set it. i know its probably me, since all the testers here model at lightspeed.

i did cg arch mostly overtime. the crew at luxology are great and i wish them a bright future. i just guess modo aint my thing. at least as is.