Background image error?

[liran_bar]

LOL
give it another shot....



Liran Bar, Israel

[Erez]

LOL........
Well I'll give you one small clue...... It's not Israeli made or Israeli air force airplane (can you believe it???)
By the way Liran, I saw him today on TV.....
Well sooner or later Liran will have to tell the world what is he up to......

[liran_bar]

Shit! that weird UFO is getting famous!

[Erez]

Cough*UFO......cough cough* space....... cough*.....

[liran_bar]

:-X :-X

[Felix/FFDS]

Candidates:

Independence Day,....

Close Encounters .....

The Day the Earth Stood Still....

:-X :-X

[liran_bar]

check your PM box! (but keep the info to yourself!)




Liran Bar, Israel

[Erez]

Candidates:

Independence Day,....

Close Encounters .....  

The Day the Earth Stood Still....

And the Oscar goes to.......

[X_eidos2]

Back to liran_bar's original question- how to get rid of the message prompt.

If you're using the background image with lock/zoom and pan the only way to avoid this prompt is to never zoom in for a close-up of the mesh. Even though your original image is only 70k - the software is trying to maintain the aspect ratio of the image to the objects in the scene. So if you zoom in on a section and the view is now 300 percent bigger than the original view, the software trys to blow up the background image 3 times. That's part of the reason why it says it needs 300 MB of memory to create the new background image. There's also the problem of the image shifting around when you zoom in and out a few times. These are the two reasons why I recommend to other modellers to make textures using their background images and map the material onto boxes or planes, and then position the boxes beind the mesh as needed.

[liran_bar]

Alright.... thanx man... I was afraid that will be the answer....
Thanks anyway


Liran Bar, Israel

[Felix/FFDS]

I've noticed that in gmax  (and other modelling programs) mapping theimages to reference boxes/planes is more or less the "standard".  

As to complex curved wings, the best example I can give you would be modelling an F4U Corsair's inverted gull wing.

I would either start out by modelling the wing "flat" against a top view background, then "pulling down" the cross-section/points at the point where the anhedral inner goes to dihedral... OR, model the inner and outer sections separate from each other.

There is no "right" way to model something.  

Alright.... thanx man... I was afraid that will be the answer....
Thanks anyway


Liran Bar, Israel