Ok, i updated the german translation on my site. http://poi.sturmwelt.de

MfG
sk2k

Hi Michael
17 h 35 Greenwich's Meridian :)
New "French Translation" is in your Lettrer's box :)

Just something about images :)
But damned and sorry I have not good reading this
< It currently isn't possible to edit the location or size of an image after you place it, this will be coming for the next beta release.

So my folowing remarks is not avaible :(
That work's very fine but...
It's not possible to put one image in a "Rectangle Object" for move it or resize it after the first input?
Seems this will be very practical :)

Yes, i agree with Pilou ! ;) (hei Pilou, you remeber me? On ZbrushCentral?)

For Michael, little WISH:

1) U can add some slider to move the image on x,y,z and one for scale it?

Tnx in advance for the reply! ;)

Mr Braun, a demo user like me? Of course I remember :)

Yes of course Pilou! ;)

@Mr Braun : That's a very new crazzy prog isn't it? :)
And like me you must more reading the First post :):):)
< It currently isn't possible to edit the location or size of an image after you place it, this will be coming for the next beta release.
http://moi3d.com/forum/index.php?webtag=MOI&msg=325.1

@Michael
You say Angle to Fill
and Step Angle
Ok
But they work singly!
There is not "Angle to Fill" + "Step Angle" and the same time :)
That can be cool too!

a tiny tiny "bug"
When you increase the UIcursor UI to the max of big size, then reduce to the smal size
width of the UI on the right stay "big" ! (not the caracteres)
You must press "Default" for a normal use :)

Rhino 4 has this feature called Picture Frame. But the images on the planar surfaces are visible only when the current shading mode is set to render textures. It is a really nice feature, though. I agree it would be nice in Moi too. But it would probably require that Moi is able to render textures in real-time. the side-effect is that Moi would have to support textures for all objects. I think nobody will complain if Moi can support textures!!! :)

jonah

**PS - the other nice thing about using a surface with displayed image is that it will support trimming/splitting operations. So it's especially helpful for visualizations such as architectural, using planes to represent background objects (or people) in a scene. trim away the parts of surface you don't need...

Hi Michael,

Nice work, thanks ! ;-)
I really like the align tool. Very useful !

Just add AI import/export and I'm ready to buy the commercial version ! ;-))

As Michael don't refind the keys of It letter's box :)
Here the "french translation" of the 18 Jan version
Just replace the old file "FrenchStrings" by this one in the folder /MoI beta Jan-18-2007/ui
Simple isn't it? :)

Hi Mr Braun

> For Michael, little WISH:
>
> 1) U can add some slider to move the image on x,y,z and one for scale it?

I'll be working on a way to edit the images for the next beta.

What I'm going to try to do is enable direct editing of the images when you are inside the image command - I mean that you will be able to click and drag on an image to move it, and there will be some kind of frame that will appear that will allow you to scale it.

That's the concept anyway.

This should also be a good trial run for an object frame that will eventually become a different way to scale and rotate regular objects as well.

- Michael

@Michael
> You say Angle to Fill
> and Step Angle
> Ok
> But they work singly!
> There is not "Angle to Fill" + "Step Angle" and the same time :)
> That can be cool too!

Hi Pilou, but I don't think it is possible for both to work at the same time! Unless you can explain how it would work...

These are two different ways of calculating the same value - that is what angle to rotate for each item in the array.

Using Angle to fill will take that full angle and then divide it by the number of items - 1 to calculate the rotation angle for each new item.

Using Step angle lets you input the rotation angle for a new item directly.

But they both result in calculating the same thing, that's why you can't have both at the same time. You can't have a new item that is rotated by two different rotations at the same time...


> a tiny tiny "bug"
> When you increase the UIcursor UI to the max of big size, then reduce to the smal size
> width of the UI on the right stay "big" ! (not the caracteres)
> You must press "Default" for a normal use :)

Yeah, I have seen this happen sometimes too. Something is not quite exactly right in the size calculations when going from big to small sometimes.

However, if you close the program and then re-open it, it should use the new size correctly. So that's an easy way to solve the problem.

I probably won't be focusing on fixing this bug very soon because you don't normally need to change the UI size on a very regular basis, it's something that you will more just pick a size you like and use it from there on out - it should work fine for that.

- Michael

Soon Italian Strings of MOI! ;)

P.S:
How i change the UI colors?

Tnx ! ;)

P.S2: Tnx Michael for your work! ;)

Jonah wrote:
> Rhino 4 has this feature called Picture Frame.

Yes I know, I added it to Rhino! :) It has been there since version 1.0, although 1.0 didn't have the rendered view shaded mode to go along with it.

You should be able to get a close equivalent to PictureFrame in MoI now by using images with the "Draw: With objects" style.


I do want to add texturing into MoI eventually, but I don't think that it is really a replacement for dedicated background images.

One problem with a rendered picture frame is that it is shaded by the light which changes the brightness of the image, even in a simple top-view-only tracing scenario.

For example make a small image and make it pure white - in Rhino go to the top view and set up a picture frame. If you look at the picture frame, you can see that it is not white, it has become darkened a bit due to lighting effects. In the 3D view you can see much more dramatic darkening due to lighting.

The other problem is that just a plain textured surface doesn't support either underlay or overlay type display layering modes, which I think are quite useful options for reference images.

So it is helpful to have a specialized tool for background images that can provide these types of specific features that are not important for normal textured objects.


> **PS - the other nice thing about using a surface with displayed image is
> that it will support trimming/splitting operations. So it's especially
> helpful for visualizations such as architectural, using planes to
> represent background objects (or people) in a scene. trim away the
> parts of surface you don't need...

True, this is one positive aspect of doing images through regular render texturing.

But as far as people or object stand-ins go, you can do that with MoI's images by using an alpha channel for the areas that you want to trim away. In fact you should be able to get better results by using alpha for this since you can have some partially translucent blended areas around borders instead of a severe on/off like a trim will produce. It should also be a lot easier task to set up the borders as alpha in a bitmap program since you will have things like the magic wand tool to help you, instead of having to trace the borders as geometry to trim with.

- Michael

Hi MrBraun,

> P.S:
> How i change the UI colors?

You can change the viewport background under Options / Background color.

But there isn't any easy way to change the color for the other UI elements - some of those are drawn using some little bitmap images, so you would have to edit the bitmap to change the colors.

- Michael

Tnx for the answer Michael! ;)

@Michael
Angle to Fill / Step to angle = Item count
So in this case Item count is automatic :)
No need to input it :) So in this case Item count must be disable at the start :)
I am agree I can take my poket calculator :)

Michael,

I like the new Align tool... it's like "Set Points" in Rhino,
only it's easier to use and it works with other objects as well.

Cool, now I don't need "Project to C Plane" anymore... :-)

Nice job!

Jesse

Pilou wrote:
> Angle to Fill / Step to angle = Item count
> So in this case Item count is automatic :)

I see.... But it seems like this creates an inter-dependence between those values that would be difficult to show in the UI.

For example if you entered both an angle to fill and also a step angle which then updated the item count, what would you expect to happen if you then went and edited the item count?

- Michael

Just don't permit to users to input a number in the Count item !
Only Step and Angle to fill :D
I agree it's not academic :)
maybe it's an too progressive idea ! ;)

It will be the same result than your but with an headhache so Forget it !

Pilou wrote:
> It will be the same result than your but with an headhache so Forget it !

So don't throw away your calculator yet!! ;)

- Michael