Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 07/05/20 in Posts

  1. 3 points
    PUBLIC APOLOGY FROM AUSTRALIAN AIRLINES VA We have been advised by AEROSOFT that some members at AAVA have been uploading pirated software via the Aussie Airlines public upload box, a system designed to share freeware aircraft and programs, that enhance the user experience of flight sim. This box was public and open, and not monitored or moderated by AAVA and this has now been seen as a gross oversight. Australian Airlines VA is a small community based VA, but will not be part of piracy and have advised members of the stringent and serious fines and consequences of software piracy, not only to the individual users but also to the VA. AAVA also strongly advises other communities and users to monitor files and systems in order to stamp out piracy. AAVA has now removed the upload box, and link from the website. AAVA apologizes to all those affected by this oversight including the software companies, hosting providers and service providers involved. AAVA has taken immediate action for this situation not to occur again, and advised members as a general announcement to purchase all aircraft from the rightful owner if they wish to use them. Thank you.
  2. 3 points
    Es sind die Beta Versionen der X-America und X-Africa verfügbar: https://simheaven.com/xp11-sceneries/ Für Kommentare dazu am besten ein neues Thema aufmachen, bitte nicht hier reinschreiben! Hab das eben noch gerade so vor meinen Urlaub geschafft Ich bin im August wieder zurück!
  3. 3 points
    In progress (ignore graphics, colors etc) There is some other stuff being done that we are doing with our friends at PMDG that I hope to show soon.
  4. 2 points
    So... I was on the beta for the CRJ 700/900 X way back when. I had just started flying the plane in real life, and was excited to see a decent version come to our simulators. Unfortunately, it was never as good as it could have been in my opinion, and was more or less released as public beta (again, my opinion). So I did not fly it much. Since then, years have passed, I'm still flying the CRJ in real life though now from a different seat, we are a couple of P3D versions along and with the discount for owners of the previous version, I decided to check it out again. First quick flight, a departure from an airport I know well. Fully set up, mass and balance, route (an SID, short intermediate leg and a STAR back to the field). Graphics are a lot better, sound is as well. But how is it possible to still not have LNAV figured out? Inserting a direct to waypoint draws a line from some imaginary point on the MFD for some reason, something you will not see on the actual plane. It wiggles over waypoints in a Fair Weather theme, it undershot the less than 90 degree turn to base, tries to correct it in the short distance between there and the turn to final and because of that completely overshoots the turn to final. Once on final, it has captured the LOC1 and GS but NAV-to-NAV mode still seems to not be implemented, as the EFIS nav source is not automatically switched from white to green needles. Eventually somewhat stabilized on the approach I take over manually and then it flies fine. I thought, maybe I'm being harsh, or the plane does not like a flight plan with arrival and departure at the same airport. Lets try a full flight and see what happens. So I load up the plane for a full flight from C&D. Tallinn to Warsaw, a common CRJ flight before the pandemic. Routing ORTAX 1T, ORTAX L729 LUTAL P870 BOKSU M857 GERVI P851 NEPOX, NEPOX 4U for ILS Y RW33. FL380 I set it up as I would the real plane, removed some of the double waypoints. Most of this is possible so that is a plus. Off we go! For some reason, when checking the LEGS page, all cruising waypoints have FL370 listed. But my cruising altitude is FL380. I double check the FMS performance and VNAV pages, and yep... FL380 is set correctly. Why does it say FL370 everywhere in the LEGS page? Well, let's just edit it. I put FL380 in manually at the first waypoint past top of climb. This should normally recalculate the vertical profile and update all the other points that don't have specific constraints set. Nope, still all following waypoints are at FL370. And what is even more fun, VNAV is stuck in CLIMB mode. I'm at my cruising altitude and it is still indicating CLIMB. No way to switch to CRZ profile either. So, I start setting up a copy of my flight in the secondary flightplan. Everything inserted, activated, quick direct to nearest waypoint... And all the waypoints have FL370 again. The first waypoint of the STAR has a constraint of 280/FL190B. The second waypoint has a speed 250kts constraint but no altitude, and the CRJ thinks it should be at FL370 there. Like, what is going on with the VNAV calculations in this plane? I actually double checked this again while writing, and it does it by default! It was not me screwing anything up with the secondary flightplan. At this point I just use my own personal VNAV (brain) and plan my descent. Approach is set in the FMS, I create a base leg from ADINI to WA533 as that is what ATC will usually give you in Warsaw when coming from this direction. Just past ADINI and on the base leg I activate APPR mode for NAV-to-NAV functionality. It instantly captures GS even though I am 90 degrees off the final track and the localizer is not even captured, why is this possible? LOC1 is green shortly after, still 90 degrees off track. It again does not switch to green needles. It never actually captures the real GS and just continues with a steady 1200fpm to the ground... And why is the ALTS CAP FMA still missing? Why is the flap limit speed for flap 20 on the CRJ900 still incorrect on the airspeed limit placard? It should be 220, not 230, I reported this back in the CRJ X beta even all those years ago and it should be such an easy fix as it is correct in the system logic.. so just a texture change. Why does the MDA have a leading zero when less than 1000 is selected? Why does VNAV on the MFD indicates the required flightlevel to be at as F380 instead of FL380? The only place a format like F380 is used is as input in the FMS. Why can't I delete an altidude/speed constraint at a waypoint? It is something we use daily. Why does it still have trouble with turn anticipation? I'm sorry, but this product does not deserve the tag Professional. If after these years, even basic functionality like LNAV, VNAV and approach captures are not able to be 99% reliable... I am truly sorry mr. Hartmann, but you need some help getting this addon to a point where it fully deserves to be called Professional and where it is fully worth the asking price of €75. Video demonstrating the weird VNAV calculations, I go through a quick FMS setup and from 2:37 you can see me setting up performance and VNAV and showing the LEGS page after. This was me double checking, not during the actual flight, so it is reproduceable: Screenshot showing the GS capture on base leg before LOC capture: Video of the plane telling me it is fully stabilized on the ILS while basically flying into the ground: Image showing that MDA does not have a leading zero when less than 1000 is selected: The flap speed difference you should be able to easily confirm yourself by checking QRH Vol.1 Speed Limitations for CRJ700 and comparing to the one for CRJ900. But as it is already correct in the system logic I am assuming you know.
  5. 2 points
    We don't use Reallight, just Trueglass. But yes, that has been a problem. If you run trueglassinstaller.exe -beta from the command line, you automatically get the latest version of Trueglass. You can find the file in "Aerosoft CRJ Pro v5\Data\SupportFile".
  6. 2 points
  7. 2 points
    We're entering a realm that the RJ isn't supposed to be operated in, so we're finding errors that won't be explained in the books and can't reasonably be expected to be fully programmed by Hans because the info just isn't available. That being said, VNAV relies heavily on proper database data (altitudes) and will behave erratically if any of the data is inconsistent with the approach. Keep in mind you're supposed to be doing an RNAV approach with vertical guidance of some sort if you're leaving VNAV engaged. Given you're doing a VOR approach, this data is likely not available, or incompatible with the VNAV function, so its getting confused. Manual edits of approach segment altitudes effectively renders VNAV useless in the real plane. Long story short, in a real world level D sim training session, I'd be letting you go down the way you did to display to you the real mess that you've out yourself into to impress on you the importance of disabling VNAV prior to the approach. The only safe solution in real world ops from there is a go-around, or continue visual if possible.
  8. 2 points
    Fix to Version 2.0.1.0 will be available via ASupdater soon as posible now.
  9. 2 points
    IMPORTANT! PLEASE READ! v2.0 I did some more testing (= tracking and analyizing the file changes made by the QW787 installer and uninstaller) and found that the Uninstaller deletes the navigraphOIDC.dll from the Prepar3D main folder. This file is part of Navigraph's charts SDK and is installed and used by both, the QW787 and the CRJ Pro. If one of the two is uninstalled and the file gets removed, the other product is affected as well. Please note: I don't know which other add-ons make use of the navigraphOIDC.dll if there are any, they can potentially cause the same problem. So, temporary and probably only partial workaround: Please check your P3D main folder for a file named "navigraphOIDC.dll". If it's missing, unzip this file navigraphOIDC.7z into the folder and try again. If you have the file, please let me know so I can check for other things that might be missing.
  10. 2 points
    what kind of support is???
  11. 2 points
    IMPORTANT! PLEASE READ! I managed to reproduce the issue here, thanks to Bryan York from FS2Crew, who had the same problem a while ago. However in his case, it was just that he was using 2.0.0.0 and had to update to 2.0.0.3 to solve it. But before he did, he tried a lot of things and finally thought that the problem was related to uninstalling the Qualitywings 787. I didn't follow up on this because the 2.0.0.3 update seemed to sort it, but due to the fact that several of you have issues with 2.2.0.0, I gave it a try. I used the same clean installation that I used yesterday. The result was clear: Bryan's find was correct. I installed the 787, loaded the CRJ. It worked. I uninstalled the 787, loaded the CRJ - all black, yoke to the left. I reinstalled the 787 (with crash reporting active, choosing "Repair" for the VC++ 2012 runtimes), loaded the CRJ and it works again. (I repeated this several times) So, it's quite safe to say that the 787 uninstaller kills something from under the CRJ's butt that effectively kills it. Note: Uninstallers are created mainly automatically by installer software. There's NO reason to blame or bad mouth QualityWings or Flight1 for anything! This falls under the category of "shit happens". Note 2: It is not guaranteed that this only happens with the QualityWings 787. There might be other installers (Bryan suspected the PMDG installer as well, but it's not necessarily just P3D add-ons) that cause the same issue. The next step will now be to find out what has been removed that kills the CRJ and provide you with the necessary information (and may be a little installer) to revive it. I will also talk to QualityWings and Flight1 to gather more information.
  12. 1 point
    Could you also answer the second question Otto made? Did you use the v5 installer to install the bus? Also, are you able to see the sim and aircraft normally in external views? Do you use any shader software? Have you tried to reinstall the Airbus? If those steps don't work, I am afraid that you might need to try complete reinstall of the sim. This issue is something that I have never seen myself and you are the first user to report it, so unfortunately no idea what is going wrong on your side so that this is happening. Let us know if you still exprience it after going through the steps I mentioned.
  13. 1 point
    @Heinz Flichtbeil Ich hab dir im Projekt eine korrigierte Apt.dat geschickt, teste die mal bitte durch.
  14. 1 point
    Hi all, Just in case Mathijs instructions are not 100% clear (as it took me a little playing to figure it out 😊): - "Throttle (cut)" needs to be be set to button 17 with "ON RELEASE" ticked - "Throttle (decrease quickly) needs to be set to button 17 with the Repeat slider set to middle or full You also need to ensure the stick is in "Mode 2" as per the Thrustmaster manual linked by Mopperle. 👍 If you don't put the stick in "Mode 2" then you can only get to 0% throttle past the detent (button 17). Actually - now I've written this; I think the offset config option Mathijs posted is to compensate for a stick still in "Mode 1" ???? Thanks, Mike
  15. 1 point
    Kernelbase.dll crash could be a lot. Can you try it with a fresh prepar3d.cfg file and the default settings, please? Just delete the old file. Can you also please run this tool and pot the report? It will collect some basic information about the hardware the versions of the runtimes. https://forum.aerosoft.com/applications/core/interface/file/attachment.php?id=147687
  16. 1 point
    For all new versions, check here: https://forum.aerosoft.com/index.php?/forum/946-latest-releases/
  17. 1 point
    https://sode.aerosoft.com/?lang=en FOUND! You smash it Aerosoft!
  18. 1 point
    I think this is Windows problem: in the Start Menu you can not have a more than one link to the same exe.
  19. 1 point
    Hi, In this case this registration key is still available Windows + R => regedit HKEY_LOCAL_MACHINE \ SOFTWARE \ WOW6432Node \ aerosoft \ Mega Airport Oslo 2.0 - PREPAR3D V4.x This entry is normally removed from UN-Install of the previous version. You can delete this key manually if you have already carried out the UN-Install. Do not leave the "old" data in the P3DV4
  20. 1 point
    Moin , yes, the developers knows about it and we are trying to fix it .... Have fun with Zurich Greets Heinz
  21. 1 point
    Yes, the old one was removed. The link is a dead one. But in documents\aerosoft you will find a new one. And here is a update for that one: https://forum.aerosoft.com/index.php?/topic/150903-the-livery-installer-manual-or-rather-two-images/&do=findComment&comment=972166
  22. 1 point
    There are several topics on this already that have many suggestions for fixes. The most common one is that you might have installed without first disabling the anti-virus, which seems to affect the installation. Little hunting will give you many things to try
  23. This post cannot be displayed because it is in a password protected forum. Enter Password
  24. 1 point
    I'm not Dave Please check your shop account, no separate purchase if you already own the Airbus Pro series
  25. 1 point
    Hallo Harry, du hast in deiner scenery_packs.ini Datei die jeweiligen Flugplatzszenerien in einer geringeren Priorität als andere Landschaftsszenerien, weshalb die Gebäude unterdrückt werden. Deine oberen Einträge der scenery_packs.ini sehen bei dir so aus, wobei ich die zu gering priorisierten Szenerien fett hervorgehoben habe: 0 Custom Scenery/simHeaven_X-Europe-1-vfr+corr/ 1 Custom Scenery/simHeaven_X-Europe-2-regions/ 2 Custom Scenery/simHeaven_X-Europe-3-extras/ 3 Custom Scenery/simHeaven_X-Europe-4-forests/ 4 Custom Scenery/simHeaven_X-Europe-5-scenery/ 5 Custom Scenery/simHeaven_X-Europe-6-autogen/ 6 Custom Scenery/simHeaven_X-Europe-7-network/ 7 Custom Scenery/ff_library_extended_LOD/ 8 Custom Scenery/R2_Library/ 9 Custom Scenery/VFR-Objects_GK_+52+009_D_Hannover 2.0/ 10 Custom Scenery/VFR-Objects_GK_+53+008_D_Bremen_Oldenburg_2.0/ 11 Custom Scenery/X-Plane Landmarks - New York/ 12 Custom Scenery/X-Plane Landmarks - Washington DC/ 13 Custom Scenery/OpenSceneryX/ 14 Custom Scenery/X-Plane Landmarks - Dubai/ 15 Custom Scenery/AEHD_Ramps/ 16 Custom Scenery/AEHD_Taxilines/ 17 Custom Scenery/Aerosoft - EDDF Frankfurt/ 18 Custom Scenery/Aerosoft - EDLP Paderborn-Lippstadt/ 19 Custom Scenery/Aerosoft - EGLL Heathrow/ 20 Custom Scenery/Aerosoft - LFMN Nice Cote d Azur X/ 21 Custom Scenery/Aerosoft - LFPO Paris Orly/ 22 Custom Scenery/Aerosoft - LPFR Faro/ 23 Custom Scenery/Global Airports/ 24 Custom Scenery/KSEA Demo Area/ 25 Custom Scenery/LOWI Demo Area/ Du solltest diese Einträge in der scenery_packs.ini Datei über die sonstigen Szenerien einordnen. Es müsste dann ca. so aussehen: 0 Custom Scenery/Aerosoft - EDDF Frankfurt/ 1 Custom Scenery/Aerosoft - EDLP Paderborn-Lippstadt/ 2 Custom Scenery/Aerosoft - EGLL Heathrow/ 3 Custom Scenery/Aerosoft - LFMN Nice Cote d Azur X/ 4 Custom Scenery/Aerosoft - LFPO Paris Orly/ 5 Custom Scenery/Aerosoft - LPFR Faro/ 6 Custom Scenery/Global Airports/ 0 Custom Scenery/simHeaven_X-Europe-1-vfr+corr/ 1 Custom Scenery/simHeaven_X-Europe-2-regions/ 2 Custom Scenery/simHeaven_X-Europe-3-extras/ 3 Custom Scenery/simHeaven_X-Europe-4-forests/ 4 Custom Scenery/simHeaven_X-Europe-5-scenery/ 5 Custom Scenery/simHeaven_X-Europe-6-autogen/ 6 Custom Scenery/simHeaven_X-Europe-7-network/ 7 Custom Scenery/ff_library_extended_LOD/ 8 Custom Scenery/R2_Library/ 9 Custom Scenery/VFR-Objects_GK_+52+009_D_Hannover 2.0/ 10 Custom Scenery/VFR-Objects_GK_+53+008_D_Bremen_Oldenburg_2.0/ 11 Custom Scenery/X-Plane Landmarks - New York/ 12 Custom Scenery/X-Plane Landmarks - Washington DC/ 13 Custom Scenery/OpenSceneryX/ 14 Custom Scenery/X-Plane Landmarks - Dubai/ 15 Custom Scenery/AEHD_Ramps/ 16 Custom Scenery/AEHD_Taxilines/ 24 Custom Scenery/KSEA Demo Area/ 25 Custom Scenery/LOWI Demo Area/ Grundsätzlich sollten Flughäfen ganz nach oben, andere Overlay (Gebäude) Szenerien darunter und weitere Szenerien (wie etwa Fototexturen oder Mesh-Szenerien) ganz nach unten. Bei Librarys ist grundsätzlich egal, wo sie in der Reihenfolge stehen, da diese nur von anderen Szenerien abgerufen (verlinkt) werden. Jedoch können auch Librarys von den selben Objekten abgerufen werden und dann gewinnt auch jeweils die obere Library gegenüber einer anderen Library. Somit spielt keine Rolle, wo die Librarys im Vergleich zu anderen Szenerien in der Datei stehen, jedoch sollten die Librarys untereinander in der richtigen Reihenfolge sein, wenn sie teilweise für die gleichen Objekte zuständig sind. (Das habe ich aber bei dir nicht gesehen) Philip
  26. 1 point
    Jizaz... that was quick. Updated it. It's all fixed. Thx a lot!
  27. 1 point
    The first one enables VNAV, Second one is a placeholder right now, work in progress. 3rd one adds a tiny green line to the speed tape to let you know if you're going too slow (customer option on the real RJ) Final one is to display whether or not the speed trend magenta line displays on ground or not (customer option on the real RJ)
  28. 1 point
    Hi. Thank you very much for the good feedback. Now Poprad is being tested. Improvements were made, among which the corrected work of Windsocks. Previously, Windsocks showed only the direction of the wind. Now he is also reacting and showing the strength of the wind. In addition, made flashing light SFL landing system. Poprad sent again for testing. I hope there will be a release in late July, possibly in the first half of August.
  29. This post cannot be displayed because it is in a password protected forum. Enter Password
  30. 1 point
    Hi Hans! Glad to report that this fixed my issue as well. Thank you so so so much for your hard work trying to help us fix this. It means a ton.
  31. 1 point
    So I've uninstalled both the 787 and the CRJ. This time I turned off my anti-virus and looks like the CRJ installation went through well this time. I may decide to risk it later by installing the 787 again but will be following up on this thread to see what the root cause is
  32. 1 point
    Hi I installed the new Airbus updates for the A318-A330 for P3D4.5 .... the A318-A319 and A330 have the updated Configurator.exe but the A320-A321 hasn't … Can tell because it's missing the TCA option and the file date....as you can see in the pics below the A320-A321 is missing the option for the new TCA joystick. Thanks Rich
  33. 1 point
  34. This post cannot be displayed because it is in a password protected forum. Enter Password
  35. 1 point
  36. 1 point
    Hola Walter Esa solucion la vi, pero estoy buscando una solucion que no implique reinstalar todo desde cero, pero si no hay manera de arreglarlo habra que aplicar esa solucion. Si la version 2.0 me funcionaba perfectamente y solo se hizo desinstalar esa version e instalar la 2.2, y no funciona , ahora tampoco me funciona la version 2.0 , ya que presenta el mismo problema, no se deberia ser la solucion desinstalar el simulador completo. Pero sera la ultima opcion si quiero volar este avion. Gracias Alejandro
  37. 1 point
    Same issue for me as well. Can confirm I did the latest P3D hotfix by updating each component on its own but unfortunately it's not worth a full reinstall just to troubleshoot this aircraft.
  38. 1 point
    Thanks for the kind words. Its a bit sad more sims don't support attaching a function to a button going "Off" out of the box, as I think it is very useful in many cases (especially with 2/3-way buttons like those on the Warthog throttle). FSUIPC allows you to do so in P3D, but that is the only one I know of (hence why I made this tool). In other sims I do miss the "modifier" option you have in DCS (often I use the paddle-switch as my modifier, so all other buttons can have two functions). But then again nothing is perfect 🙂 Dave I used to do all kinds of weird sh*t in the CH Products programming interface, e.g. the driver had support for 3 modes, so all buttons could have 6 different assignments (3 modes that all had support for both an shifted/non-shifted function). Normally I would keep the same function for the buttons in all modes, and then just do something different with the axis in each mode. E.g. for DCS I used to use one of these modes to "half" my elevator/aileron input so it was more easy to air-refuel, and for FSX/P3D I used the modes to switch rudder-pedal/aileron input around, so I basically could use my (CH) yoke as a steering wheel on ground while taxing, and then shift to "normal mode" before take of. Also in this "ground mode" it would reduce my physical throttle input so even when moving the physical throttle to its full extend it would input about 30-50% of throttle, so it was more easy to dial in just the correct amount of throttle to taxi 🙂 I still have my CH Products rudder pedals, but these days I only fly with these and my Warthog HOTAS (without any special CH/Target "programming", but using this tool to get the full effect of the 2/3 way buttons). It was a bit weird to get used to fly airlines with a joystick in stead of an Yoke, but now my throttle/joystick is placed on either side of my keyboard 100% of the time. Whereas with a Yoke I had to mount/un-mount it every time I switched between flying and using the PC for other purpose - its such a drag writing software with a yoke between yourself and the keyboard 🙂
  39. 1 point
    OMG 😬 First time of my FS experience since FS 2004 I see that we need to reinstall a simulator for installing an update of addon aircraft 😨
  40. 1 point
    Nice to read David, but TBH you now have made 264 posts, but still posting in the wrong section?
  41. 1 point
    But have you ever seen an cabin done in good detail, like the Flight Deck? And have you ever seen one with passengers in them? Flying an ampty airliner around is not really how things work. All in all it just does not compute for us, the days where a captain would wals the cabin to talk to passengers is long gone.
  42. 1 point
    Hi, Is there any update on the Simbrief profiles for the smaller busses? Thank you.
  43. 1 point
    Hold your horses there, Mathijs Kok! I only meant I didn't want it in my FOV (glowing) during very specific, short but critical and possibly CPU-intensive moments of flight. You know just a simple option - click it On, click it Off with a mouse, no drama. EFB is a great tool, why would you think anybody wanted to debate that?? Thank you! PS: Lol, don't get me started about money spent on other planes - it's too late, way way too much over last 20 years, FSL or others, just pick any and name it to me.. )).
  44. 1 point
    This is an unnecessary distraction during the flight and possibly a drain of valuable resources. Thanks.
  45. 1 point
  46. 1 point
    In the meantime, this one will be pretty much suitable: Vol6-StepbyStep.pdf I also love the guide from Chuck a lot: https://www.mudspike.com/chucks-guides-fsx-p3d/ So far I have not seen any seriously good video's guiding you to use all the software has to offer.
  47. 1 point
    ... there are a few more small things to do and Turkish Airlines will be the next one of mine. Here's a little taste ...
  48. 1 point
    Hi guys! Could someone make this Brussels Airlines Bruegel livery? I have all icons liveries and I just miss this one..
  49. 1 point
    Zürich v3 might be in development, but Zürich v2 is available and works in P3D v4. I guess he was referring to that. Some people don't care about the newest version as long as they got "something that works". From that point of view, Zürich V3 isn't really needed. V2 can do the job. Just like Munich which is covered by Taxi2Gate, several other German airports are already covered by other developers (non-Aerosoft). For example Bremen (FSDG), Dresden (JustSim), Düsseldorf (JustSim), Leipzig (Digital Design), Magdeburg (29Palms) and Nürnberg (29Palms). The quality varies a bit, but some of these are really good. Of course it leaves to be wished for, development takes time. Just look at the Canary Islands and how long it took SimWings to fulfill their promise to do a new version of all of them. How long ago did they make that promise? They're still not finished. And such a promise was never made for the German airports. Some of them are available and that's a good thing, but it's not something to count on. Just a bonus.
  50. 1 point
    Hi there, I want to request for a livery of the new scoot A320Neo/ 9V-TNA. Here is some pics to help! Of course the default reg is replaced with the reg, 9V-TNA. Thanks! Also, at the front, under the cockpit windows, there is a name, "Chapati Party"


  • Newsletter

    Want to keep up to date with all our latest news and information?
    Sign Up
×
×
  • Create New...