Jump to content

wakevortex

Members
  • Posts

    11
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

wakevortex's Achievements

Newbie

Newbie (1/14)

  • Collaborator Rare
  • Conversation Starter Rare
  • One Month Later
  • Dedicated Rare
  • First Post Rare

Recent Badges

2

Reputation

  1. Aircraft seems fine..no crash, just noticed these in the log...
  2. 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
  3. That indeed appears to be the issue...somehow CDU1 had got different numbers , so I used the ones for CDU3 and its back to normal no idea how that happened though as I've never touched that file..also oddly no entry for CDU2 though that appears to work normally hope that helps anyone else with this issue Bill P this is what I had cdu/1/inn/bottom = 77 cdu/1/inn/left = 358 cdu/1/inn/right = 942 cdu/1/inn/top = 639 cdu/1/open = false cdu/1/out/bottom = 480 cdu/1/out/left = 718 cdu/1/out/right = 1300 cdu/1/out/top = 1042 cdu/1/popped_out = false cdu/3/inn/bottom = 40 cdu/3/inn/left = 349 cdu/3/inn/right = 931 cdu/3/inn/top = 680 cdu/3/open = false
  4. interesting..I certainly haven't by choice...will take a look at that, but strange that I havent touched it if its now wrong somehow thanks Pils !
  5. any comments on this ? ..its still happening and I have no idea why, - many updates later both in normal screen mode AND in VR..its very odd thanks Bill P
  6. You can interact with the mouse in VR BUT only if you pop out avitab as an extra window from the plugin menu (right click in VR) , and place it where you like in the cockpit.. The built in avitab then mirrors it.. as mentioned , its an avitab limitation for all aircraft in VR , but this method works really well for me...it also means you can resize the avitab window if you need to .. ... Bill P
  7. When I use the popout FMC, as the picture shows, the screen is misaligned.. this messes up the buttons.. For example pushing DIR gives MSG , pushing A gives FPLN etc...they are all moved down by one button any ideas? Bill P
  8. That is indeed the solution... to get continuous movement on those buttons , map the standard AUTOPILOT commands, not the CL650 specific ones I did indeed have HDG already assigned to that, hence why it was working hope that helps some others Cheers Bill P
  9. Think Ive found the answer in another post ...use the default Xplane keybinds for these ...! will try that later Maybe my HDG bind WAS set to default and I hadnt spotted it :-) Bill P
  10. Hi all..I usually map things like HDG ALT SPD VS to joystick controls..( I fly in VR where turning knobs is a little hit and miss with a mouse sometimes) this works fine in the 650 BUT..only the HDG knob continues to move if the assigned joystick button is held down...all others seem to only do one click at a time.. which makes setting ALT for example a rather long process Is there something that can be changed in the config to make them behave like the HDG knob? ie hold down the button and the change in heading is continuous while held down ?. thanks ! its a BRILLIANT piece of work by the way Bill P
  11. Totally agree with the above.. I find it crucial to wait for x plane to "settle" in 2d for a moment (usually accompanied by a jump in frame rate upwards) Switching to VR too soon usually ends in a slide show.. Then I use a button to switch to VR on my yoke, and again allow that to settle before doing anything.. One other tip..if you need to come OUT of VR , I tend to then close steam VR completely before going back in, as sometimes reentering VR again produces a slide show.. works well for me ! Bill P
×
×
  • Create New...