Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (โ‹ฎ) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

OzWhitey

Members
  • Joined

  • Last visited

Everything posted by OzWhitey

  1. Donโ€™t know if anyone already said this, but the Fenix now does 4x sim rate. The update would have come out on the same day you posted. ๐Ÿ™‚
  2. Yeah, if you can run the sim. Even Randazzo says he canโ€™t get the platform to work. This debacle, this day of infamy in flight sim history, is partially your fault, Bert. I tried to organize an Occupy Redmond Three protest prior to the sim launch to try and address these issues. Given that you are a veteran of Occupy Redmond One back in โ€˜12 I thought I might have your support, but when I turned up at MS HQ I was pretty much on my own. So the complaints that you read on Avsim now are pretty much on you and the other OG Avsim โ€œOccupyโ€ crew. People who had the power to change things, but chose to stand idly by and do nothing. Whatever happened to โ€œSolidarity Foreverโ€??
  3. Ha, Iโ€™d forgotten about this post, but Iโ€™m glad I could be of service. ๐Ÿ™‚
  4. Itโ€™s got to be done. Interesting to see that PDE is the most popular option in this survey. Lots of people here and on Reddit saying theyโ€™re just getting the Standard, but the stats here do not support this. I learned to always get the Deluxe+ edition back in the MSFS 2002 days. Iโ€™d be sad if I couldnโ€™t fly aircraft that other people were recommending.
  5. Left my preorder late, but just dropped the hammer on the Aviator edition at AUD$299. Meh, the dollars per hour over a four year period is pretty good value. And Iโ€™ve spent that much on a single aircraft before (PMDG P3D 777 + upgrade, to give just one example). So Aviator Club it is. ๐Ÿ˜Š
  6. Iโ€™ve flown it quite a bit. Itโ€™s not bad. You do need to do the things you mention - balancing fuel between fore and aft - to fly it properly and hit Mach 2. I flew it with real Concorde checklists.
  7. It sounds like itโ€™s your PC. Have you tried turning it off and on again? When you restart the sim, your problem should be solved. If/when you experience further crashes after this, just repeat the process. Also, next time donโ€™t sit at the gate for 15 minutes, take off straight away so youโ€™ll get 15 minutes of flying time. Choose shorter routes that can be done in 4-8 15 minute segments. This Avsim support ticket is now marked as โ€œresolvedโ€. Please submit a new ticket if you encounter any further problems not covered by this fix.
  8. A great deal, but it hasnโ€™t been available for a year now. Just so people know, I checked directly with the dev last week and heโ€™s still not offering it.
  9. Beautiful. One thing Iโ€™m wondering. What is the argument for using the payware Seafront global shipping? Are the models better and/or more native to MSFS? Better night lighting? The reason not to use this product is obvious - other than cost, thereโ€™s around 20 models (I think) rather than 1600. I actually own and have used both on many occasions (have had GAIST for a long while now), Iโ€™m just not an expert so am wondering from a technical perspective whether thereโ€™s any way(s) in which Seafront is more advanced.
  10. The bgl files you make with ortho4xp for p3d are fully compatible with all versions of p3d and fsx. Small print: If you want to make it theoretically better for v5, use the resample.exe file from the v5 sdk. Never noticed any difference between versions, but they seem to be different sizes etc so itโ€™s possible (though unlikely) that something was changed. I do most of my flying in v5.1, and 100% of my flying over ortho, absolutely no compatibility problems and none would be expected. More specifically, p3d has had a problem with blurry ortho rendering in the past. This was fixed late in v4โ€™s run (around v4.4, i think from memory), and v5 does a great job of rendering orthoscenery under challenging conditions.
  11. Thanks for the input, kj. Thatโ€™s an amazingly useful mod youโ€™ve made to Oscarโ€™s tool - thanks so much!
  12. v5 plus ortho is great, and fits well with the australian orbx airports. i tried building oz a while back in x-plane, but the data available was poor. Very happy with everything iโ€™ve seen so far from Arc for northern and central australia.
  13. By the way, regarding the original topic. I've been using Ortho4P3D extensively since I posted. I have come to the conclusion that the redownload of the vector data is just a feature of the P3D version of the program. CWBurnett, I think that you do not experience this as you are not using Ortho4XP to compile your BGLs. Perhaps try rebeuilding a tile sometime with the standard five boxes - including "Build for ESP (FSX/P3D)" - option ticked. I bet that Ortho4P3D will want to re-download your vector data as well, and if you deselect the "Assemble vector data" box when rebuilding, the program will not generate a usable .bgl. So TL;DR, this is just the way the P3D version of Ortho4Xp works. If anyone disagrees, please let me know!
  14. Orbx ortho (included with both AU2 and airports) may display through your scenery as some of it is higher resolution than what you are producing. Orbx landclass should not. I have AU2 installed, and have not noticed this anywhere in Australia where I have ortho tiles (mainly ZL16, with some ZL17). Btw, I've built a lot of northern queensland over the past few months, and have found ARC to be a great source.
  15. Hi guys, Now that I'm awake again, I think I can provide some decent data and clarify the question/situation. Here is my data in three situations: 1. 'Batch build tiles' tick boxes: all 4 "normal" x-plane boxes selected: Assemble vector data, trinagulate, draw water masks, build imagery/DSF. Batch build launched for a number of 1 tiles. Dealing with tile 1 / 1 : +36+022 Step 1 : Building vector data for tile +36+022 : -------- -> Dealing with airports * Recycling OSM data from ..\OSM_data\+30+020\+36+022\+36+022_airports.osm.bz2 LGSP Sparti Air Base 1 runway , lat= 36.97, lon= 22.53 Loading elevation data and smoothing it over airports. * Min altitude: -17.0 , Max altitude: 2375.0 , Mean: 111.07116 Auto-patched 1 runway and 0 piece of taxiway. Flattened 2 helipads. Number of edges at this point: 333 -> Dealing with roads Outcome: OSM data recycled as it should be 2. 'Batch build tiles' tick boxes: all 4 "normal" x-plane boxes selected as above PLUS the "Build for ESP (FSX/P3D" box: Batch build launched for a number of 1 tiles. Dealing with tile 1 / 1 : +38+021 Step 1 : Building vector data for tile +38+021 : -------- Downloading OSM data for ScenProc, this might take some time, please wait... If OSM server rejects our request due to too many requests, will keep trying until successful. Attempting to download OSM data from 38, 21 to 38.25, 21.25 Download successful Attempting to download OSM data from 38.25, 21 to 38.5, 21.25 Download successful Attempting to download OSM data from 38.5, 21 to 38.75, 21.25 Download successful Outcome: OSM data is re-downloaded (this is what I am trying to avoid) 3. 'Batch build tiles' tick boxes: all 4 "normal" x-plane boxes selected as above PLUS the "Build for ESP (FSX/P3D" box PLUS 'ESP_scenproc_script=default.spc' line removed from Ortho4XP config file. Batch build launched for a number of 1 tiles. Dealing with tile 1 / 1 : +38+021 Step 1 : Building vector data for tile +38+021 : -------- Downloading OSM data for ScenProc, this might take some time, please wait... If OSM server rejects our request due to too many requests, will keep trying until successful. Attempting to download OSM data from 38, 21 to 38.25, 21.25 Outcome: OSM data is re-downloaded, behaviour unchanged from scenario 2 i.e. removing this line from the Ortho4XP config file is not the solution. Findings: You will note that selecting the "build for ESP" option add this line/step to the process, even with the scenproc path removed from the config file. "Downloading OSM data for ScenProc, this might take some time, please wait... If OSM server rejects our request due to too many requests, will keep trying until successful." If you run the "build for ESP" step by itself, it does not use the previously downloaded data and no tile results. So far, I can only generate a tile by re-running all 5 steps. Questions: 1. Is there a way to rebuild a tile using only the "build for ESP" step? 2. If I need to run all 5 steps to rebuild a P3D tile - as appears to be the case - is there a way to force the program to re-use the existing OSM data, or is in an intrinsic part of this modified Ortho4XP version that the ESP build requires fresh OSM data each time a tile is built? Note that I am not trying to use Scenproc to generate overlays, rather I am just trying to rebuild basic ortho tiles after post-processing the existing bmps. As per my previous notes, this works for me but is very slow and places unnecessary stress on the OSM servers when rebuilding large areas.
  16. Am trying it right now! As for scenproc - yes, it would be great if you could share your script. Any pointers as to instructions/video to try and get my head around scenproc? Most people seem to give up before succeeding as the instructions are infamously hard to follow.
  17. OK, I've now decided it's not a path issue. If I run tile via batch build with assemble vector data, triangulate 3D mesh, draw water masks and Build for ESP ticked (ie NOT selecting build imagery/DSF), it reuses the data beatifully for the first 3 steps, completing them in about 2 minutes. BUT it doesn't run the critical "Build for ESP" step. If I do what I usually do and have all five boxes ticked - including build imagery/DSF - it does not recycle the previously created data. Interesting. Re: disabling scenproc. Are you suggesting altering this line from the Ortho4CP config? : ESP_scenproc_script=default.spc If so, what would you set it to, or does it just get left out entirely?
  18. Addendum: With my paths setup as above, if I JUST choose the "Assemble vector data" - and nothing else - from the "Batch build tiles" tick boxes on the map, it runs like it should: ------------------------------------------------------------------------------------------------------------ Batch build launched for a number of 1 tiles. Dealing with tile 1 / 1 : +38+024 Step 1 : Building vector data for tile +38+024 : -------- -> Dealing with airports * Recycling OSM data from ..\OSM_data\+30+020\+38+024\+38+024_airports.osm.bz2 LGSY Skyros Airport 2 runways, lat= 38.97, lon= 24.49 Loading elevation data and smoothing it over airports. * Min altitude: -12.0 , Max altitude: 1377.0 , Mean: 39.94991 Auto-patched 2 runways and 25 pieces of taxiway. Flattened 9 helipads. Number of edges at this point: 1258 -> Dealing with roads * Recycling OSM data from ..\OSM_data\+30+020\+38+024\+38+024_big_roads.osm.bz2 * Checking which large roads need levelling. * Buffering banked road network as multipolygon. Encoding it. * Encoding the remaining primary road network as linestrings. Number of edges at this point: 24864 -> Dealing with coastline * Recycling OSM data from ..\OSM_data\+30+020\+38+024\+38+024_coastline.osm.bz2 * Encoding coastline. * Reconstructing its topology. Found 6 contiguous patch(es). Number of edges at this point: 54092 -> Dealing with inland water * Recycling OSM data from ..\OSM_data\+30+020\+38+024\+38+024_water.osm.bz2 * Building water multipolygon. Cleaning it. Encoding it. Number of edges at this point: 55162 -> Inserting edges related to the orthophotos grid -> Inserting additional boundary edges for gluing -> Transcription to the files D:/X-Plane Custome Scenery 2020\zOrtho4XP_+38+024\Data+38+024.poly and .node Final number of constrained edges : 89221 Completed in 30.85sec. ---------------------------------------------------------------------------------------------------------- Unfortunately, once I select all five necessary tick boxes, including "Build for ESP (FSX/P3D", I'm back to: Batch build launched for a number of 1 tiles. Dealing with tile 1 / 1 : +38+024 Step 1 : Building vector data for tile +38+024 : -------- Downloading OSM data for ScenProc, this might take some time, please wait... If OSM server rejects our request due to too many requests, will keep trying until successful. Attempting to download OSM data from 38, 24 to 38.25, 24.25 Download successful Attempting to download OSM data from 38.25, 24 to 38.5, 24.25 Download successful Attempting to download OSM data from 38.5, 24 to 38.75, 24.25 Download successful Attempting to download OSM data from 38.75, 24 to 39.0, 24.25 OSM server MAP rejected our query, new tentative in 2 sec... OSM server MAP rejected our query, new tentative in 4 sec... Download successful Attempting to download OSM data from 38, 24.25 to 38.25, 24.5 OSM server MAP rejected our query, new tentative in 2 sec... OSM server MAP rejected our query, new tentative in 4 sec... OSM server MAP rejected our query, new tentative in 8 sec... OSM server MAP rejected our query, new tentative in 16 sec... OSM server MAP rejected our query, new tentative in 32 sec... OSM server MAP rejected our query, new tentative in 64 sec... ------------------------------------------------------------------------------------------------------------------------- As well as using more OSM data, it's taking me a long time to download the OSM data per tile when the servers are busy (seems to be a very common problem at the moment), sometimes to the point where Step 1 gets stuck. I'm running the .exe. version rather than python.
  19. That may be my problem. I don't have any of the folder pathways setup in Ortho4P3D, as I think the guide here suggests its unnecessary. How have you got your pathways set up? If I point the Base Folder to drive:/<Ortho4P3D Folder>/Tiles (containing the same data as a custom scenery folder if I'd moved the X Plane tiles), my tiles show up on the map view, but I've still got no evidence of reusing most of the OSM data. Did I choose the wrong folder? I've also tried setting this to the main Ortho4P3D folder, still doesn't work plus my built tiles no longer show on the map There are also pathways in the config for custom_dem and custom_overlay_src. I have used both of these in Ortho4XP, but they would seem to be unhelpful/irrelevant here.. FInally, there is the custom_scenery_dir path in the config settings. I've tried setting this to where my created XP tiles are currently stored (drive:/<Ortho4XP Folder>/Tiles, but still no luck with the OSM data reuse: From a tile that I just built, and are now re-running a build on as a test, it gives the following initial output: (ie the same as if no OSM data existed) Downloading OSM data for ScenProc, this might take some time, please wait... If OSM server rejects our request due to too many requests, will keep trying until successful. Attempting to download OSM data from 37, 23 to 37.25, 23.25 Download successful Attempting to download OSM data from 37.25, 23 to 37.5, 23.25 Download successful Attempting to download OSM data from 37.5, 23 to 37.75, 23.25 Download successful It's been a while since I used Ortho4XP, so I'm guessing that I'm just doing something basic wrong in the path settings. Do you have different path setup from what I describe?
  20. Question: rebuilding tiles. When rebuilding tiles - such as after you've post-processed the .bmp files - do you need to complete all 5 steps under the "batch build tiles" menu again? That's: - Assemble vector data - Triangulate 3D mesh - Draw water masks - Build imagery/DSF - Build for ESP My major problem is that the "assemble vector data" step is often slow these days, due to the OSM map servers rejecting queries. It would be great to able to skip this step and use the already-created data in the OSM_data folder (.osm.bz files). However: 1. If I don't select this step, the ESP scenery is not created properly (error message about an empty area) 2. If I do select this step, it only reuses a small amount of the existing data (I think the airport data says it's recycled), whereas most is downloaded again via "Attempting to download OSM data from 48, 0.25 to 48.25, 0.5" etc. The triangulate mesh step and water masks is OK, it's mainly this first step that is problematic and which I want to eliminate if possible. The orthoscenery bmp files are reused and it's obviously necessary to run the "build for ESP" step again anyway. Any thoughts on this? I've been doing a bit of rebuilding post-processed areas this week, and my current workflow is far from optimal. Cheers!
  21. Oops...sorry. That's what you get for Avsimming at 3am.
  22. After reading this thread, I just went and googled the Level D 757 - haven't done that for a year or two or three, you never know they might have posted another screenshot or something. No luck there - but I did find this from Daryl from four years back: http://www.leveldsim.com/forums/future-of-level-d-757_topic24453.html "Oh, how the PMDG forum can stir things up... Yes. Some of you are overly passionate about this niche hobby. We (and by that I mean me) have stated many times that the 757 will be produced, and that there will be no updates about the status of the project, other than the 757 is coming. I recognize that some of you - the hardcore users - don't like this answer, and are apparently concerned about what is happening, want an update, and have begun a poll over at the PMDG forum to get PMDG to produce a 757/767. PMDG can produce whatever they want. There is NOTHING preventing them from producing any airplane they want. They want the 757, why don't they produce it? You want a 757 from PMDG, ask away... ... I have removed posts about the 757, because - quite frankly - I am tired of repeating myself time and again. The 757 is coming. If that doesn't please, then have at PMDG to create a 757... ;-)" ------------------------------ So hey - PMDG? Level D's suggested methodology if we want a 757 is to have a chat to you folk. I'd echo the comments of some of the preivous posters - I would love a 757. I'm a big fan of the Level D 767, or certainly was back in the day. But it shows its age now, and lacks P3D compatibility. So add my vote to the growing number asking you to consider a 757/767 release at some stage in the future, Cheers! Rob
  23. I have been pondering this today, as I have been making photoscenery - what is the role of vector programs for photoscenery users? I think they do have some purpose: 1. If you're water masking your scenery, you need the water data - default misses some lakes. 2. I think - but i'm not sure - that you'll get more road traffic, as it follows the vector roads. At any rate, traffic should be better placed. 3. My scenery has power lines - I suspect they're coming from the vector data. Maybe some of the antennas as well, haven't tried turning off the vector program to see if it's placing them. Can't think of much else that vector data add to photoscenery. If anyone knows - let me know! I'm trying our Orbx Vector, after buying it in the recent sales - despite the general negativity around here to it. I normally use UTX, which I like. So far, Vector seems fine - not aware of it causing me any problems. I suspect long term I'll use it for areas not covered by UTX.
  24. Well, I just reinstalled fsx after my last post, and flew it for the first time in a couple of years (I needed it to run an airport tool that's not p3d compatible). Reminded me of just how much progress p3d had made - you sometimes forget - because each iteration just changes a little - just how far it's come. Advice: spend money on the base P3D, fly it, be happy - and worry about the adding costs some other time!
  25. Guenseli,I think the developer will if buyers demand full P3D compatibility! I buy addons when I'm confident that the vendors are serious about supporting P3D - and avoid the older stuff that 'probably works'. I hate to lose access to airports etc that I've bought, but if that's the price of progress I can live with it. P.S. SIMstarted is splendid - enjoying the paid version, works great with P3D!

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions โ†’ Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.