Hi lyes

> my be the problem is in the screen 22" (1920x1080)

It's possible those markers are too small for your screen.

There are some things you can do to adjust them though.

In moi.ini under the [Drawing Aids] section, there are some settings you can alter:

ObjectSnapMarkerOpacity=80
ObjectSnapMarkerDisplayRadius=100

The opacity is a value from 0 (totally transparent) to 255 (totally opaque) - if you increase this to have a higher opacity value the maker will become more substantial and darker on the screen which may be good for you.

Also the display radius is the radius in pixels around the mouse - markers that are within this radius of the mouse cursor will be displayed. You may want to increase that value if the current radius is too small on your screen.

Finally, the little X marker itself is an image named "OsnapMarker.png" which is in the \ui subfolder inside of MoI's main installation folder. It is a pretty small 7x7 image, if you replace this image with a larger sized one that should make those markers bigger too.

- Michael

Hi Micheal thanks for your time

Hi lyes, currently a simple solution for that is to hide the other objects that are interfering with your point picking.

If you only have that arc visible, it should then be easy to tell which center point will belong to it since there will be only one.

But there are probably a couple of different things I can do in the future to improve this situation - having the center point show up as a grip when it is selected as we were previously discussing is one thing that would probably help since it would give you a way to identify it, and maybe showing some kind of highlight on the curve that has a center osnap active on it would also help.

But again, I'm not sure exactly when I will be able to do those, for now just hide the other things and that should let you complete that task pretty easily in the current version.

- Michael

Hi Michael,

I can relate to lyes with center picking issues, especially when you have several arc enteties around each other not sharing the same center point it's a hit and miss situation.
It'll be nice to have something to zero in on the right acr center, maybe a mouse click key combination to pick the arc it self to snap to the center.
In regards to the object organisation stuff if you apply a style colour to an object/arc will the X marker inherit the same colour, this could help in identifing which center belongs to which arc.


Cheers

Hi Danny, yup I think it would definitely be a good area to tune up. I'm just not quite sure when I will be able to make that happen.

It may be a couple of months before I'll be able to focus on brand new features, right now I'm pretty much just trying to wrap up v2 and adding new features tends to be pretty much the opposite of "wrapping things up".

re: Using style for the marker - that is an interesting idea, but the marker is pretty small and faint, I'm not sure that it will be that distinct to use color for it, plus that would be of no help in the situation where you have not assigned any styles. Possibly some highlight around the arc that has its center targeted would have a more universal application.

For now there is a sure-fire way to solve the problem though, which is to hide other entities so that they are not cluttering things up.

- Michael

Michael, I didn't expect you to have a look at this right away, we know you have your priorities and it's good that you set yourself deadlines by setting a time limit on each beta.
Could you imagine the forum posts if the beta deadline was up and you didn't have the next one out yet :D

No probs, keep up the good work, it's well appreciated.

Cheers

There is another "One Man" app genius who has had 75 Beta updates (in 4 versions incl mac) since last September.

And, still, just as frustrating as waiting for Michaels beta update!

The customer is never satisfied!

Brian
(Will the Easter egg be under the cabbage in my garden on Monday?)

Hi Danny, I just like to mention if it may take me a while to get to something.

Otherwise what tends to happen is if I just say "I want to do that feature", people kind of append "for the next release" at the end of that automatically.

Then when the next release comes out they're sort of like "hey I thought this feature was going to be in this next release", and I'm like "well, I said I wanted to add it, but I didn't say it would happen right away", and they're like "Hmm, that's not what I remember...", and then I'm like "well, here I went back and dug up the discussion - here is the post where I said that I wanted to do it, notice it does not say when exactly", and they're like "oh ok", and then I'm like "hmm, maybe I better mention this more up front so that people won't assume that it will happen immediately"... :)

Mostly that's just to try and reduce extra discussion by providing more info up front, but in this case I guess it made for more discussion instead. I can't win! ;) ;)

- Michael

Hi Michael....

Why MoI V2 Beta take more than 5 minutes to boolean difference for the phone button ?
Is there any plan to improve this ?

Please find attached 3dm file.

My laptop configuration :

Hi Anis,

> Why MoI V2 Beta take more than 5 minutes to boolean
> difference for the phone button ?

Are you possibly running other CPU-intensive tasks on your machine at the same time?

I can't seem to repeat your problem over here - on my 5-year old system with a single 2.4GHz CPU, it takes 27 seconds to finish doing a Boolean Difference of all the buttons from the main phone body, using the Jan-19 v2 beta with the file you posted.

This system is pretty old now, and it was not even a high end machine at the time.

You may want to take a look at your system and make sure there isn't any bad software that may be running in the background taking up a lot of CPU time.

Another possibility is that your laptop may be running in a special "conserve power mode" where it runs at a slower CPU speed in order to prolong your battery life. You may want to plug in your laptop to a power source to possibly help avoid this.

- Michael

Hello Michael....

So the problem is not the software but my laptop yeah....
OK I will check what make it happen....

Thanks !!!

Hi Anis, maybe someone else will be able to test it on their machine and see if it also takes them such a long time.

But it seems strange that my old system finishes it 10 times faster than yours...

The booleans are a very CPU intensive calculation, so if you have other programs running in the background also taking a lot of CPU time, that could slow them down quite a bit. That's the main thing I would look for at first anyway.

- Michael

30 sec on a IBM T23 clunker, P3 1.13GHz, 512MB ram, 16MB S3 graphics.

---------

Hi Danny, thanks for testing it. That's somewhat amazing that MoI actually runs on that machine at all, that must be something around 8 years old or so?

The S3 graphics makes me wince a bit, but I'm glad that it works! :)

- Michael

Zbrush has this same capability! :) Working on old computer!

Hi Michael,
> That's somewhat amazing that MoI actually runs on that machine at all, that must be something around 8 years old or so?

Yeah, it's our general home hack laptop that lays around the house on standby for when someone what's to jump on the net quickly, I loaded MoI to see how it would run and for when I have a look at models that people post on the forum as I'm lying on the couch having a browse, it works great for that sort of stuff :)

> The S3 graphics makes me wince a bit, but I'm glad that it works! :)
It's ok for simple things, but yeah, when you load heavier models, surfaces tend to break up and manipulation starts to get jittery, but still works.

Cheers

Hi anis i have tryed your model took 16s

AMD ATHLON X2 3800
2GB RAM

I tried it again after restart my laptop and took 12 - 18 sec as well...

Thanks Guys...