Jump to content

John Dow

Orbx Team
  • Posts

    9,727
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by John Dow

  1. Yes I've made a comment however in case nothing comes of it, I have copied the [FLTSIM] section encompassing all the liveries into a text file, saved to the same folder. If an update changes the relevant text it will be less than a minute to restore the changes.
  2. First we've heard of it... sure it was a genuine Microsoft alert?
  3. Totally uninstalled. The click click is probably the ignition key up the top of the pillar, mine was animating as though it was an normal starter key going into the start and out again.
  4. It's always done that I think. The lady is one who you wouldn't get on the wrong side of! She'd pick you up with one hand and toss you out the window.
  5. Yes. If you go into the aircraft.cfg file (in the simobjects folder, you might need to search for the location) you'll find each model has its own section, and towards the bottom of each section you'll see a line that includes "RAMP". Delete the word RAMP leaving just the "". Do that for each entry in the file. That should be enough. I'll add to this post later when I'm on the pc with a bit more detail. Here's what I posted elsewhere, should be enough info for you to prevent the Opticas being seen everywhere: In my aircraft folder: M:\MSFS Community\msfs\EA-7 Edgley Optica\Community\Orbx-aircraft-optica\SimObjects\Airplanes\orbx_optica there's a file called aircraft.cfg. It lists the various models under the [FLTSIM.X] sections. In each of these at the bottom are the lines: isAirTraffic=1 isUserSelectable=1 atc_parking_types="RAMP" which I have changed for each model to read: isAirTraffic=0 isUserSelectable=1 atc_parking_types="" A check of a few airfields just now hasn't shown any Opticas as AI or parked aircraft.
  6. Almost all these problems have been in the pipeline somewhere between Orbx servers and your ISP, if so Orbx can't do anything about it. But I'm sure someone will check the Orbx servers if the slow speeds continue.
  7. I've been wondering this myself. However the notes for the aircraft indicate that the original Opticas didn't have differential braking. It was added to this MSFS model to make ground handling easier. So the differential braking wasn't modelled. If you prefer to taxi more realistically, you should use both of your toe brakes together, or for full realism pull back on the brake lever as required.
  8. I hear what you're saying and requesting but the Open Landclass products have only replaced the default textures with upgraded and more accurate textures for 'land class', not for details such as bridges. The FS and P3D sceneries use a 1km x 1km grid system (modifiable to a certain extent) that lays down scenery approximating the actual scenery for an area. You might have open farmland in this grid cell, forest in the next, suburbs in the next. But it doesn't alter details such as roads and bridges. Vector does attempt to make roads and bridges and a whole lot of other features more accurate but it mostly relies on publicly available geodata to accomplish this, and is therefore mostly limited by the information that is out there in the public domain. I know it's annoying to have details that aren't right in the sim but suspension of disbelief is an important part of simming. There are freeware scenery editing programs available that might allow an exclusion to be put in the bridge location however I don't know enough about them to say for sure. it might be an avenue for investigation if you're really keen. But as you say, in the landclass product, the cities and towns don't look anything like reality so an extra bridge might not make that much difference anyway.
  9. Here's a comparison of the Cambridge Airport from NZA Simulations with Hobart in the background, with a real world shot taken on 2 June from a Boeing 717 out of Hobart Airport.
  10. Dead hard drive? Sounds terminal. If it doesn't spin or attempt to spool up, I have read of people getting the exact same model drive and swapping over the control board, but I'm not sure of success rates. I had a work pc once that wouldn't boot up. Nothing we tried would make it go past BIOS. So I dropped it on the desk, by allowing it to fall directly on to it's base from a vertical position (It was a flat desktop pc) which I guess was the equivalent of allowing it to drop dead flat from 12-18", and the shock freed up the heads and it booted normally. HDDs are pretty robust so a moderate amount of percussive maintenance isn't likely to damage it if the heads are stuck and need to be freed up. Good luck.
  11. Confirm that your flight model is Modern not Legacy. I have no tendency to roll in flight. Some find the elevator control too sluggish, the quick fix is to change the sensitivities in your Controls in MSFS, and save as an Optica profile. DOn't just save generally or your Asobo aircraft will be far too skittish. I used 25% for roll and 50% for pitch when I set my profile, however I now use FSUIPC. If you have FSUIPC you can tailor the sensitivities and save for each aircraft, the thing to remember is you need to disable the MSFS control that you are setting up in FSUIPC. So far I have only set the three primary control axes as the rest all seem to work well enough in MSFS.
  12. Are you using the Modern flight model? It's not designed to work with the Legacy Flight Model. I don't have any of the problems you are having.
  13. Bit harsh. The explanation clearly states that the problem is caused by an update to MSFS after the product was developed. The developer is trying to fix the problem, which may not be an easy task. Normal protocol in the case of software that was working and is not working temporarily while the developer finds a solution is to show a bit of patience and wait for a result. I imagine the response to your query was in the expectation that the accepted protocols would apply.
  14. Pretty sure the turning as active in the betas, so maybe an old file crept in to the build.
  15. Are your controls set up corectly? Might there have been some residual throttle even though your joystick throttle was at minimum?
  16. I'm sure they'll get around to it in their own time. I doubt it's an easy fix, they probably don't even know why it's happening. There doesn't seem to be any consistency in the pauses. There's a Zendesk you can log bug reports etc, but you'd need to have something you've logged for them to even look at it.
  17. Thanks... almost over in my time zone!
  18. This project sounds like a job for the contributors to flightsim.to scenery library. Freeware can be a mix of textures and imagery gleaned from various sources that Orbx cannot use. I'm sure a clever freeware develper can use available library objects to create the look and feel of YWLM without it necessarily being accurate, aftyer all something is usually better than nothing!
  19. I ran a test flight with this mesh from Queenstown to Milford Sound. No issues at all with the mesh. However at Milford Sound, with the freeware airport add-on from flightsim.to installed, I saw mesh anomalies around NZMF airport. No doubt as time fgoes on the freeware will be adjusted to suit this new mesh. (I hope). The quality of the mesh as you fly up the lake and then climb over to NZMF is absolutely stunning.
  20. The P3D engine isn't particularly good at textures that have been exhausted. The trick is to find the settings that allow you to fly at what speed you want to into the scenery you want without going into 'debt'. A 737 at 300 kts will quickly exhaust the ability of the computer to keep up. Try grabbing a small simple GA plane like the Maule and fly into the same scenery. Chances are it will perform much better. If so, reduce your sliders across the board one notch from the bottom, check the scenery is OK, then start moving the sliders up a notch at a time until you reach a point where the scenery is able to keep up. P3DV5 does perform better but it is also easier to get into texture 'debt', but it's worth it for the smoother performance at the same settings.
  21. Unlikely to see anything developed for Melbourne area until a lagging problem in the default is resolved. The problem has come to light in testing. To test for yourself, take a GA flight from say YMEN over the CBD to Moorabbin and a bit further, and then return towards YMEN and YML. We've been getting long lags and pauses, my last flight I had 2-3 second lags down past Moorabbin and up to 8-10 seconds approaching YMEN, in default MSFS scenery.
×
×
  • Create New...