Sorry if this has already been discussed, I didnt see anything about it.

I can not snap to a solid, except 'On' and 'On Surface'. Everything else doesnt work. Yes, the 'object snap' is on (see picture for proof :-). So just to make sure I wasnt imagining things, copied the same solid (just a box) to V1 and everything was fine there. I also reinstalled V2, but that made no difference.

-Nick

No problem for me, all snaps are fine between solids or others in beta 2.0 august 4

Hi Nick, that's definitely strange, I have not heard anyone else report this problem so far.

Does snapping to curve objects like a line or circle work ok?

What about if you go to the view toolbox on the side pane and switch the checkbox for "Display hidden lines", does that make a difference? If it does then it probably means something is not behaving right on your particular video card for the hidden point determination for object snaps.

V1 did not try to determine if an object snap point was hidden, that may be why it behaves differently.

But also if you have "Display hidden lines" turned on, then v2 will not try to determine if points were hidden so if you let me know if that makes a difference that would probably help me.

- Michael

Aha! That was it, I unticked 'display hidden lines' a few days ago and thats when it happened (although i didnt realize that until you said so).

This happens on both on solids and curves (hadnt realized that either).

One notable thing is that it DOES give a snap point on the FIRST and sometimes second point you create a solid or curve with. I mean, if you drag out a 'corner to corner' rectangle, the only snaps it will give you are the FIRST point you snapped, and the second point, both as 'End'. If you draw an elipse by 'center' the only thing it will snap to is the FIRST quadrant... thats it (except for 'On', which it always gives). If you draw a box with 'corner to corner', you can snap to the start point, the end point, but not the height.

Hope that all helps. Let me know if you need more feedback.

-Nick

You mentioned video card. FYI: It is a NVIDIA GeForce 7300 LE. Thats OEM for this Dell E521, thats about 1 year old. PC is running Win XP sp2.

-Nick

Hi Nick - that definitely narrows it down!

It basically means that MoI is not getting the expected information back from the video card.

Could you please try a couple of things?

First - can you please update to the latest drivers for your card here:
http://www.nvidia.com/object/winxp_175.19_whql.html

It may be some glitch in your particular video driver version - over here I have a machine with a GeForce 7350 LE which does not have the problem but I have a recent driver installed.


Another thing - can you please go to your video card control panel thing and look at the anti-aliasing settings and see if you have anti-aliasing turned on in the driver? If you do, can you please switch that to the "application controlled" setting and see if that also fixes the problem?

Thanks,
- Michael

Aha again!

I tried the most undoable thing, which was the anti-aliasing option. See the attached screen shot.

When I had the problem, the setting was set to "Use my preference emphasizing:" and the slider was all the way over to 'Quality'.

Then I ticked "Let the 3d application decide", restarted MoI and the problem was gone.

I did this a few times and yes, it is definately a factor with the issue at hand.

I know that I set it to 'Quality' myself a few months or more ago. I cant remember what app it was changed for though... I dont care anyway.

I will update the driver when you reply back, but I'll leave it on there for right now in case you have any other questions. KWIM? :-)

And here i always ignore video card type threads on any forum because those are for fools with outdated systems. D'ohhhhh! :-P

-Nick

Hi Nick, that's great news!

Basically, what happens is there are a few times that Nvidia have had a bug in their drivers where they don't listen to MoI's request to disable anti-aliasing at certain times.

For the normal display anti-aliasing is not a problem, but MoI also uses the video card for some selection and visibility related calculations, and anti-aliasing in those particular calculations throws a monkey wrench in there.

You may find that if you update your video driver that you can then have the anti-aliasing setting and also MoI working properly at the same time. But it is not really necessary to do that since you have a solution.

Also even with your current driver version you can leave anti-aliasing turned on for everything, and then go to the "Manage 3D settings" entry on that NVidia control panel and there you can adjust the driver settings for individual programs and turn it off only for MoI there.

- Michael

Thanks for the help!