wings3D on slow PC

#1

does wings run choppy on a slow PC?

PS:i dont know much about computers but i think our RAM is 128MB i dont know the Video Card too. :frowning: but im sure its pretty slow…

#2

When i first started on Wings a year back, i was on a Pentium 2 350 mhz, 192 MB SDRAM, 32 MB graphics card.

It used to be horrid, the minute i hit 2000 polygons, it lagged like muffins. So yes, it does run choppy. :stuck_out_tongue:

What i used to do for complex models is, cut the model up into small pieces. And when you need it as one complete mesh, just weld the pieces back.

Or, you can get a new computer. :stuck_out_tongue:

#3

too bad…
looks like i wont be using wings on this computer…:rolleyes: i can use the other though. :slight_smile:

#4

old P3 667 256mb sdram on win2k here.

A ‘bit’ choppy over 2000 polygons but still very useable,you gotta test it.

You can loopcut and hide some parts,that’ll help sometimes when the scene gets bigh but I rarely have to use that.

Note of interest:A ‘polygon lock/freeze’ or hide option/mode has been requested before and I’m sure that if it’s on the list and they find the right time,or the right way,they’ll implement it.

#5

i think they are actually semi trying to implement a way to hide part of the mesh

but dont quote me on this

#6

LOL good for you, you can reach 2000 polys. mine is choppy even if the scene is empty! :blush:hehe…

#7

A ‘polygon lock/freeze’ or hide option/mode
this would be really great!
improve/increase OpenGL and Video/Card capabitlities…

the faster interaction rate with the mesh manipulation
i’ve found in Wings3D! it is all i need! :thumbsup:

#8

A lot also depends on the graphics card/chipset too, since it’s heavy in the use of OpenGL. That’s what determines the starting speed (it’s not just the CPU.) On most computers running above 450 MHz, Wings is usually quite workable to start with. It’s when you’re pushing polys (doing multiple smooths and making complex geometry “poly-bombs”) that make having a strong computer necessary. If you need to model something more complex than what your computer can handle you’ll just have to chop and weld like the others have said. Or you could compose your model out of many less complex parts. (And hiding any piece you’re not working on or using for reference.)

#9

Note of interest:A ‘polygon lock/freeze’ or hide option/mode has been requested before and I’m sure that if it’s on the list and they find the right time,or the right way,they’ll implement it.

Would that be like “Freezing” in XSI? Does Wings store a construction history like XSI does?

#10

AFAIK it doens’t have a construction history.

I meant lock as in wings and freeze as in Max or Maya(I think),although these operations are restricted to whole bodies/elements/objects,like to select a bunch of polygons and Freeze/Lock them to prevent any transformations and/or to save on cpu time(if it would).

#11

Max has Freeze, and Maya’s equivalent is Template.
Does locking a model affect performance? Has anyone tested that?

#12

I doubt that locking will do anything except to do what it is intended, that being so as you do not affect the objects you have locked, when working with the rest of whatever it is you are working on… :smiley:

Hiding said objects will most def speed things up

I pretty much learned to model with Wings3d, on a celeron 266, and then a celeron 400, with but 192 megs sdram, and a 128 bit, 16 meg older vcard…

all was ok up to about few thousand poly’s, then uggg, sheessh things would slow down… then I realized that my models were usualy much too dense in mesh, and that I would be serving myself better to learn how to craft things much more boxy like…

now I have a much quicker amd 2200, and all of that is in the past… though I have to say that having to learn to make things more boxy was perhaps one of the most important aspects involved with the learning curve for boxmodeling, and thus I really am glad I had those poly limitations when I was learning… it really forced me to rethink my mesh building approach…

#13

Actually,it is faster to lock objects for me,sort of.

The way I work,I jump alot between sub’ed and not subd’ed so if the rest of the objects that I’m not working on are locked,they won’t be affected whenever I hit tab.

Like say I have two eyeballs sphere of 900 or something polygons each and a head model roughly under 400 polygons,locking the spheres will prevent boosting their count.

Yes it would rather have to be hidden in order to increase the performances the way we know softwares work,although Wings has been known to be quite unique in the ways it deals with problems.

#14

I run it on a K6/2 450, 128 Mb RAM, and a Geforce 2. i don’t notice any slow down unless I’m rendering(obviously). I’m building a new PC next week though, maybe I’ll see a difference.

#15

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.