Jump to content

Schorle

Members
  • Content Count

    38
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

24 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    I belong to both VATSIM & IVAO
  • Virtual Airlines
    No

Recent Profile Visitors

518 profile views
  1. V 1.15 for Vulkan is out. Doesn't work for me though. Displaying no clouds.
  2. Well.......I got weak and bought it. Thanls for the discount information. Hope I won't regret buying the plane 🙂
  3. Hi Vesalius, thanks a lot for your feedback. Much appreciated. Little bit disapointing that there is no good documentation. Have to think about buying it a little more I guess. You know if there ever will be a sale of the A300?
  4. Been thinking abut buying the Inibuidls A300 but because I like to study manuals I'd like to ask if somebody could tell with what kind of documentation the plane is beeing shipped. Considering the steep pricetag I'm hoping for comprehensive PMDG-like manuals.
  5. I'm using a 2 gig M2 SSD already. Nothing changed, only updated Windows to newest version.
  6. Since I upgraded my Windows to the most current version MSFS takes ages to load (approx 5 minutes). Before windows update loading times were about 5 times better. Anyone else expierence that? Anything I can do to fix this? Thanks!
  7. I'm using 3 which equals 48Hz (144/3=48). Working great for me.
  8. Ok. I am blind. Pls disregard. Mods pls delete this thread. Thx!
  9. I'm a little bit surprised I have not seen this on this forum (or maybe I'm blind...). Just qouting official Asobo forum. On my system I'm gaining around 15 FPS using Airliners: It’s super easy to try and you don’t risk to break anything in the sim. The file to edit can be found here: MS Store version: C:\Users\YOURNAME\AppData\Local\Packages\Microsoft.FlightSimulator_RANDOMCODE\LocalCache\Packages\Official\OneStore\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared\BaseInstrument.js OR %localappdata%\Packages\Microsoft.FlightSimulator_RANDOMCODE\LocalCache\Packages\Official\OneStore\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared\BaseInstrument.js Steam version: C:\Users\YOURNAME\AppData\Local\Packages\Microsoft.FlightSimulator_RANDOMCODE\LocalCache\Packages\Official\Steam\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared\BaseInstrument.js OR %localappdata%\Packages\Microsoft.FlightSimulator_RANDOMCODE\LocalCache\Packages\Official\Steam\asobo-vcockpits-instruments\html_ui\Pages\VCockpit\Instruments\Shared\BaseInstrument.js To edit the BaseInstrument.js file I suggest to use a code editor as Notepad++ or Sublime Text (both free). Backup the file making a copy on your desktop to restore it in case you encounter any problem. This is the part to be edited (line 235 in my case but may be different): CanUpdate() { var quality = this.getQuality(); if (quality == Quality.medium) { if ((this.frameCount % 8) != 0) { return false; } } else if (quality == Quality.low) { if ((this.frameCount % 32) != 0) { return false; } } else if (quality == Quality.hidden) { if ((this.frameCount % 128) != 0) { return false; } } else if (quality == Quality.disabled) { return false; } return true; } and overwrite it to his new code: CanUpdate() { var quality = this.getQuality(); if (quality == Quality.high) { if ((this.frameCount % 3) != 0) { return false; } } if (quality == Quality.medium) { if ((this.frameCount % 8) != 0) { return false; } } else if (quality == Quality.low) { if ((this.frameCount % 32) != 0) { return false; } } else if (quality == Quality.hidden) { if ((this.frameCount % 128) != 0) { return false; } } else if (quality == Quality.disabled) { return false; } return true; } All that is changing is that you are adding in these lines: if (quality == Quality.high) { if ((this.frameCount % 3) != 0) { return false; } which are setting a refresh rate of the screens when in the cockpit (quality = high) and it’s setting a division of your screen refresh rate (144/3, or 60/3 or 120/3, whatever) and you can change that ‘3’ to be whatever you want. The higher the number, the smaller the end refresh will be and the better performance you should get but the more choppy the little screens will refresh. Hope this helps some people to get better FPS. Surely helped me a lot!
  10. Thanks for your feedback guys. I guess this is normal behaviour then.
  11. First of all: wonderful bird! Only "problem" I have: Aircraft reaction to aileron and elevator joystick input seems to be very sluggish compared to all other planes I'm used to (PMDG 737, TFDI 717 FSL A320). Even maxing out sensitivity of all axes doesn't change much. Is this a problem on my side or ist this the way it is meant to be? Thanks for feedback!
  12. I know this is an old topic but is this checklist still available somewhere? Thanks!
×
×
  • Create New...