Jump to content

daemotron

Members
  • Posts

    235
  • Joined

  • Last visited

  • Days Won

    6

Everything posted by daemotron

  1. Each development team will assess the risk involved releasing an aircraft for a not yet final release of X-Plane (as I see it, XP11 wasn't even close to stable before 11.10; a lot of aircraft had to be adapted after Austin had some fun with the free shaft turboprop engine model, setting them... uhm, well, on fire ). Depending on the complexity of the aircraft, the team's aspiration in terms of perfection, realism etc., the team's capacity to manage early-access issues, the (perceived) evaluation of XP12's stability and maturity, and probably many more factors, the development teams may come to different conclusions as to when is the right moment to update, upgrade or refurbish their products. Also bear in mind that some developers have already been involved in XP12 since the days of the first alpha builds, and others just started their familiarization journey with the public EA. And that's perfectly ok - IMO each team should only release if they feel comfortable doing so. Anything else just leads to inappropriate expectations, misunderstandings, and disappointment on customer side, and/or burned-out and frustrated developers on the other side.
  2. Thank you, Ilias, that's great news - the Sundowner v2 is a superb aircraft, looking very much forward to do some cloud-dodging in XP12 And a huge thanks for the G500 retrofit; this looks to be an awesome panel!
  3. That crash is happening on Windows, not Mac, so I think this is something else going on here. In particular since I only deactivated (moved) the rsg_g500 plugin folder but kept the OpenGPWS one. Unfortunately, those crashes are "hard" CTDs, i.e., the log is just ending abruptly, and also XP doesn't generate a crash dump in those cases - doesn't make it any easier to figure out what's happening. Only correlation I could find up to now is the combination of startup location and the G500 plugin. Now what's interesting is that I can load the Cessna 172 with G500 on those spots without producing a CTD (which also uses both plugins, G500 and OpenGPWS). Conclusively, it must be something in the interaction between the G500 and the MU-2B which causes this crash. If I can obtain a log or crash dump, I'll upload them here. P.S. another observation: this crash only happens if loading the MU directly after starting X-Plane, i.e., loading it from the "Start new flight" screen. If I load the C172 first in such a spot, and then switch to the MU, it doesn't crash. P.P.S. the OpenGPWS crash on unload (known for Mac iirc) also happens on Windows (cf. attached log and crash report). crash_report_11_13_2022_07_44_53.rpt Log.txt
  4. Observed in the 5 Blade GNS model - as the title says, the clock's display remains dark (button backlights do work though). From the information available at https://www.davtron.com/product-detail.php?M877-17, I couldn't really figure out whether the A models (grey face plate) do have a lit display or not, but in the general feature description it says things like "BRIGHT SULIGHT READABLE DISPLAY" and "AUTOMATIC DIMMING", so I'm assuming also the display of the A model would be somehow readable at night.
  5. There's a thread on XP12 progress over in the general discussion area:
  6. I use the "Save control positions on exit" option with the MU2, but I noticed the parking brake lever's position is not saved - it always defaults to OFF. I even have a two way switch assigned to xscenery/mu2b60/set_parking_brake (resp. xscenery/mu2b60/release_parking_brake). I usually keep it in the SET position when shutting down the sim, but when I reload (with the switch in the SET position), the parking brake still defaults to OFF - a bit of an issue if the MU loads in a spot that's not perfectly level. Would it be possible to either save the state of the parking brake lever with the other controls, and restore it, or alternatively initialize the parking brake in the ON position?
  7. Can confirm now it's at least related to the G500 plugin. I deactivated it (moved it out of the plugins folder and into plugins_deactivated), and the MU loads without crashing.
  8. Fresh attempt - I reset all Mu-related configuration files and deactivated the RXP GTNs. Now I could start it. Weird, but *shrug* In return, I found another issue - the MU seems to be sensitive with regards to where it's loaded. Example: when I try loading it at CYYR (11.55 default scenery) ramp position 38, it CTDs a few seconds after having been loaded. At ramp position 40, no issues. (also with the RXP GTNs deactivated). My suspicion: it could be the G500 plugin (which loads in the background, no matter which version of the MU you actually load in sim) - position 40 is on a fake tarmac, not a real taxiway tarmac.
  9. The 5 blade GNS version seems to have an issue with engine management: the yellow ignition light doesn't come up when trying to start engines (exactly following the checklist) engines can be started through the menu though (Shift+Ctrl+e) if started this way, props don't come off the locks when trying to unlock them The 5 blade glass version works completely normal; engines can be started, and props unlocked after start. Any ideas?
  10. The numbers are a bit off, but not that much. My POH recommends 72% torque for a cruise altitude of 24,000 ft (ISA), which should result in 193 - 205 kt CAS (depending on weight). In your screenshot it looks as if you were temperature-limited on the engines and therefore could not reach the recommended torque - ending up at 165 kt IAS with less than 60% of torque seems about right, or even a bit fast when comparing to the POH numbers.
  11. Cooper already confirmed he'll update the G500 plugin for XP12, but a bit further down towards a more stable version of X-Plane. Also Tom and Cameron both confirmed there will be an XP12 version of the Moo, so all we have to do is being patient and wait - XP12 won't be a beta forever
  12. Observed in the 5 blade glass variant, version 2.0.4: from outside, the glass looks as if it weren't there: When looking from a different angle, it's obvious the glass object must be there however: To me it appears as if there's something going on with the tinting or reflection of the glass, but it could also simply be my dreadful eyesight ^^
  13. I have played with the GTN configuration to see if I can improve the integration with the G500 to a similar level we see in the BN-2 Islander. So far I managed to see the whole flight plan from the GTN drawn in the G500 by modifying the RealityXP.GTN.ini file: [GTN_750_1] ... stuff that's been there already ... MasterDevice = true LinkHsi = true LinkCrs = false LinkObs = false LinkVor = false LinkOto = true LinkSimGps = true AutoNavGps = true AutoCdiSrc = true What doesn't work yet is having the CDI show the correct course (LinkCrs didn't work, nor did LinkObs, so there must be something else). While the GTN is in GPS mode, the G500 blocks the course selector, so it also can't be adjusted manually by the pilot. Maybe @Coop could point us in the right direction here.
  14. The current stable SDK is v3.0.3, which fits with 11.5x. There is also a beta version of the v4.0 SDK available (cf. https://developer.x-plane.com/sdk/plugin-sdk-downloads/), which is the one fitting for 12.0. The API documentation is however not yet updated to incorporate all the XPLM400 changes. So in short, if a plugin builds without issues against the XPLM400 API, there's a good chance it will simply work without problems. If it fails to build and the reasons aren't obvious, it'll depend on the developer's patience digging into the header files and resorting to try & error troubleshooting. In both cases though chances are that SDK changes down the road entail further changes to the plugin code.
  15. All custom commands are documented here: https://www.togasim.com/mu2docs/setup/mu2_commands.html
  16. I don't know anything about those FAA parts (I'm EASA regulated ), and "study level" can really mean anything and nothing. I mean, as an example, is it important to simulate fuel sampling and oil quantity checks on a small piston aircraft, 'cause that's what pilots have to do in reality? Or is your focus on flight dynamics and avionics? Where to draw the line? I went with a selection of aircraft that I consider "study level" because they require studying how the real thing works, and are also built in a somewhat instructive way. I would never consider a model "study level" if it doesn't come with documentation (or documentation is otherwise publicly available) - how should I study if I can't find the required documents (POH, FCOM, FCTM, ...)? I'm trying to match your set of categories with my favorites: Small aircraft for private pilots and flight schools: The AirFoilLabs Cessna 172 NG makes an excellent model for flight students - though I'm still waiting for the analog panel they announced The Torquesim Cirrus SR22 is IMO the best high power piston aircraft model out there - particularly the version with Entegra avionics is superb. Personally, I prefer the TN over the normally aspirated engine, since managing a TN engine correctly (which TS models pretty accurately) IMO is a great experience and additional stuff to learn. Light twins (multi-engine trainers and hobbyists): IMO not covered. There's a load of excellent models out there (Aerobask's DA62, Torquesim's Islander), but I wouldn't categorize them as study level. Medium sized aircraft for charter ops or corporate transport: The TOGA Mitsubishi Mu-2B Marquise (v2) is my favorite turboprop - it's a quirky beast, so IMO a lot more interesting than the "boring" TBM (though that's an excellent aircraft model as well, just not as exciting as the Moo). You can learn a bunch about roll control and roll trim flying this aircraft, and it will savagely punish pilots flying uncoordinated turns. Light business jets IMO not covered yet by something deserving the term "study level". I suppose TS will change that with their Citation II, but it's not available yet Heavy business jets HotStart Challenger 650, no doubt. It might get a strong contender with the upcoming Aerobask Falcon 8x, but absolutely not sure there. Airliners IMO none atm. Many models out there get certain aspects right, but I don't see a model that actually integrates all aspects properly. As a compromise, I'll list my favorite airliners which I consider close to study level: Regional: FlyJSim Dash-8 Q400 Domestic: ToLISS Airbus A321 Twin Aisle: iniSimulations Airbus A300 Intercontinental: Felis Boeing 747-200
  17. It was included up to v10 - in 11, Laminar had it removed already. P. S. for anyone starting to dip their toes into creating aircraft, before going with the big bazookas (Gizmo, SASL) why not do your first steps with xLua (or xtLua)? Sure it's less powerful, but also simpler and easier to get into the absolute basics.
  18. Laminar based their new windscreen effects on the pioneering work Saso has done with librain. In one of the interviews Austin (or Ben?) gave a few details, and it sounded to me like they used his open-source implementation, adapted it to Vulkan, and embedded it within their rendering chain. One of the improvements pointed out in that interview was that now it was embedded, it could make use of all physics data, including prop wash etc. to natively couple effects with XP's physics calculations.
  19. When flying the OEM version (or any other aircraft with radio navigation and without GPS), I use a simple pencil/paper route plan. Usually I use Skyvector (and Navigraph charts for departure and arrival) to establish the route. Then I simply note down all segments of the route on a piece of paper, using my own shortcuts. In flight, I just follow the instructions I wrote down. Here's an example of a route plan for the route EGLC/EGGD: route: EGLC/09 CPT6U CPT CPT1B EGGD/BRI.I09 transcript: dep RWY 09 92° clb 520+ until ILST 111.15 D+1 int BPK 117.5 329° in int BPK 117.5 272° out D+26 trk HEN 433.5 int CPT 114.35 225° in int CPT 114.35 274° out D+32.4 trk BRI 414 @ FL070 hdg 278° IBON 110.15 D+8 trn left 107° int IBON 110.15 87° intc @ 2,500' dep = depart int = intercept trk = track hdg = fly heading trn = turn This way I can break down a flight plan with SID, STAR and IAP into 10 lines with simple instructions. I find it easier to have all frequencies and courses noted down and ready at hand. Theoretically a fully fledged LIDO format plan would deliver the same information (plus a lot more), but for me it's harder to extract those bits from a bunch of paper sheets.
  20. I'm aware this would break with how the aircraft is in reality, but for simmers not using VR it's impossible to quickly glance down at the roll trim indicator without losing situational awareness. The time it takes to pan the camera down, adjust trim and look back, is usually sufficient to have gone off course when hand-flying, and/or even banking to 45° and more. Having the little wing position indicator replicated somewhere in the pilot's FOV on the instrument panel would immensely help trimming the aircraft. I have no problems with rudder and elevator trim, but a wrong (even a neutral) roll trim setting can nearly flip you over at low speeds and high power setting. That being said, if someone has a technique how to deal with that in sim (with a non-force-feedback yoke), I'd love to hear how it could be done without referring to the indicator.
  21. Do you have a hardware switch bound to avionics on/off? If so, this hardware switch cuts the avionics bus, leaving those devices unpowered. The Honeycomb Alpha is prone for this (avionics bus 1 switch is bound to this by default). Solution: unbind this switch and reload the aircraft.
  22. For me it doesn't freeze entirely, but drops to ~1 FPS when trying to cruise in the flight levels (flying at lower altitude in the same area didn't cause any issue). Seems though that only XP's main thread gets clogged, the displays still update. I can reproduce it by loading at Nantucket (using the iBlueYonder scenery that was sold at X-A for a while, but seems to have gone from the store), climbing out and heading for the LGA VOR at FL340. Flying the other way from the main land towards Nantucket Island at 17,000' doesn't create any problem. This makes me wonder if it is perhaps triggered when a scenery with custom mesh is unloaded when leaving the area. I also looked at the performance view in the plugin admin. When the issue starts, it's first X-Plane itself that goes up to ridiculously high frame times (~500,000us). Slowly the other plugins start following suit, until the Challenger reaches ~250,000us - I'm assuming this is rather a consequence of the first rather than the root cause. I have tried with both, unlimited worker threads, and a limit of 24 (my sim rig has 16 physical / 32 virtual cores). On the ground I get between 50 and 60 FPS with the Challenger (using pretty high rendering settings). When the problem occurs, FPS drop to 1.1 - 1.3 FPS, driven by CPU time. Only one CPU core then is running under full load (and with boosted clock rate), the others are (pretty) idle and run with throttled clock rate. I let the system sitting for half an hour to see if it recovers by itself, but no luck, so I had to close X-Plane (I could initiate a normal shutdown through the menu, but its very tough to navigate the menu at 1 FPS). I don't have the AlpilotX mesh, but of course a lot of airport sceneries bring their own tile nowadays. The only things I can try is the SAM integration for Traffic Global - must test that tomorrow (not sure what it was set to), and a worker limit below 16. Log.txt
  23. I found that I can cover (nearly) all Linux users by providing one build for the Ubuntu and one for the Arch Linux distribution family. Unfortunately I haven't found a way yet to create a build catering to both, Ubuntu and Arch based distributions (experience gathered with the FSEconomy client). With the M1 architecture, Mac also adds an additional required build, bringing the total up to 5 builds (Win, Intel Mac, M1 Mac, Ubuntu, Arch).
  24. Do you by chance have a hardware switch bound to the default avionics on/off command? I ran into this on my first attempt...
  25. Some impressions from this morning's flight (EGLC - EGGD) - this time in the 4 blade OEM version:
×
×
  • Create New...