Holger

Hi John,Richard and I are working on a patch for his Alaska Cinematic, which will resolve the current issues with Ultimate Terrain (a few raised lakes and flattened shorelines). In general though, the two products are fully compatible. For example, with the combination of UT and AC, Anchorage now has both photorealistic terrain and 3D night lights, as the screenshots below show.Cheers, Holger http://forums.avsim.net/user_files/116768.jpghttp://forums.avsim.net/user_files/116769.jpg

Hi Luis and Luis,Nice story of discovery ;-) When I first tried placing those objects I too was about to dismiss them as odd. My "Heureka" came when I used the F1 button to place the aircraft (in slew mode) on the ground facing the object. When one hits the ground there's a split second that one can see the part of an object that extends beneath the ground and so I noticed that I wasn't seeing the whole thing.Two other objects that are drilled deep into the ground are gen_pole01 and gen_stack01.Cheers, Holger

Hi David,first in line to say a huge thank-you for your team's efforts! I'm greatly enjoying the previous Citation package and are looking forward to installing the Cessna 402 package as well as any future releases!Thanks again and my kind regards to you and your team!Cheers, Holger

Hi Lars,the display mesh files with the same display resolution (LOD) can be prioritised via the scenery library. However, for some unknown reason the priority for mesh files in FS9 is reversed when compared to other types of scenery add-ons. Thus, the mesh file you want to have displayed needs to be positioned *lower* in the scenery library than the one you don't want to have displayed.In your case, you should install the Abacus/FSG mesh files into a separate add-on folder, add that to the scenery library, and keep it above the entry with the Hellas mesh in it. That should ensure that the Hellas mesh is displayed in its coverage area and the Abacus/FSG mesh in the "rest" of Europe.Cheers, Holger

Hi Matthew,only land class texture sets that include autogen buildings have an associated nightlight file set. That actually does include most of the agricultural textures so if your VTP2 poly is supposed to represent a field without night lignts then you'd have to make your own custom texture set to achieve that.There's a very neat land class table in MS EXCEL made by Arnaud Cl

Hi Paul,the tower view gets saved in each flight situation file. Thus, if you do adjustments to your AFCAD but load a previously saved flight the old tower view position will be loaded. You either have to set up a new flight situation or edit the TOWER section in your existing flight FLT file (which you can open in Wordpad).Cheers, Holger

Hi Luis,alas, no, I'm not doing airports ;-) Just "bulldozing" some places and adjusting the AFCAD files and surrounding landscape and then handing them over to more talented folks to do their magic. :-smile12 Cheers, Holger

Hi Luis,the multiple-excludes approach worked for me when I used the same set of parameters for each rectangle. Thus, you could try either using both excludeAllObjects = "TRUE" and excludeTriggerObjects = "TRUE"for each rectangle or, if that's undesirable, drop the AllObjects and be more specific with the other excludes instead (see below). The other possibility is that one may have to include all parameter calls, which is what I did. In my case, the parameter set was like this (again, identical for each rectangle): excludeAllObjects = "FALSE" excludeBeaconObjects = "FALSE" excludeEffectObjects = "FALSE" excludeGenericBuildingObjects = "TRUE" excludeLibraryObjects = "TRUE" excludeTaxiwaySignObjects = "TRUE" excludeTriggerObjects = "FALSE" excludeWindsockObjects = "TRUE"/>Good luck!Cheers, Holger

Howdy,perhaps it's my fault, or rather that of my Columbia River Gorge package: http://forums.avsim.net/dcboard.php?az=sho...topic_id=240404 Chers, Holger

