Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/16/21 in all areas

  1. I don't really think anyone's complaining, you're not the only one who knows how to wait a bit... others have don't that in their lives too (Shocking). Were talking about all we really can talk about now, a potential release date or when news will come. We are all still optimistic (some cautiously) about the project, but talking about what we can. We know developing an aircraft takes time, that's not new information, and everyone here would rather a bug free aircraft on launch. A little conversation even speculation is better than letting the thread die, you're not really onto something.
    3 points
  2. It's kind of funny that the same people complaining are the same people returning to see if there's any news on a sooner release date. Just think when it's released, whether it's this year or 2022, everyone will have something new to complain about. I've waited months of a product that was supposed to be in stock in a week, already having paid thousands of dollars. I knew better and they did tell me that it may take much longer, but kept me in the look and provided me with options if I wanted to continue. That being said, I received it 90 days later and have been thoroughly impressed with the product and their service. This "aircraft" is a software add-on for our entertainment value. It will be released when it is ready and we all know there are a lot of moving parts to it. Heck, people complain about Free-ware a lot! Anyway, I have my own complaints and issues, and I believe the team is doing the right thing. We are very fortunate to even have these forums and even have the development team chime in from time to time. Yes, I am anxious to "fly" it and feel frustrated at times like the rest of us. But going forward the majority of the users/pilots will be very happy with it; whenever that may be.
    3 points
  3. Hi Rastislav! On Monday, I will be sending the archives. The scenery will be tested. I may need to edit something. These organizational and preparatory nuances will take some time. It should be borne in mind that apart from me, Aerosoft has a lot of its own tasks. I hope there won't be a long break before the release of Bratislavа Project name? Apparently, the name of the project will be: "Bratislava. Štefánik Airport" As soon as everything is ready for release, I will be the first to report it here on the forum
    2 points
  4. Hello friends. Aside from the real-world stuff and other flightsim things, I have been busy with another major project of mine. This is Boeing 737NG and Boeing 777 accurate aircraft cockpit configs for PMDG and iFly models. I have been doing this since 2015 in personal purposes, and for the Ukrainian flightsim community since 2017. Now, with the experience, deep research and understanding, I decided to do all the airline operators of the world in order to increase the quality of flight simming. Many popular airlines like Ryanair, Emirates, Norwegian are already done with many more to come. Please note that the fleet list is valid as at the revision date. I'll try to keep it up-to-date as much as possible. Please read the installation and use the manual for more details. Of course, your help will be highly appreciated should you be interested in helping. Feel free to contact me via the email flyprecisely(at)hotmail.com or Telegram @Mykyta_D regarding the project. And I would like to say a big thank you to all the people who have already contributed this project with the information about the airlines and configs. Please share this information on your resources and with your friends and colleagues. Boeing 747, 757, 767, and 787 are also planned, but only after subject types are complete. Keep safe and FlyPrecisely Facebook page: https://www.facebook.com/FlyPrecisely/ Links to the Google Drive. Later, I'll upload all of them to Aerosoft Forum file library. B737NG: https://drive.google.com/drive/folders/1jnj0qGGwKUH99EYq4jUz6-nD-g3xVD5D B777: https://drive.google.com/drive/u/0/folders/1aZGl-e03171NV_r_1J8FZ8pYFhWC5s7M
    1 point
  5. Sehr nett Christian! Gehen die Gesichter evtl. etwas hübscher zu machen?? Das Auge isst ja bekanntlich mit... mfg Kai
    1 point
  6. Sieht nach schlampiger Arbeit aus... ohne xEnviro müsste die Szenerie theoretisch immer zu fehlern führen, mit xEnviro könnte das auch noch passieren wenn wet geladen werden soll, außerdem scheinen die Border-Linien zu fehlen, die in der Library zu sehen sind (muss nichts bedeuten, wenn die nicht über die DSF aufgerufen werden passiert da nichts). Falls der Fix über die Library nicht funktionieren sollte versuch es mit diesem hier: (Die ursprünglichen Regionen werden im zweiten Block alle per # auskommentiert und unten bei der letzten Zeile "border_dry.lin" durch "runway_dry.lin" ersetzt weil border_dry.lin ja nicht vorhanden und runway_dry.lin ohnehin nur ein unsichtbarer Platzhalter ist.) REGION_DEFINE mega_pavement_dry REGION_RECT -180 -90 179 89 REGION_DREF env/surface < 0.5 REGION_DEFINE mega_pavement_damp REGION_RECT -180 -90 179 89 REGION_DREF env/surface >= 0.5 REGION_DREF env/surface < 2.0 REGION_DEFINE mega_pavement_wet REGION_RECT -180 -90 179 89 REGION_DREF env/surface == 2.0 REGION_DEFINE fallback REGION_ALL #REGION mega_pavement_dry #EXPORT_EXCLUDE mega/pavement.pol pavement/dry.pol #EXPORT_EXCLUDE mega/pavement_runway.lin pavement/runway_dry.lin #EXPORT_EXCLUDE mega/pavement_border.lin pavement/border_dry.lin #REGION mega_pavement_damp #EXPORT_EXCLUDE mega/pavement.pol pavement/damp.pol #EXPORT_EXCLUDE mega/pavement_runway.lin pavement/runway_dry.lin #EXPORT_EXCLUDE mega/pavement_border.lin pavement/border_dry.lin #REGION mega_pavement_wet #EXPORT_EXCLUDE mega/pavement.pol pavement/wet.pol #EXPORT_EXCLUDE mega/pavement_runway.lin pavement/runway_dry.lin #EXPORT_EXCLUDE mega/pavement_border.lin pavement/border_dry.lin REGION fallback EXPORT_EXCLUDE mega/pavement.pol pavement/dry.pol EXPORT_EXCLUDE mega/pavement_runway.lin pavement/runway_dry.lin EXPORT_EXCLUDE mega/pavement_border.lin pavement/runway_dry.lin
    1 point
  7. Das lieber Christian, sieht doch schon mal sehr gut aus. Ich bin aber auch nicht überrasch, denn alles was du machst und erstellst, schaut einfach perfekt aus. Gruß Günter
    1 point
  8. Thanks mate! I have been checking there but alas, nothing. I will forward the original and again, as always, thank you for replying. Now, enjoy your weekend!
    1 point
  9. Good morning, I hope you are doing well too! I guarantee that all emails received until yesterday have already been answered. Could you please check your spam folder? If you don't find an email there either, please write an email to me directly and I will take care of it immediately on monday! My address: marius.ellenbuerger@aerosoft.com Greetings, Marius
    1 point
  10. Dies ist ein schönes Tutorial über die Programmierung der MCDU Ich denke, das beschreibt deine Situation bedingt recht gut, bzw. untermauert das, was ich vorher gesagt habe, dass der Flugplan bis zum letzten Wegpunkt gefüllt wird, und vor Erreichen des letzten Wegpunkt der Arrival mit der gesamten Prozedur zu Ende gebracht wird. Mal anschauen
    1 point
  11. Hey, thanks for those many replies. Actually it worked today. Last time I tried, there spawned no Marshaller so the VDGs wouldn't work aswell. Thank you for your help. Traffic settings are default btw. (50)
    1 point
  12. Oh well my bad, I was talking about Prepar3D, not MSFS
    1 point
  13. Da X-Africa ja inzwischen fertig ist, ein kleiner Tagesausflug auf Lanzarote und Fuerteventura. Frühmorgens geht es los in GCRR auf der 03. Costa Teguise Im Vordergrund das Kraftwerk Central térmica de Punta Grande, an der Spitze des Spinners die Ortschaft Tahice, in der sich die Fundacion Cesar Manrique befindet. Der Künstler Cesar Manrique hat die Insel sehr positiv beeinflusst (Lanzarote-Urlauber werden das kennen), er hat auch den Mirador del Rio erschaffen, wo Timm Thaler gedreht wurde - die Älteren werden sich erinnern. Im Vordergrund Playa Honda + Gewerbegebiet, links der Flughafen. Puerto del Carmen Playa Blanca Es geht nach Fuerteventura. Rechterhand Corralejo, linkerhand das Landschaftsschutzgebiet Parque Natural de Corralejo mit seinen berühmten Sanddünen. Fuerteventuras Hauptstadt Puerto del Rosario Caleta de Fuste (rechts) und die Golfplätze mit den Häusern mittendrin (links) Costa Calma. In den Sanddünen die vielen Windräder - wie ich gelesen habe, sind die meisten davon aber wegen mangelnder Wartung inzwischen außer Betrieb. In X-Plane drehen sie sich trotzdem munter weiter 🙂. Die Playa de Jandia, mit (von links nach rechts): Iberostar Selection Fuerteventura Palace, Iberostar Playa Gaviotas, Club Aldiana (mit seiner wunderschönen Gartenanlage), Royal Palm Resort & Spa, Club Magic Life, Fuerteventura Princess, Club Jandia Princess und Robinson Club Esquinzo Playa. Morro Jable. Etwas oberhalb der Nase des Fliegers, der (ich glaube) 10stöckige Torre des Robinson Club - wenn mich nicht alles täuscht, das höchste Gebäude auf Fuerteventura.
    1 point
  14. Kommt drauf an, welchen Maßstab du anlegst. Wenn du alle Verbesserungen meinst, die X-Europe weiter aufwerten, werden das noch Jahre sein. Ich wollte eben eine Silokiste in einer Kiesgrube mal schnell ändern und entdecke dabei, dass der nebenliegende Ort Möllenbeck extremst spärlich in OSM erfasst ist. Also auch da noch mehr als 500 Häuser eingeklimpert. Das dauert aber mehr als 1 Stunde. Dann überfliege ich Espelkamp und erschrecke mich beim Anblick der Industriegebiete. Also auch da einige Vereinzelungen eingebracht, dazu eine Biogasanlage geändert ... Muss man sich mal klar machen: Per VFR geht's in 2-3000 Fuss über die X-Europe-Landschaft und trimmt parallel die X-Plane-Welt. Und das nur, weil 3D-Häuser/Bäume fehlen, Seen etwas eckig aussehen, oder hellgraue Fassadenkisten in der Landschaft stehen. Gucke gerade bei Lindern(Oldenburg) aus dem Fenster und entdecke eine Fassadenkiste ...
    1 point
  15. I know how it's supposed to work. Wind conditions will effect ground speed more than airspeed. Temperature and density altitude changes are more apt to affect airspeed than wind direction. The instability of the power setting happens only on this model and no other P3D models I have. It's a design issue. I can walk away from other non-autothrottle aircraft and while the ground speed may fluctuate, the TAS and N1/N2 power setting remains stable. I could probably live with having to ride the throttles if the other issues were addressed. But it appears the developer has abandoned support for P3D V4 and moved on to newer platforms. Version 2.2.0.0 is as good as it's going to get.
    1 point
  16. Did a quick test round in the traffic pattern at EDLP with the A32NX mod similar to what I did in the link in my previous post at Trondheim. After landing and getting clearance from ground to the stand I set as my destination the VDGS system activated as it should along with the default marshaller. After shutting down the system reverted to the default off state, showing the UTC time. As far as I can tell there shouldn't be any issues with the A320, let me know if the guidance part still doesn't activate.
    1 point
  17. Hello, here I would like to describe the LED configuration with the Honeycomb Configurator ( v2+) only for X-Plane 11. With the included Default_Throttle Profile the LED's are already preconfigured, but it can't hurt if you know how to do it... Configuration of the LED's for the landing gear. This are 3 LED's for a 3 point landing gear with nose wheel. The LED's have the letter designation on the throttle L, N, R. These LEDs can be red or green. Red = Landing gear is in motion (extending or retracting). Green = landing gear is extended no LED is on = landing gear is retracted. In the Configurator the designations for the LED's are: LDG-L_GREEN LDG-L_RED LDG-N_GREEN LDG-N_RED LDG-R_GREEN LDG-R_RED We need a X-Plane 11 Dataref in the Configurator to control the LEDs. You can find it in the Configurator function Actions - Open XPlane Variable List - Dataref (web page). The dataref variable in this case is called: sim/flightmodel2/gear/deploy_ratio This variable can take values between 0 and 1, which we now have to query. 0 means: landing gear is retracted, 1 means: landing gear is extended. Values between 0 and 1 mean: Landing gear is in motion. Let's start with LDG-L_Green: Now proceed according to the numbers at the arrows as shown in the picture. 1. Switch on LED mode. 2. Select LDG-L_GREEN (Select LED:). 3. create condition (+ sign). Enter the mentioned dataref sim/flightmodel2/gear/deploy_ratio. 4. Enter index. 0 = LED L ; 1 = LED N; 2 = LED R. 5. Enter Value: 1 = Landing gear is deployed (since we are configuring the Green LED). 6. save. We do the same for all 3 green LED's L, N, R with the matching index 0, 1 and 2. Continue with the red LED's for the landing gear. Again proceed according to the numbers. But now we now need 2 conditions (queries) for the "Value", which we have to link with AND in the condition link (3.). Value is less than 1 and Value is greater than 0, because only then the landing gear is in motion and the LED's must light up red. So for Condition 1 enter the value <1 at Value: (picture above) and for Condition 2 enter the value >0 (picture below): Again, this must be done for all 3 LEDs (L, N and R; index 0, 1 and 2). As a 2nd example, we want to query the oil pressure and display it on the annunciator panel. The LED is called ANC-OIL. The dataref is called: sim/cockpit2/annunciators/oilpressure_low Since we only have one display here for all possibly existing engines, we now need 4 conditions (for 4 engines) and the condition link "OR". With the "OR" function we make sure that the oil pressure light turns red if any of the 4 engines has too low oil pressure. If there are only 2 or only one engine, this also works if you program 4 conditions. With the + sign (next to Conditions) we create 4 conditions for 4 motors. The Index value must then run from 0 to 3 (0 = motor 1 .... 3 = motor 4). The Value field must always contain 1 (=1), which means that the query (Condition) "Oil pressure low" is true. See now the picture below for motor 1: We do this for all 4 engines (Condition 1 to 4 with index 0 to 3). One more hint: If you can't find a name on the web page for the datarefs and commands: All always current datarefs and commands can also be found in the X-Plane 11 directory "Resources/plugins/". The text files are called Commands.txt and DataRefs.txt. Addon aircraft can also have their own commands and datarefs. This must then be found somewhere in the installed addon aircraft folder. If not, then you should ask the manufacturer...... So, I hope this helps for now. Please ask questions here in the subforum with a new topic (Create new Topic). Greetings Heinz
    1 point
  18. Only a somewhat minor update: 2.04 (17 DEC 2020) ------------------ - IMPROVED MULTI-SCREEN SUPPORT - IMPROVED IVAO/VATSIM TRAFFIC VIEW - FIXED CONNECTION ISSUES - REMOVED CFMU ROUTE VALIDATION (SERVICE NO LONGER AVAILABLE) Especially happy with the last line, as it always generated three errors after computing and releasing a flight So something happened at their end, but I'm still awaiting a proper reply. If it's what most of us expect (I suppose..) which is that Christian has moved on to other business opportunities than that's fine by me too, but at least give us something. Even if it's a 'Goodbye and thank you'. @Mathijs Kok have you heard anything from Christian and/or Judith in regards to your post in this thread on December 1st? Thanks, Stefan
    1 point
  19. Well we've proved this forum isn't dead, so there's a positive. Everyone's entitled to an opinion, and a few people seem to be quite vocal in expressing theirs. I've expressed mine above, and to me this subject is akin to that favourite question of flightsim forums - "when's the release date?". Again I'm taking the positive view that PFPX works very well. What I paid for works and the developer hasn't failed to get the servers back up when they've had an outage. I got what I paid for. The developers don't owe me anything else. That's my reality.
    1 point
  20. Many people in the beta tests have found that using a controller is the easiest way to manipulate the drone and views. But what controls what is not very well explained so I made a small guide. START Toggle main menu BACK Toggle last two views used GUIDE Opens the XBOX overlay menu ------------------------------> Moving the drone LSB UP Drone move forwards LSB DOWN Drone move backwards LSB LEFT Drone move left LSB RIGHT Drone move right RT Drone move up LT Drone move down X+A Reset drone location X+LB Increase speed X+RT Decrease speed RS Toggle between free and follow mode LS Toggle lock mode ------------------------------> Pointing the drone RB Drone roll right LB Drone roll left RSB LEFT Drone rotate left RSB RIGHT Drone rotate right RSB UP Done rotate up RSB DOWN Drone rotate down X+Y Look straight down RL+LB Drone orientation reset X+LT Increase camera rotation speed X+RB Decrease camera rotation speed X+LS Target user aircraft ------------------------------> Camera settings Y+RT Zoom in Y+LT Zoom out Y+RB Exposure increase Y+LB Exposure decrease Y+LS Exposure reset B+Y Toggle depth of field mode B+RT Depth of field increase B+LT Depth of field decrease B+LS Toggle Autofocus ------------------------------> Drone autoflight A+LB Set start location A+RB Set end location A+LT Fly start to end A+RT Fly end to start
    1 point
×
×
  • Create New...