Jump to content

Emanuel Hagen

admins
  • Content Count

    10079
  • Joined

  • Last visited

  • Days Won

    110

Posts posted by Emanuel Hagen


  1. I won't go into detail what happened with DetCord, that's not for the public eyes. Rest assured he can always contact Aerosoft using the support email address.

    He indeed is an excellent painter, but there were certain limits overstepped which resulted in his ban.

     

    Thanks for forwarding the message, it'll go right to the legal department.


  2. 11 minutes ago, Sabre10 said:

     

    This is an unnecessary distraction during the flight and possibly a drain of valuable resources.

     

    Thanks.

     

    So switch it to a page which is not an unnecessary distraction. There is a useful page for *any* phase of flight, be it the enroute chart of your flightplan.

    I have my EFB running all the time as well in real life.


  3. Hi Louis,

     

    the clickspot of the instinctive disconnect button is indeed not modelled as we did not believe anyone would look down to the thrust levers to disconnect since normally you'd disconnect the AT only in rather busy situations.

    We therefore use the default command to simulate. the AT disconnec button

    • Thanks 1

  4. I've had one single occasion where I changed the altimeter in the A330 (uses the same system as the 320s) was indeed set to STD, but still indicating local pressure altitude, despite actually showing STD on both the FCU and the PFD. There was no way to see that in the flightdeck, only the VATSIM controller noticed.

    In that case a reset of the altimeter to local and right back to STD sorted it out and then my altimeter was indicating correctly.

     

    Afterwards it never happened in over 500h of testflying this year. The developer checked it and I believe it got fixed (must have been two months ago or the like), so make sure you are on the latest version.
    If it still happens with the latest Airbus version you should maybe try it with a different weather engine.

     

    No microsoft based flight simulator so far simulates temprature errors on altimeter readings, however I don't know your weather tool and if it simulates them or not.

    In real life a warmer air mass expands, thus when you're flying at a certain FL in a warm airmass, all other factors remaining unchanged, you'll have a HIGHER true altitude than at ISA conditions. Similarly when flying in a cold air mass you'll have a LOWER true altitude.

    That would of course be shown on the controllers radar scope as VATSIM (and IVAO as well if I'm not mistaken) read true altitudes and then pressure correct only.

    All the weather engines I know of do not simulate temprature error, but I have not tried nor heared of your weather engine before, so who knows...

     


  5. Hi John,

     

    what do you mean with right hand radar screen? I assume the weather radar? Does it show correctly on the left side but only the top on the right ND?

    I believe the WXR is currently only implemented on the left ND for performance reasons.


  6. Regarding the GSX issue: You don't need to adjust any AFCAD: Just change the stand size in the GSX airport configuration menu.

    The reason why the AFCAD is the designed the way it is, is because you can not park several large aircraft next to each other, otherwise the wings could collide. However that's exactly what FSX/P3D would do if the AFCAD allowed for it. Using the GSX editor is the best solution here.

     

    Regarding Johanns question, I am not aware of any update plans at the moment.
    What exactly is wrong with the placing though? I am not aware of any such issue.

    Taxiway and Apronchanges are known, but Aerosoft can just not constantly update any of their scenerys for all changes the real airports undergo.


  7. 3 minutes ago, SK10 said:

    I know its on the FO side and you model it to fly as a CPT, but that should not mean to model it not correctly and as a FO in real life, I'm only fly from the right side

     

    What leads you to this assumption that it's not modelled correctly on purpose? It might be a simple bug instead?

    Since introducing CFD the Airbus is modelled to be flown from both sides.


  8. 12 minutes ago, flycln said:

    Many of your customers have switched, though. It is what it is. 

     

    True, but those customers simply can't expect a seemless experience like most had with P3Dv4. And they can't blame addon developers for it.

     

    P3Dv5 feels very much like a rushed release, probably to set themselves ahead of Microsoft, so if you want to use it: Fine, but complain to the right people.

    If an update comes out and breaks the lights don't expect a fix within a day. It might take longer. And a beta might not resemble the final version. Even if Aerosoft already has betas and adapts products before the official release, LM might still change something the last hour before release which breaks compability again and might take days, or weeks, to fix before being able to update the addon.

    • Upvote 1

  9. I've seen this happen at a couple of sceneries and with different aircraft when the Mesh Terrain resolution was set to a value greater than 5m.
    Try to reduce your Mesh terrain to 5m and see if you still encounter those drops.


    Other planes I've seen this so far (for reference, maybe interesting for others as well):
    KORD - A330/B767/B74x

    ELLX - B74x

    MKJS - A330/B767

     

    All of them were addon sceneries.

    I don't quite know what exactly caused this yet, but in all cases removing the addon sceneries solved the sudden drops. They must somehow be related to aircraft size vs mesh terrain setting vs scenery.


  10. 5 minutes ago, CFG916 said:

    Sorry Mathijs but that's wrong and a sign that Aerosoft is not familiar with the new v5 version of Prepar3D and DX 12. With DX 12 comming up it is a developement issue how much of VRam the addon will use, with DX11 it was not. For me I don't have the A330, i do have the PMDG747 for v5  i'm afraid but a friend of mine does have the bus. We both using P3Dv5 with H1, we do have absolutly the same hardware too. GraKa NVidia 1080 GTX 8Gb Vram with the newest driver. We do have all the slider and other settings at the same way. We both have LatinVFR Miami for P3Dv5 and when we start at Miami Gate F16, me with PMDG 747 and my friend with Aerosoft A330, I do have an VRam use of 4,5 GB and my friend has 6,3 GB. So it is not a question to asked Lockhead Martin but you ! And it's not a good way to send customers to onather developer before you understand the new engine right. Sorry but this is my opinion.

    Regards Axel

     

    You're of course entitled your opinion Axel, but that doesn't mean it's correct in terms of the facts concerned.

    For instance having "absolutely the same hardware" while using two different computers does by no means mean you'll get the same performance, unless you would have an identical windows version, identical programs running at the same time, use Windows in the identical way, have an identical flight loaded, etc.

    You can have the same hardware and get different results due to different software. Probably even without knowing you have different software.

    Unless you have the same hardware, both have a totally fresh windows reinstallation and only have a vanilla P3D you can simply not compare things.


  11. Hi Laurie,

     

    99% of Alpha Floor activations I saw with customers so far were caused by a rotation which is far to quick, thus causing a stall right on rotation.

     

    The last 1% is usually caused by windshifts from an erratic weather addon which causes the speed to fall below minimum during takeoff.


  12. It happens in P3Dv4/5 with Cologne Bonn Professional.

    The DME for the ILS of runway 32R and 24 is not implemented. Bug.

     

    14L has a DME though but shouldn't have one.

     

    Clear scenery bug, not aircraft or database related.

    • Upvote 1

  13. "If you have any more questions feel free to open a new topic."

     

    Okay, so I open a new topic.

     

    We all know the airport will not get a redesign by Aerosoft and the GAP team is retired.

     

    However Olivers answer does not address many questions asked before the topic got closed.

     

    Once again:
     

    "the wrong N3/N5 signage"

     

    That taxiway is called N3 since 2010. The original scenery being developed in 2015/2016 is not an excuse. Please correct the bug.

     

    "Why does the terminal behind the C gates have such a bad resolution, both at daylight and especially during night time, while the A and B gates have a rather good resolution?"

    • Thanks 1
×
×
  • Create New...