Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. I have also had these errors on a CL650 crash.
  3. HI guys, I am aware that the Collins Proline joystick can be used for manipulating the Charts, but does anyone know of uses for the vectors it can draw on the MFD - see screen shot? Thanks
  4. Today
  5. I have recently been getting the x plane log filling up with FMOD errors when flying the current update of the challenger -like below ,but many more 0:04:07.079 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.100 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.116 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.131 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.146 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.160 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.175 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.191 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.207 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.223 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.237 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.252 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.267 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.282 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.297 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.311 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.326 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.340 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.355 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel. 0:04:07.369 E/FMOD: C:/jenkins/design-triggered/source_code/app/X-Plane-f/../../engine/sound/soun_fmod.cpp(144): FMOD error 2 - Error trying to allocate a channel Is this connected to the challenger or is it coming from something else? Its only there when the C650 is loaded... any help appreciated Bill P
  6. Hi- as in the title, the sim consistently CTDs when passengers board. Any help please? Didn't happen prior to installing 1.6.1. Log attached. Log.txt
  7. Hi Ben, Affirm... - I tested the TBM900 on my test system with XP11.55 installed and no problems there. Finally managed to get the version registered there and it now loads fine. Thanks a lot. Bernd
  8. Yesterday
  9. Abishai

    SR20 g6?

    Hi I couldn't find this info anywhere. is the sr20 g1000 a g6? and what other information would I input in the attached screenshot?
  10. Makes absolute sense! Thank you, Pils for this explanation and enlightening insights. I was not aware of the degree of "intelligence" this plane demonstrates.... It is very rare that I touch the date settings when starting a flight, unless I need to see snow and ice.... However it seems not to be possible to update the date after loading a saved state and changing it in the flight settings to save it then. I have tried, but when resuming nothing changed (probably why it is called "resume"...). But also a "start new flight" after changing the date AND location did not get rid of the MARCH indication. It seems I have to restart the whole procedure and use today´s date, then save a few states for backup purposes, like Cold and Dark, APU running, ready for engine start etc.pp. Again, thank you for your help, Pils, and have a great weekend with family and friends. Cheers Juergen
  11. Thanks. Data of the day are back this morning...
  12. Last week
  13. In the sim it’s primarily used as a staging location for the newest database to be activated as the primary, in-use database (“active data base”). Under the hood there’ll always be two databases available; one is the default nav data that comes with X-Plane (which changes when Laminar pushes new major versions of the simulator), the other is the content of your custom data directory, where third-party nav data is installed, e.g. from Navigraph. The CHK DATA BASE DATES message is showing (and the database date range text is in yellow) because your sim’s date is outside of the valid range for the nav data cycle that’s active. As you can see your sim is set to the 22nd of March (“DATE”).
  14. Hi Pils, I tried command but also didn't do anything on these specific buttons?
  15. Sorry, but I thought the secondary data base is actually the one used by the FMS, and my Flightplan is based on 2206, so I guess they should be the same, right? And then wat does the request to check the dates mean, please? Thank you for some more detail, Pils....
  16. You can’t. Only active is updatable to cycle between the two.
  17. I’ll ask the developer but can you use commands instead? The raw datarefs are more for driving the animations.
  18. I found this thread when searching for the title and could in the meantime update my AIRAC circle to 2206. I was able to copy the line from LSK2L to the scratch pad and then into LSK3L. However when trying to paste that data back into the scratch pad and from there into LK3L I get an error "INVALID ENTRY" followed by "CHK DATA BASE DATES", see screenshots attached... What should I do to update the line for the secondary data base LSK3L? I am turning in circles at the moment...
  19. Hi, I'm trying to finish my hardware CCPs and I have all buttons working except the zoom (+ & -) and Mem 1,2 & 3 buttons. Using the dataref tool I can see that these are classed as non writable and all other buttons are writable so I presuming this is why I cannot operate them. Q1. Will this be the reason? Q2. Is there a way round it? Q3. Could they be made writable? (if indeed this is the issue?) Any help or guidance appreciated. Screenshot below of mem1 dataref vs lwr_menu dataref.
  20. So far I haven't had any issues after unbinding the speedbrake axis to one of my throttle levers. I will leave it that way and manually control the speedbrake from within the sim. If the problem comes up again I will try the joystick shake.
  21. https://www.pilots.shop/Cms/Ui/Pages/Products/MainPage.aspx?id=253b8b5c-0a91-4935-8d01-b3c70aee6034
  22. Hello, Today, FSGRW is stuck on yesterday's data (2022/06/30, 23:58 Z) Do people here have the same issue ? I could not find anywhere the website of the editor...
  23. @skiselkov I tested again today with latest version. But now I get this at ILS approaches (only). But now I get this (at the IF). This is ILS24Y @ EHRD but it happens at all ILS approaches at EHRD and EHEH. RNAV and VOR approaches are OK. I also flew it, but it follows the approach as depicted. I use the latest AIRAC
  24. Ok I've figured it out. I had started my flight using the mouse to manipulate the yoke for takeoff for speed (my joystick was plugged in just out of reach), and of course when you let go of it, it stays where it is. When the A/P was engaged it was fighting the yoke position. I wiggled my joystick, which unstuck it, and my passengers have stopped barfing. Cleanup on aisle 2 please.
  25. Log attached. The only extra plugin that I have is the one for DataRefs; I tried disabling that but the problem persists. No other "weird settings" or custom scenery; it's a stock-standard X-Plane install - no additional scenery - and only 1 other aircraft in addition to the TBM. TBM900_Log.txt
  26. I have the same issue. No apparent binding problems. No weather engine, standard day.
  27. N.B. it's regarding cockpit instruments etc. The view appears to be forward with no display
  28. Please see photos. I have update to 1.4.0 and now there doesn't appear to be any internal views. Brian
  29. Haha yes fair enough! All down to Saso and Goran - I just fly it around looking for bugs! I'll see what I can do myself, I'm away now until mid-July but I'll crack on with something then for sure. Have a good one!
  1. Load more activity
×
×
  • Create New...