polys disappearing

[Sil3]

Post the scene so that Lyle can take a look at it.

[Zoogie]

If could be that you have polys that have more than 4 sides. so when you cycle through and it gets to the subdivision9metanurb) mode, then it disappears cos it cant handle the ngons.
Go back into your modeler and check if you have any ngons.

It happened to me when first tried m:a . there happened to be one "bad" 5 sided poly hiding in the mesh. fixed it and no more disappearance.

[cousin it]

Only quads and trigons, I'm afraid. I also removed ev'thing that might cause grief (weightmaps, endomorphs etc. ...) No change. I really think it's more of a display problem, since different polys disappear when i close and restart Messiah and different display mode settings result in my mesh becoming completely invisible. For instance, sometimes "m" fixes all problems, and is one of the only modes to work properly, sometimes it makes my mesh vanish completely. But I'll try and post a sample scene later today anyway...

[cousin it]

Done some more testing. The problem appears OpenGL related. When I disable hardware acceleration on my graphics card and then start up messiah, the mesh displays fine.
Anybody got another workaround though? Or an OpenGL setting I haven't tried yet?
It's just that, hardware acceleration, that's what a graphics card is for...

[Geco]

which graphic card?


http://tinyurl.com/uiqz

[cousin it]

nvidia geforce4 ti4200 with agp8x and 128mb ram

[Geco]

afaik this card should work well with messiah.
try to use the default nvidia opengl setup and the latest drivers.
did you have this problem with other models too?


http://tinyurl.com/uiqz

[cousin it]

I've got the 5.2.1.6 NVidia driver - which was the lastest until yesterday, I think. I've tried every OpenGL setting I could think of; no luck.

I've had it with several 'fairly complex' models. (i.e.: more complex than a cube or a sphere)

[Qslugs]

Did you turn off all the windows crap, like mouse shadows other every other visual enhancement? Also, if you're in xp try running xp in classic mode.

[cousin it]

All the more fanciful XP-stuff has been disabled since the day it was installed. I like my machine to at least appear to be a working environment...

[Qslugs]

heh

[tangledpath]

Could be a physical hardware problem...maybe the card is toasted. I had one go out on me once; it exhibited similar behavior.

If you can, try out a different card.

good luck

[ThomasHelzle]

After having this problem too for quite some time and getting no usable feedback to my inquirys, I finally deinstalled the 52.16 Drivers today and have gone back to 42.30 which is recommended for my Geforce4800SE by Gainward:
Now the problem is gone!

I haven't tested the newest version 53.03 though...

Strange that a driver will show some polys and others not... :banghead:
I hate computers :-)

[cousin it]

YES! :beer: Thanks Thomas!

I reinstalled the old driver that originally came with the card, and most of my problems are history!

I say most, cause "m" mode still has some quirky behaviour. Anyone care to try this at home, see what he/she comes up with?
1. load a mesh in messiah, e.g. a cube;
2. tab the object;
3. switch it's display mode to "m";
4. replace the object, by another object, or even itself;
5. the object becomes invisible in "m" mode, until the fxs -scene is reloaded.

Can anybody confirm this? Or am I doing something wrong?

[bradenbickle]

Originally posted by Zoogie
If could be that you have polys that have more than 4 sides. so when you cycle through and it gets to the subdivision9metanurb) mode, then it disappears cos it cant handle the ngons.
Go back into your modeler and check if you have any ngons.

It happened to me when first tried m:a . there happened to be one "bad" 5 sided poly hiding in the mesh. fixed it and no more disappearance.

Does this kind of thing only happen with >4 sides or does it also happen with trigons and less?

[Miyazaki]

I have the same problems with the demo version of animate 4.0.
It worked fine with my old GF2 and old drivers, but my FX5900 with newest nVidia driver sometimes hides polys of the mesh. All pure quads.
It`s funny, some models show all Polys only when Meta Nurbs Level is set to highest(10), other show all polys when level is set to 2 or 3.
I played around with the driver settings, but only hardware acceleration set to off fixes the problem.
This is not an issue with other openGL dependent applications such as LightWave, Cinema4d, Maya or XSI. It just happens in Messiah and just in F, S and T Modes.
M Mode works fine.
Could it be that Messiah 4.0 does not support the newest driver correctly?

[chikega]

Yep, getting the same thing with my Alienware rig which has a GeForce FX5900 Ultra even with last year's original drivers. The wierd thing is that everything displays perfectly on my laptop which is running a GeForce FX Go5600! I've been using the Wild E. Coyote file found in the Projects folder as a test scene. The good thing is that it renders fine in m:s 1.5.:)

[Freebooter]

Originally posted by Miyazaki
I have the same problems with the demo version of animate 4.0.
It worked fine with my old GF2 and old drivers, but my FX5900 with newest nVidia driver sometimes hides polys of the mesh. All pure quads.
It`s funny, some models show all Polys only when Meta Nurbs Level is set to highest(10), other show all polys when level is set to 2 or 3.
I played around with the driver settings, but only hardware acceleration set to off fixes the problem.
This is not an issue with other openGL dependent applications such as LightWave, Cinema4d, Maya or XSI. It just happens in Messiah and just in F, S and T Modes.
M Mode works fine.
Could it be that Messiah 4.0 does not support the newest driver correctly?

