dene maxwell wrote:

I would like to put a fence around my local airport.

Intuitively I would start by building a 3-D model of a fence (say wire-mesh) of some nominal length (say 5-10m). Then place multiple instances of this fence around the airport. A few issues arise with this approach;

1) on even a short airport (2000m) it would take 200 instances to go down one side and over 400 instance to surround such an airport when using 10m sections. Surely this would place an unacceptable load on the graphics processes.

2) placing over 400 instances around an airport would be VERY time consuming (and VERY boring )

My thoughts on static objects (or even AI objects) is that as the distance from the airport grows so does the size of the object grow to become noticable eg placing vehicles on roads 9Nm from an airport is pointless, placing a crash tender on the airport is worthwhile. Little details like Control Towers, fences, wind socks, LLZ antennae etc that are on the airport would add alot, but at a greater distance things like tall buildings and radio towers are all that are needed.

My question: How would you (anyone with ideas) put a fence around an airport?

Dene

_________________________________________________________________

Hi there ... I did CYVR airport as an ac3d model .... it worked fairly well , why not do it that way ?


Hi
Being relatively new to modelling I have a few questions;
a) Was your fence wire-mesh and do you have a wire-mesh texture?
b) I was under the impression when using ac3d model is had predefined dimensions. Even you stretched the length it would distort the texture? c) did you create fences of different lengths to cater for the different lengths required around the airport?

Dene

_________________________________________________________________
Check out the latest video  @  http://xtra.co.nz/streaming


_______________________________________________
Flightgear-users mailing list
Flightgear-users@flightgear.org
http://mail.flightgear.org/mailman/listinfo/flightgear-users
2f585eeea02e2c79d7b1d8c4963bae2d

Reply via email to