Modo Crash (mirroring )

#21

My apologies to the overly sensitive ones out there. There are many ways of saying the same thing I guess, and wasting time picking the “correct” words so as not to offend software companies has never been my strong point. Etiquette and “being polite” is for drones and robots.

The fact is I have seen MANY posts on these boards describing problems experienced trying to run Modo. They seem to be crippling bugs which would make using Modo in a professional pipeline a nightmare. Granted, not everyone seems to be experiencing the same bugs. So I guess it all depends on your individual hardware setup (gfx cards, drivers, etc), but please don’t tell me that Luxology were not aware of these problems BEFORE they actually decided to dump a product unfit for sale onto the community. I just don’t believe that.

A lot of people are still waiting for the demo version of Modo to appear, me included. At least by trying a demo first I could thoroughly test the software on my environment to see whether it is a usable product or not. Why is there no demo of a $700 dollar product? I suggest the reason there is no demo is because Luxology know all too well that after trying a demo full of bugs, most people would not be tempted to part with $700. I mean come on, even Silo offers a 17 day demo and that only costs $100! But then I guess Silo is actually a stable and usable program so they have nothing to fear of demos.

If Luxology wanted to test their software out on a large population of users than they should have setup a free v0.xx public BETA project BEFORE releasing it for sale. Instead it seems they have gone for a v1.0 BETA scam costing us $700. That’s wrong. In France we have laws against things like this.

#22

Here is a reproducable bug sequence for you:

(1) Set Modo for a fully orthagonal quad view mode.
(2) Shutdown
(3) Restart the app
(4) As we all desire, Modo remembers our prior config, and boots into orthagonal quad view.
(5) Note that the grids are slightly out of alignment on start up.
(6) Do not create any geometry, load or execute any commands before doing step 7
(7) Go to the top left quadrant of the work area, use the “move” tool to align the grids
(8) Watch the MS Error report screen pop up and request permission to transmit error info to Microsoft.
(9) Say yes or no
(10) Watch Modo crash like a ton of bricks.

In my single night with Modo, I also encountered the bevel and mirror crashes.

I started with Lightwave 7.5 before moving to 3ds Max because I didn’t like the radical interface of Lightwave. I like the interface on Modo. I can tell you guys are working on a high quality architecture. You have a lot of nice ideas, so I don’t want to seem overly-negative. However, I will wait for 1.1 before I slap some cash down on the table.

One other thing: I think you would be better served with Python as your scripting language rather than Perl. Python is now the lingua franca of the 3d and 2d industry. It’s no use fighting it.

#23

Please don’t feed the trolls! :banghead: There is a small group of LightWave users who seem to have taken it as a personal insult that some of the LightWave programmers decided to for their own company. I’m not saying this guy is one of them, but it’s possible. It’s also possible that he’s just some stupid kid who thinks this kind of thing is funny. My advice is just to ignore him or tell him to go away. It’s obvious he hasn’t read many of the posts here or he would see that most people are very happy with modo.

#24

I am not happy at all with modo at the moment…I hope that the next upgrade will change that.

#25

never been crashed in mirroring. But it crushes in undoing and renaming (layers, maps etc…) in my Modo. :frowning:

#26

For anything like this that you’re having trouble with don’t hesistate to send an e-mail to cs@luxology.com and we’ll figure out why you’re having issues… We need to get information on the machines that people are using and the kinds of things that they’re running into. It’s really impossible for us to have every configuration possible to test against internally. So the more feedback we get the better each release will be!

#27

Well i dont agree with the choices of words Chav have used. I do agree with his views somewhat. However, I think for a v 1.0 release it isnt bad. As far as a software that isnt buggy at v1.0, I never crush Mirai even once when modeling with it(it might have some bugs nevertheless). Like i said before in the past, if Luxology implement tools base on what their user base wants(not just their Maya/LW beta tester,because the world doesnt revolve around just LW/Maya) they should do fine in the future as a software company.

I like Luxology Modo not because of its somewhat buggy 1.0 release, but rather the potentail it hold for future release :D.

BTW i followed all the steps davidaleon mention, still no crashes. I never had a crash problem with mirroring(scale -X?), only losing symmerty when using modeling tools with it(which kills my workflow), than i have to cut,mirror,merge vertexs,.blah,blah,etc.

For the most part, people who have used Modo long enough know it doesnt crash often. So its production ready.

#28

Modo is a 1.0 release, so it has some bugs … but no constat crashes here. I use it all day in production and i have not serious problems with it … MODO is probably the most stable 1.0 version application i have used. Perhaps we can remember XSI 1.0 or LW[6], for example. The most important issue in MODO is his bright workflow and architecture, who is the base for a incredible new 3D app.

#29

here is the latest fix for modo…got to this link and download the latest driver from nvidia
http://www.nvidia.com/object/winxp_2k_66.93
mine used to crash, now it doesn’t…goodluck to all…

#30

This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.