I get that exact same behaviour using an FX5900 Ultra. M mode is also my best solution. I also found a set of Nvidia drivers labelled as 6112, which came from http://www.guru3d.com which seems to fix it, and also corrects an occasional bug with OpenGL textures not displaying.

Maybe that will work for others out there?

N

[chikega]

I rolled my 5900 Ultra drivers back to " 45.23" - and that has solved the problem of some polys not showing up.

Unfortunately, it still doesn't resolve my issue of the entire mesh disappearing when using the C4d plugin. :-(

[Freebooter]

This FX5900 thing is a trifle weird, ain't it?

I found that the 6112 driverset fixed the problems on the meshes I had been working with, but yesterday found that a mixed sub-patch/polygon model (vehicle) exhibited the same symptoms. Turning the sub-patch bits off in modeller and seperating the non-displaying surfaces from those around them (cut and paste back into place) solved the problems.

It seems to me that the problem is in some way related to the suface assignments and connections between surfaces. Try this: On a copy of a mesh that displays weirdly, try changing surface assignments, around, the missing polys (for me) tend to go, or move around depending on what seems to be surface topology and the area covered by the surface. Obviously surface assignments need to be where you want them to be, not where the GFX card wants them to go, so this is hardly a solution, but maybe a starter for trying to track the problem down.:shrug:

Chikega, glad to hear that the 45.23 set works. I'm sure I've got a copy of those somewhere. Sorry to hear about the C4d issue though. I take it there are still issues between messiah and C4d?

Later,

Nic

[ThomasHelzle]

I tried the latest 61.40 drivers with no success.

All drivers below 5x should work (4x.xx and below) - that is a long known solution to invisible polys and bones, but it is not a real option for newer cards and the new drivers have some very nice options I would really miss :-)

The only workaround for me is setting the surfaces to textured mode or wireframe - those modes don't show the problem here.

Let's hope that pmG is able to track the problem down!

Best regards,

Thomas Helzle

[chikega]

Originally posted by Freebooter
Chikega, glad to hear that the 45.23 set works. I'm sure I've got a copy of those somewhere. Sorry to hear about the C4d issue though. I take it there are still issues between messiah and C4d?

Seems that way. In m:s 1.5c, everything displays correctly until I save the C4d scene and open it back up. The mesh is "invisible" - but there is a bounding box both in C4d and messiah. When I go into Poly, Edge, or Vertex Selection mode in C4d I can see the wireframe of the object. The one clue that leads me to believe that this is not a Hardware issue is that once I delete the "messiah:dform" tags, the object displays properly. :hmm:

Gary
3ddmd

[Freebooter]

Interesting, Is that on all C4d scenes, or just now and then? And does the mesh render okay?

(I ask because I'm seriously considering ditching LW(8), and having used C4d in the past, I know it for a good option - of course I'm not going to worry too much about it until after M:S 2.0 is released).

I've noticed a vaguely similar behavoiur in Studio 1.5, when cloning or replacing a mesh, it will occasionally vanish, in all view modes, until I exit messiah, restart messiah and reload the scene.

Perhaps the two are related in some way?


Nic

[chikega]

I'm kinda riding that C4d/LW fence myself. I'll see how LW8.5 fairs against C4d9, should be interesting ... :D

I've created about 10 different simple scenes on both my laptop and desktop. So far it's consistent. When, I save the scene and reopen - Nada. I can unparent and reparent the object from the "messiah:dform" tag, and the geometry will pop in and out - it will display properly and then not. Unfortunately, it doesn't render either. I've brought the issue to pmG's attention. So, we'll see if the issue can be resolved before the 2.0 release.

[CGTalk Moderation]

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.