Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

FWAviation

members
  • Content Count

    468
  • Joined

  • Last visited

Community Reputation

425 Excellent

1 Follower

About FWAviation

  • Rank
    Gliderpilot

Recent Profile Visitors

2604 profile views
  1. I know that the ground textures at the real Tenerife South Airport are a bit quirky (they misspelled "LENGTH" as "LENGHT" themselves at taxiway B6, near the threshold of runway 25), but according to the Google Maps satellite imagery, this ground marking near the threshold of runway 07 (at the turn from taxiway T to taxiway B2) actually does read "LENGTH" in real life. Can you fix it?
  2. @MartinM I second your remarks especially about the hotels in the south of the island. It sure wouldn't have hurt the immersion of the otherwise very good scenery if we could see some of those hotels during approach instead of that rather generic autogen.
  3. Sorry, I know this is hugely off-topic, but since you mentioned that number here: What marked the start of those three years for you? I am a bit puzzled about that number, since you guys had the first preview topic for the A330 already in early 2015. I'm just curious, maybe there was a significant shift in that project in 2016 that I didn't know about so far.
  4. Thanks for the quick help, @OPabst! I had the AirHispania/Alberto Sanchez freeware photoscenery for the Canary Islands installed which contained some BGL files for GCXO, including an ADE file. I de-activated all those files, and just to be sure, also all other BGL files from that scenery that referred to Tenerife. That fixed the problem.
  5. While all jetways are present in Tenerife South, only the easternmost gate at Tenerife North has a set of jetways. The other jetways are missing. What could be the reason? I ran the setup normally, there were no error messages whatsoever. This is in P3D v4.5, SODE is installed, but I guess that by default, the scenery has the Strg+J jetways, right?
  6. Thanks, @mopperle, but sadly, changing the themes (IPS Default 4 was my preset theme anyway) did not help.
  7. Hi @Mathijs Kok and to the other members of the Aerosoft team, in recent days I notice that a large number of forum posts don't display any dates. So it appears that the problem has become even more serious than in spring. One example is the A330 preview topic where only the posts that were posted until June 7 and within the last 24 hours show a date. Did you get any further in searching for the cause of that?
  8. @maukro_1990 Na ja, die Antwort von Oliver war aber ja schon recht eindeutig: EDDL ist in Entwicklung, aber es gibt auch nicht immer neue Zwischenstände zu vermelden - erst recht nicht, wenn nicht Aerosoft, sondern ein Externer der Entwickler ist. Ich vermute ganz stark, dass das German-Airports-Team EDDL entwickelt, und bei diesem Team traten in der Vergangenheit leider immer wieder längere "Funkstillen" auf. Damals bei der Entwicklung von Frankfurt v2 hat es auch manchmal zig Monate gedauert, bis es neue Informationen gab. Das liegt wohl auch daran, dass das Team nur nebenberuflich Add-Ons entwickelt. Und jeder Entwickler ist auch anders, was die Freigiebigkeit mit Infos und Preview-Bildern angeht. Auch jedes Projekt ist anders, und Prioritäten können sich im Laufe der Zeit verschieben. Während sim-wings ansonsten immer ganz gerne mal alle paar Monate Zwischenstände rausgibt, war bei der gestern erschienenen Teneriffa-Süd-Szenerie auch über lange Monate Funkstille - und das, obwohl der Release ursprünglich mal für Anfang 2018 angekündigt worden war. Da steckt man manchmal nicht drin... Ich kann aber angesichts des Geschreis, das hier und anderswo bei Previews seitens einiger User immer wieder stattfindet, auch gut verstehen, dass Entwickler irgendwann mal die Nase voll haben und einfach nur in Ruhe arbeiten wollen, ohne dass irgendjemand gleich bei einem Work-in-Progress-Bild rumnörgelt, dass da eine bestimmte Bodenplatte auf dem Vorfeld noch nicht genau so wie in der Realität modelliert ist.
  9. @Kristian1484, I'm not a staff member, but let me point out that you already got an answer by Mathijs Kok about the take-off call-outs. So it would be nice of you if you could stop flooding this forum with call-out questions. Mathijs wrote: And we do not plan to change our call-outs, a call like V1 is done by the PNF and thus belongs in the complete flow of calls and actions and we believe it should not be separated. So this means: Just like in Aerosoft's A320 series, there will be no takeoff call-outs, at least besides the ones made by the co-pilot when you switch him/her on in the checklist menu. And since Aerosoft has modelled the original landing call-outs also in their A320 series, you can certainly expect the original landing call-out sounds in the A330 as well. The sounds you posted above are from an A320, but all Airbus aircraft have the same landing call-out sounds (besides the earliest generation of Airbusses, they had a more robotic-sounding call-out voice).
  10. I have become cautious about manually installing sceneries that were designed for FSX and/or the 32-bit versions of P3D into P3Dv4, I must say. It might work for some, but might cause problems for other users. I installed a few non-P3Dv4-native sceneries (like SkyHighSim's Belgrade and Tivat) into my P3Dv4 a few months ago and suddenly got an increase of CTDs even when I was flying nowhere near those sceneries. So I deactivated them, everything seems to be fine again since then. I can understand the need for having a decent Iceland and Keflavik in P3Dv4 (and, as a matter of fact, I installed at least Keflavik into P3Dv4 a few months ago, so far without noticeable problems), but I suppose one should be careful about forcing those non-native sceneries down the throat of P3Dv4. I guess Aerosoft has good reasons why it usually does not support any third-party fixes, workarounds and patches for those old 32-bit sceneries that are not officially compatible with P3Dv4.
  11. Thank you for your feedback, @Secondator! I hope that you can find the cause of the speed oscillations. I keep getting them when the FMC is not programmed, so a solution would be much appreciated. I will see whether I get the managed speed drops again with a programmed FMC. So far, I had no further problems with that, but if I should, I will report back those problems in the corresponding topic. If I may (without opening a new topic for that), I would like to ask about the following problem I addressed in my fourth post in this topic. Is there any known cause to that? On a side note, you will notice at 1:03 and 4:13 that the autopilot makes a sudden slight right turn and then back to the left during approach in order to stay at the localizer. This is pretty typical for my ILS/autopilot approaches in the Airbus Professional family. And I believe this has been reported here already by other users - and the probable cause you guys named in those cases were FPS drops due to the loading of scenery. I do not notice any unusual FPS drops or visual scenery loading effects at those two points, though. So if anyone has an explanation for that problem, too, that would be much appreciated as well.
  12. Sorry, I rather took the video offline because I thought that there would be no response anymore and everyone who should see it had already seen it. No, the speed never shows 100 knots. It does drop below the set speed (138 knots), but only by a maximum of about 10 knots. As I have written in my first post, the speed oscillates only mildly at the start of the final approach (that means, starting from the point of glide slope capture) and the more the speed drops towards the 138 knots mark (and below), it oscillates more strongly, leading to the "Speed! Speed!" warning sound during most of the final minutes of approach. Apart from that, you understood everything correctly.
  13. @Patrice_cesson Thanks for your input, Patrice. Luckily, I don't have the crashes and blinking speed numbers you encountered, but it's good to know that you had those autothrust issues as well. @Mathijs Kok So your recommendation is to leave FSUIPC as it is? And apart from that, you do not have an idea what could cause these problems or what I can do next? It is interesting that Patrice had no such problems in version 1.2.3.0 (me neither), so I'm tempted to revert to that version and wait for a stable new version. I can say, though, that I made a flight with fully programmed FMC in the Eurowings A320 (D-AIZV) from Hamburg to Lanzarote yesterday - and that one went very well. No strange speed reductions above 10,000 feet, a normal cruising speed of Mach 0.79, and of course no speed mode/thrust oscillations during final approach (I didn't expect the latter anyway due to the fully managed flight mode). So at least the managed speed problems (with fully programmed FMC) I mentioned in one of my previous posts seem to be an only occasional issue.
  14. If you mean by that, "have you configured your throttles through FSUIPC, i.e. have you changed sensitivity of thrust, rudder etc. through FSUIPC", then yes. I'd just like to point out that I have been using FSUIPC since mid-January now, so way before my current autothrottle problems in the Airbus started. And I haven't changed any of my FSUIPC settings since January. But still, I wonder whether there's something in version 1.2.3.2 reacting more sensitively to FSUIPC than previous versions of the Airbus Professional that I operated. It might also be a change in FSUIPC that went unnoticed by me (although that is probably highly unlikely). Or the problem might still be not connected to FSUIPC at all. But if you have any idea what I should change about FSUIPC (at least for a test), I'm of course open to that.
  15. No changes on my PC at all recently (besides the occasional Windows update, but that was already after the autothrust problems occurred). The only changes in my sim in recent weeks was that I installed a couple of (P3Dv4-native or -compatible) sceneries and the latest NavDataPro AIRAC cycle 1904. I have touched no settings in my sim, so I see nothing so far which could affect autothrust behaviour in the Airbus. Or can a scenery or an AIRAC set alter any files in such a way that even such a feature inside an airplane add-on can be affected? I use FSUIPC, though - and I know that there have been cases where this created bugs with the throttles or other hardware. Could this be a trace to follow?
×
×
  • Create New...