Remen, nunca me canso de decirlo: pronto estará su rostro en algún portaretratos de mi casa (que difícil será explicarle a mi mujer e hijos el por qué
)
"Más mejor que no", como decimos al otro lado de los Andes. Medio problemita que yo tendría dando explicaciones a mi mujer...
Voy a mirar tranquilo tu línea y estructura de trabajo y ver si puedo volver a colaborar con los escenarios, sobretodo en le NorEste argentino que está muy pobre.
Como dicen los italianos (y tú debes saberlo muy bien, ya que llegaron tantos por esos lados): "qui va piano, va lontano". Comencé en Victoria (donde nací, en la Araucanía), seguí un poco hacia el sur y luego hacia el norte (Santiago).
Voy a completar algunos aeropuertos para FS Economy en la Patagonia, completo algo en Argentina (el próximo es SANE, donde estoy construyendo FBO's con passenger terminal, repair shop y fuel stations), y finalmente sigo hacia el norte y el este, para finalmente entrar al Uruguay.
Bueno, en una entrevista que dí hace algunos días atrás hice un punteo del proceso que utilizo (está en inglés y espero que no sea problema para ti):
The process of making a new scenery airport has these steps:
I choose a real active airport. It doesn’t matter if it is “large”, “small” or an “airstrip”, or if it has one or more runways, or it has many or none buildings.
I look for so much possible information about the real airport, in the official airport databases, photos, I use the maps of Google Earth and Bing, and I collect the information from the national aeronautic authority. There are always interesting facts in the history of the area of the scenery. I put this information with URL’s. I make the first document for the scenery, the “ReadMe.txt” with the most important information. This document will be the basis for making the scenery. My idea is: I am not so young anymore. This information can be used in the future by other people to continue this work. I know the most “developers” and “designers” do not do that. Maybe because they want to “protect” their work… My work can be used and continued by everyone, it’s free and always available.
I make the airport using World Editor (WED). I make the runway(s), apron(s) and the taxiways using the maps of Google Earth and Bing, and according to the data from the airports databases. I add the radio frequencies for the ATC, the windsock(s), the airport boundary, the airport beacon and the tower viewpoint.
I check if anyone has built this airport for FS9 or FSX. If so, I convert the old scenery and take a look at the buildings and objects used there. If there are nice buildings and/or objects like in the photos of the real airport I’ve found, I contact the author and I ask his/her authorisation to use those buildings and/or objects. You see, I do not make 3D buildings or objects, I just want to make an operational airport for X-Plane.
I look for hangars, towers, fuel stations, gates and other buildings and objects in the libraries of X-Plane, to use them if needed. Otherwise, I look at the libraries of OpenSceneryX or I search in my own collection of stand alone objects. Anyway, I always try to make a scenery without elements extern to X-Plane. I think the best scenery is one that ONLY needs the standard X-Plane, without other libraries, plugins or objects.
I add ATC flows for each runway (wind, time and runway use), and I make the ATC taxi routes needed for departures and arrivals. I define the parking places (gates, aprons, etc.) for the different types aircrafts. This information is always available, mostly from the national aeronautic authority, and I put it as URL’s in my “ReadMe.txt”.
I test the working of the airport flows and the ATC taxi routes, until everything is working “como Dios manda” (like it has to).
Finally, I add the taxi signs, the lines and lights, the navaids (ILS, VOR, NDB, etc.), and… very often… some trees (I love some green/grass in my sceneries).
Saludos,