Howdy,OK, extra points for Horst ;-)Thanks for correcting my mistake regarding the order of the coordinates (doesn't make any difference, it seems, but I was wrong nevertheless). More importantly, you're correct about the number of excludes per area: when I re-wrote my original set of exclude rectangles to all use the same parameter settings the windsocks disappeared as ordered. Thus, anyone with the need for more "surgical precision" can indeed combine multiple smaller rectangles in one XML file.Cheers, Holger

Howdy,Besten Dank, Horst, but the SDK states NW coordinate pair first, then SE coordinate pair.Full points go to Luis!!! I had put several excludes into the same XML, and only the first one (for the buildings) was read. Thus, I consolidated all of the smaller excludes into a single rectangle and selected the parameters as follows (didn't want to set excludeAllObjects = "TRUE" because I've heard that it would also remove autogen and/or effects: BTW, it IS possible to place the excludes for several different airfields into one XML file but it's probably better not to (to make it easier to remove specific excludes).Thanks again, everyone, for the help!Cheers, Holger

Hi Del,thanks for getting back to me on that!Unfortunately, those parameter settings ain't working either, at least not for me. Can't believe how stubborn those poles area - does anyone have a spare chainsaw? :-8 Cheers, Holger

Hi all,I'm having trouble with excluding windsocks from default airfields. All other default objects disappear when I code the XML exclusion rectangle but the windsocks remain ;-(I checked the corresponding default object file and my rectangle definitely excludes the windsock location, or so I think. Here's an example:1. The original code for two windsocks 2. My XML exclude codeLike I said, everything else works just fine. I also tried adding excludeAllObjects = "TRUE" but that didn't help either.Any ideas what I might be missing?Cheers, Holger

Howdy,and if you're just interested in Hawaii, there's a free 6MB high-res mesh available here: http://www.fs-traveler.com/products-f.shtmland the new shorelines made by Justin Tyme (FSGenesis) are available for free (Beta version) in this thread: http://portal.fsgenesis.net/index.php?name...waii+shorelinesLast but not least, Bill Melichar's airfield add-ons are wonderful!Cheers, Holger

Howdy,Horst, whether winter is over or coming depends on which hemisphere of the globe you're on ;-)The FinnIce project is a good example of how this works but it has a few drawbacks. Here's a couple of other threads that discuss this and alternatives:http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchhttp://forums.avsim.net/dcboard.php?az=sho..._id=17950&page=The process I'm using is similar to the one I describe for glaciers here: http://forums.avsim.net/dcboard.php?az=sho...id=26818&page=2Hope that helps.Cheers, Holger

Howdy,two mistakes I can see:1. you've got the values for Lat and Lon reversed (-77.16... should be Lon and the other value Lat)2. you need to drop the leading "-" in CellYdimensionDegTry those edits and see what happens.Good luck!Cheers, Holger

Hi Alfredo,please see this thread: http://forums.avsim.net/dcboard.php?az=sho...ing_type=searchCheers, Holger

Hi Lars,all of the mentioned mesh add-ons are based on the same source data - Shuttle Radar (SRTM) data of approx. 90-m resolution. It does make a difference how the mesh developer deals with the problematic areas in the source data (e.g., holes and spikes) but it seems from the HSP website that they have taken great care with their mesh and the integration of that particular mesh file with their shorelines and scenery. In other words, if you're really only interested in Greece then just keep the mesh you have; I doubt that Pietro's mesh would provide a great improvement, if any.Cheers, Holger

Howdy,easy to install: make a new folder, say "AK mesh by Ed Denney", inside your FS9Addon Scenery directory, with a "scenery" subfolder in it, then place all of Ed's bgl files into that subfolder, then add it to the FS9 scenery library via Add Area, then restart FS9. Since the mesh covers all of Alaska you can pick any airfield.If you don't like what you see then all you have to do is remove the scenery entry from the file library and delete the AK mesh folder.Cheers, Holger

Howdy,hey Tom, I was in electronics in the Navy too, except it was the German Navy (electronic intelligence, i.e., spying on Russians) and I enlisted about a decade later (left in 1989).40 years old now, moved to Canada (B.C.) ten years ago. Have an MSc in Geography/GIS and am working on a PhD (don't ask!) in Forest/Landscape Ecology.I currently spend about 50% on contract work for forest companies and the government doing research on "natural disturbances" (fire, insects, diseases) and 50% on commercial add-ons for FS. Used to fly gliders back in Germany but never got back into it here in Canada. Who knows, maybe one day I'll exchange the simulation for the real thing but that depends how many people buy my add-ons ;-) (actually, I make at least three times as much with my forestry contract work but the current political climate is not very open to "alternative" approaches to forest management).Pleasure to "meet" everyone!Cheers, Holger Sandmann

Hi there,that's actually not a bug in G2K4 but a problem with the FS9 texture engine, which places any polygon as LOD13 sections. For some reason (perhaps a rounding error in the code?) some of the lower mips don't fully cover the LOD13 Areas and the underlying land class texture shows through.Two options for minimizing this effect is to avoid crossing LOD13 boundaries (the G2K4 grid lines) as much as possible and to place a base land class that is similar in color and texture to that of the VTP2 poly.In "critical" areas (e.g., white glaciers on a dark-rock background) I use a work-around that involves setting the glacier poly as LWM water, "coloring" that water with the glacier texture via a local water class file, then surrounding the glacier with a VTP2 glacier poly on Layer 1 (i.e., only shows up on water), thus turning the water back into land. Pretty bizarre, huh? ;-)It works quite well but is not perfect. There are still faint lines visible if the user has water reflections turned on, and the polygon shows up as water in the map and GPS display. Still beats a grid of black lines, IMO.Cheers, Holger

Howdy,G2K4 indeed allows for using custom-named textures for VTP2 lines. It's described in the manual:"Ground2K4 uses also the Ownlines4.txt located in the Ground2K4Resource folder; this file is derived from the terraintexture.cfg file in FS2002; You can add your own line types at the end of this file, beginning the value at 4097.Please, respect the writing, see the example in the file. Note : Terrain.cfg and Owlines.txt are only read and stored into memory when starting Ground2K4."The only drawback is that the special features associated with VTP2 vectors, such as autogen or flattens, can only be defined in the terrain.cfg. Thus, your custom textures won't have these. The work-around, if desired, is to draw a default road with a width of '2' on a lower level and the custom road with the desired width on a higher level. That way you can add both flattens and autogen without the need for changing the terrain.cfg.Cheers, Holger

Hi Stew,I sent you the tutorial four days ago but just received notification from my ISP that it can't reach the address you posted above. Do you have any other email address I could use?Cheers, Holger

Howdy,here's a bit more information about how seasons are implemented in FS: http://forums.simflight.com/viewtopic.php?...=seasons+holgerCheers, Holger

Howdy,it's obviously not difficult to come up with rational arguments for keeping the files on the server, and I'd tend to agree with them.However, in most of these cases you're dealing with an individual who is already "frustrated". Thus, I'd consider the more important issue the potential consequences for the reputation of the file host if this individual starts an "emotional" campaign for "disrespecting" his/her wishes. In other words, it may be less work to remove the files and say "good riddance" than to spend lots of time on "damage control" posts trying to justify the decision to keep them.Cheers, Holger