Jump to content

Fragged^2

Members
  • Content Count

    143
  • Joined

  • Last visited

Everything posted by Fragged^2

  1. Small issue: When ever there's an update for the updater, version number is missing on the first launch of the updater.
  2. When A/THR is active, after moving throttle levers to MAN/FLEX/TOGA, moving the thrust levers below CL (climb) will simply limit the maximum commanded thrust to that position - idle. You can move the levers all the way to idle, which means your allowing the autothrottle to command thrust between idle and idle. It will not however disconnect/disable autothrottle. For that you need to hit the disconnect button.
  3. What can we expect to see in today's update? And when will it be out? (do I go drinking after work, or fly the bus?)
  4. Running Insider builds on your sim PC is just asking for trouble. Build updates do odd things, test releases do even odder things. I've had apps deleted by Windows 10 builds. Did the Add/Remove (Apps in Windows 10 new UI) list the Aerosoft after the update anymore? Was it actually uninstalled or just the files removed?
  5. The problem is the high fluctuation in frame times with the sim. On approach the framerate might dip close to 0 for a fraction of a second. The new bus apparently does FBW/AP calculations per frame. This causes the plane to jump around like crazy at times when the sim stutters on approach. London is really bad for example with EGKK, EGLL and EGLC payware airports and all the autogen buildings. I'm sure AS could do something about how touchy the FBW/AP is with stutters, but the biggest issue is the sim itself. Be it absolute performance limits due to poor hardware utilization or the myriad of poorly documented / explained settings. The sim gives no idea for users on which sliders affect CPU / GPU / VRAM / RAM usage, not to count all the possible .cfg tweaks. Sorry for the rant..
  6. Memory speed has almost no impact on game performance, usually. I also see it on a i7 8700k + DDR4. The sim is still far from optimized for modern hardware.
  7. Check one of the included liveries..? A320: [fltsim] fallback.1=..\..\Aerosoft A320-A321 Professional Base\Tex_FB_VC fallback.2=..\..\Aerosoft A320-A321 Professional Base\Tex_FB_A320 A321: [fltsim] fallback.1=..\..\Aerosoft A320-A321 Professional Base\Tex_FB_VC fallback.2=..\..\Aerosoft A320-A321 Professional Base\Tex_FB_A321
  8. Hi, What I did: 1) Switch on vhf1 (left side radio panel), tuned 122.8 (Vatsim unicom) 2) Switch on vhf2 (right side radio panel), tuned 135.550 (which happened to be online) So far things worked, I wasn't receiving on vhf2/com2 as the receive switch was in it's default off position for vhf2/com2. 3) Switch on vhf2/com2 receive, now receiving on vhf2/com2, tuned to 135.550 4) Turn off vhf2/com2 receive, but still receiving on it. Text message received after turning vhf2/com2 receive back to off. Also the transmit vhf1/2 buttons shouldn't be coupled to the receive knobs like they are now. From previous picture, click vhf2/com2 transmit and we get here, it should only touch the transmit button: And in this state vhf1 is still being received even than the volume knob is turned off. Thanks, Joona
  9. How so? Equal or larger than 4.3. Returns true for 4.3 or anything higher. Though obviously it's more tricky than that with version numbers that are not strictly numerical.
  10. Could you do a p3d version check during the installer to make sure ppl have 4.3 or higher?
  11. Radio is receiving on com2 even than the com2 receive switch is turned off. Also switching transmit to com2 shouldn't touch the receive buttons (right? this can't be one of those Airbus logic things).
×
×
  • Create New...