Jump to content


Inactive Members
  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

109 Excellent

About meshman

  • Rank
    100% all natural

Profile Information

  • Gender
  • Location
    In a cave!

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

About Me

  • About Me
    Naturally grumpy, but prone to fits on assisting people every now and then.

Recent Profile Visitors

4,302 profile views
  1. I'll recreate my departure from Nugg's tomorrow, bumping up the veggies above NORMAL. Right after I did the patch to 2.1 I started P3D and moved autogen full right and flew around The Big Island of Hawai'i. Found I had a very nice ... stutter... every... second ... so I... turned the sliders back and it's smooth as can be for me. During my four hour trip today P3D was just flying forward from the cockpit. GPS wasn't on, I didn't cycle outside views, nothing. Just let it cruise at 4K' and kept track of what FSUIPC was telling me was still left in the system. While I have a texture replacement package, it's not the one that keeps getting mentioned and does not change core files. With the issue for GPS and possibly some XML incompatibility, I can't help but wonder if any XML parsing issue is having an effect on the autogen system. Because what are those darling little sim-prop binary (.SPB) files? Compiled XML code...
  2. The textures? Or the other changes made to the core files by the add on? Earlier today, Jeroen mentioned OOM and default P3D, so I fired up P3D and went to everyone's favorite airport, Nugg'S!!! It's first on the list, sits in north Texas and allows for a flight along a somewhat flat terrain. Took the default Carenado Bonanza A36, pointed it north, set the AP for 4,000' and let P3D run. I started at 1325 and at 1730 I shut down P3D, as the fuel was below 30% and dinner was waiting. Four hours and no OOM. Setting were my usual, kinda high except for AG bldg/vege at NORMAL. Once the VAS settled in at 1,480,800 it started to drip away, eventually sitting at 1,186,200 when I shut down after 4 hours. And while P3D was running I browsed the LM forums and there's a thread about someone with pretty much the same system specs who was getting an OOM after 30 mins with the A36. Only difference? He has a global texture replacement add on that changes some core files in P3D. So who's going to run the test, where they see if they can replicate their OOM by swapping back the default core files that are replaced with the texture replacement add on? Things might look a little different, but if it pinpoints a cause for OOMs they would be deemed a hero for all ages! Because when you see all the postings and so, so many have a commonality to them, it might mean it's time to take a real close look at what's being replaced and to not accept hobbyist assurances that nothing could possibly go wrong by adding some package into a simulator.
  3. Seeing as the poster of that comment has been shown the door, me thinks we don't have to worry about his judgement anymore! B)
  4. So people should disable default files to fix one airport? Do you know what those files do to the area? Disabling all the bridges (BRX) is going to fix an add on airport's elevation? Or disabling all the objects (OBX) in the area is going to fix the elevation? There are five airports in the APX file, so disabling all five is going to fix an elevation problem for one airport? None of the above would fix the problem (IMO) for the add on airport elevation issue. Trying to use default parameters to find a solution, without knowing (not thinking) what the add on does is a bad recipe for a pleasant flight!
  5. Aces used data from Jeppesen for airports, as far as I understand it. The reported elevation (AFAIK) is the highest spot within the airport boundary. For smaller airports, it's Gomer's best guesstimate. Large airports have generally a smaller variance from end to end (if any) than do GA remote strips in the Rocky Mountains. When you work with mesh and see that XYZ airfield and it's 3,800 foot runway has a difference of 80 feet between the two runway end's elevation ask yourself how that is suppose to be rectified within FSX's/P3D's/FS9's flat airport construct. Maybe there will be a day when non-flat runways can be a reality, in fact I believe it could be done today and fit within FSX or P3D, but it's not a trivial task and to accommodate AI traffic would be a major undertaking. Until then, airports and elevation and higher es mesh will present a challenge. As far as ALL products having issues? Please enjoy the Hawai'i mesh I uploaded to the Library today! :dance:
  6. Jeroen, you're not thinking this out properly. Have you not ever seen a tail wag the dog? Most people think it's the other way around, that a dog wags it's tail. But they have never gotten into the "place the blame elsewhere" routine and that's when it becomes a tail wag the dog situation...
  7. The relationship between mesh and landclass texture is not such that the texture is going to display that much differently (?) on a 38m or 10m or 2m mesh. Possibly when vector is brought into the terrain structure it could show some variance depending upon the quality of the mesh, such as a bridge or mountain road, but in those cases the developmental process needs to have higher demands and tighter controls. As an example of stricter demands due to mesh, I want to place waterfalls around Hawai'i, because there's a bunch of them. It's a world of difference to place onto a default mesh of 38m compared to a 10m or 5m mesh. All of a sudden you need to analyze surrounding mesh points to make sure that the waterfall is dropping down upon the correct mesh point. That means (to me) going in with a program to analyze a small grid surrounding where the waterfall is suppose to fall and making sure that the NE-next mesh point is the direction of the waterfall, rather than aiming for the N-next mesh point. Since it would be a freeware package I can mention it, but also by being free it means it gets done when the developer gets the time.
  8. Courtesy of Pete Dowson of FSUIPC fame is a program called MakeRwys, found at the link below: http://forum.simflight.com/topic/66136-useful-additional-programs/ Run it on an installation of FSX and it will give you more information than you probably want and not in a "database" format. But the resulting output can be culled and made into a database-type file and used or abused to your heart's content. And yes, I'm a slow typist... :lol:
  9. Strange... When I look at the files in TMFviewer it reads LOD10 or 38m. Looked at 0303 (Hawaii), 0202 (Texas) and 0102 (N.Kalifornia). I believe if you do a file size check with FSX you will see little, if any difference? I haven't done a scan of all the files yet, but I will! :lol: And you need to get current on FSGenesis. It's now owned by FS Pilot Shop...
  10. Airport Wizard, as mentioned above. There's a demo available, last I looked.
  11. Land classification is going to register by what is read last (higher up in the Scenery Library inside FSX), which is why you can "sandwich" certain properties of an add on like UTX.
  12. How's that work for you? As they eye doctor might ask "better or worse?"
  13. PHLU on Molokai, I recognized it even before zooming the pics for coordinates. In a few days I will upload some freeware mesh for Hawai'i that might offer you a solution. Or if you're brave enough to see the "almost finished" freeware mesh, send me a PM with an email addy for contact.
  14. Flight1 does have a support forum and is a better choice than expecting some one to come along and give you accurate or maybe not accurate advice.
  15. Bought time... Took long enough... :lol: Thanks Stephen and Paul. May this help to make my journey into the unknown a little less scary. And Thanks to Max for the OP!
  • Create New...