Forum Replies Created

Viewing 15 posts - 1 through 15 (of 382 total)
  • Author
    Posts
  • in reply to: Alaskan Reef ?? #1552

    Hello, still not finding the anomaly in either P3Dv4 or P3Dv5. Ran out of production disk space and had to uninstall FSX, so I’m presuming you have FSX.

    I also note that you’re probably running with the default vector set and not Orbx Global Vector or Flight1 Ultimate Terrain due to the unnatural cliffs seen in the background.

    These types of anomalies are usually seen in the vector data (water polygons) and are not caused by the terrain mesh.

    If my assumptions are correct, I’d recommend either of the above-mentioned products that would fix the error.

    Justin

     

    in reply to: Alaskan Reef ?? #1550

    Hello

    Do you have any Orbx Alaska products installed?

    Justin

    in reply to: Alaskan Reef ?? #1547

    Hello,

    Sorry for the delay.  I’m not finding the anomaly.  I enabled attachments so if you could provide a screenshot and coords, it would help me track the problem down.

    Thanks

    Justin

    in reply to: Mile Hi Airport (Private) 47CO Alt. Correction #1545

    I made up a quick ADE file for you to start with.  This corrects the airport’s location and includes a background image to use as a guide for your edits.

    The  47CO_background_HiRes.jpg file in the zip is for reference only — it’s too big for ADE to handle.  Use the 47CO_background.jpg file and the corner coordinates found in the included .txt file.

    Have fun!

    Attachments:
    You must be logged in to view attached files.
    in reply to: Mile Hi Airport (Private) 47CO Alt. Correction #1539

    Hello

    Sorry for the delay. Took awhile to track this one down.

    The real-life airstrip is actually about 86 km due east of it’s location in FSX/P3D. The published info is wrong.  Airnav shows the airport at 104d50m west.  In actuality it’s at 103d50m west.

    When you go to 47CO on Airnav and scroll down to Airport Ownership and Management, note the address.  Now plug that address into Google Maps or Bing Maps.  You’ll find the strip 86 km east of its location in FSX/P3D.  Move the airport to it’s actual location and you’ll probably find the terrain matches the airport much better than where it is now.

    Hope this helps

    Justin

     

    in reply to: Coupon Code #1531

    Hi John,

    No problem. Sorry for the delay, but you got it.

    Thanks

    Justin

    in reply to: Galaxy Membership? #1525

    HI Doug

    Sorry it took so long but you should now see Galaxy-appropriate prices in the Toposim Distribution Center.

    Thanks

    Justin

     

     

    in reply to: P3D V5? #1524

    Hello

    First quick go around this morning revealed no show stoppers.  Just add your existing install paths to the Scenery Library as usual and adjust your Options | Graphics | World – Mesh Resolution slider to the highest TOPOSIM resolution you have, i.e., Continents – 10m or UltraMesh – 2m.

    Thanks

    Justin

    in reply to: Galaxy Membership? #1518

    Hi Marcus

    You should be good to go.  Next time you log into Toposim Distribution Center you should now see Galaxy pricing.

    Thanks!  Welcome back.

    Justin

    in reply to: Plateau terrain and airports #1514

    Hello,

    Yeah, the plateaus have been a pain in the butt since FS2000, unfortunately.

    Here’s a good overview from an article I wrote for flightsim.com several years ago that explains the problem . . .

    Introduction to Terrain Mesh

    As for them being fixed in the future, that is problematic with the advent of MFSXXXX, which has no flat airport imitations, eliminating the problem going forward, finally. Production time going forward is being mostly focused on the new simulator, which assumes that most will probably switch over once it becomes available to the consumer. In those (rare?) cases where simmers might stay with FSX/P3D, commissioned ATAPs can be addressed on an individual basis.

    As the article states towards the end,

    “So while most airports will have no jarring visual impact with their minimal plateaus, there are some airports in the world that would require considerable adjustments. Most simmers who have embraced high-resolution terrain mesh have long ago accepted the tradeoff of occasional jarring plateaus in order to experience the often spectacular results seen enroute between airports, and decide not to throw the baby out with the bathwater.”

    Hope this helps

    Justin

     

    in reply to: BOGO #1513

    Hi Kevin

    Sorry for the delay.  I have added European Continent Bundle to your downloads.  You should see it next time you log in and click My Account, Downloads.

    Thanks

    Justin

    in reply to: Ultramesh and older Mesh #1508

    Hi John

    The higher LOD number is more detailed, so LOD14 is 2.3m horizontal resolution, while LOD12 is 9.6m horizontal resolution.  No need to delete LOD12 stuff because the terrain engine automatically loads the highest resolution it finds in the database for display.

    I always layer the Toposim Continents right above the default cities, and the UltraMesh right above the Toposim Continents.

    Hope this helps

    Thanks

    Justin

     

    in reply to: BOGO #1505

    Hi Toggle

    The BOGO promotion actually ended months ago. I thought I had scrubbed the site of any mention of BOGO but apparently not. My mistake.

    Which other continent would you like?

    Justin

     

    in reply to: Canada Toposim from Steam #1502

    Hello

    Each continent has it’s own folder, i.e., NorthAmerica, SouthAmerica, Africa, Europe, Asia, etc.  Each continent folder has a scenery subfolder into which every BGL for that continent goes.

    What happens when you go to an airport, in, say, Ontario?

    Which airport is throwing the error? Is it a default airport or addon? Which other addons do you have active in the area?

    Justin

    in reply to: Canada Toposim from Steam #1498

    Hi Uncle Joe

    Actually, FSX-SE isn’t loading ALL the files in the folder into memory, only the ones near where you’re starting, so my best guess here is to investigate the airport where you’re starting and any other airport in the vicinity.  If you can, change your starting airport and see if the problem still happens and we can go from there.

    Thanks

    Justin

Viewing 15 posts - 1 through 15 (of 382 total)