Jump to content

Gilbnx

Members
  • Posts

    36
  • Joined

  • Last visited

Everything posted by Gilbnx

  1. Update 2: the stuttering came back quite severely 1 hour into the flight. Fps is dropping occasionally to 10-15fps from 44-55fps. I see that MainThread is the culprit and the GPU is not as busy. 😞
  2. An Update: I completely removed the installation I've done with Aerosoft One and reinstalled the build directly from the store. Replaying the flight (no other changes done to the sim or the computer) and now I get no noise stuttering and the performance remains high. Not sure what happened before but I'll avoid using the Aerosoft One in the future...
  3. Hi, I didn't fly the CRJ for a couple of months, yesterday I decided to get back to it, used Aerosoft one to get the latest update (I believe .15) and since then, I'm getting severe stuttered sound in the cockpit... I get a steady 40-50fps and suddenly I drop to 10-15fps and the cockpit sound starts to severely stutter, then jump back to 45-50fps.. this is constant throughout the flight. I also see that sometimes get this stutter even with a high fps (40fps or so) so it must be something else. It gets worse if I move the cockpit cam around to look at the pedestal, overhead gauges, etc. Did anyone have the same issue? Is there a way to resolve? I don't believe I have done anything unusual besides tweaking with the VR graphics settings yesterday (I'm not flying VR now) but even then, the GPU usage is low and fps is OK. Just to add as I'm still flying, it seems that only the audio is stuttering, and the rest performs well... very strange..
  4. Hi, Wonder if anyone was able to fly in VR with VR controllers? I see that I can turn on/off switches but multi-position switches only work in one direction for me...
  5. Please disregard. VR controllers are not working with twisting knobs in other aircrafts like FBW. Not an Aerosoft/CRJ issue. We'll have to wait a bit longer to have a real support for VR controllers. I guess that was an Alpha release from Asobo,
  6. Ok, I think I figured the 2nd screen (2nd picture) and why the time looks odd. I assume that "ETD" stands for Estimated Time of Departure in minutes from current time! Not sure if it supposed to be this way but if I enter 00:10, this means 10min from current time, and it will show the correct value. STILL, there is a bug that ETA is not rolling back to 00:00 after 23:59 ... it will keep going up and hence the strange value in ETA.
  7. Got it. Going to try another flight now and see how it goes. What is weird is - I was able to steer normally before take off and I didn't change anything during flight. Once I landed, I could not steer. Whatever assisted settings were the same...
  8. I did not and will check but if there was any settings changes, wouldn't it affect also taxing out (to the runway before take off)? It worked well before take off but could not steer it after landing... BTW, I do have "Piloting" set to HARD so, not sure what the Assisted Yoke was set to (I'm away from the sim right now) but I would assume it should be OK?
  9. Just landed and I can't steer the aircraft off the runway. The N/W steer is on and the nose steering wheel is moving left and right when looking from the outside, but the plane is proceeding straight. Steering was OK before take off and the landing was relatively smooth... Is that a potentially SU7 issue or the latest CRJ550/700 update?
  10. Hi, I'm looking for some help from you professional pilots out there. In the FMS I am trying to set things right to get an accurate ETA and range calculations. However, I either get erroneous readings or none at all. Please look at the below two screens. What am I missing to get the correct reading? First screen shows no values for time/rage to Reserve fuel amount Second screen shows ETA with an erroneous reading (The hour shows 42:33 ??) It is the same as the previous version and since it behaves in the same way, I assume its not a bug but something I'm entering wrong (or not entering) during the FMS setup...
  11. Hi, just downloaded SU7 and all other updates (including the latest CRJ550) and found that controllers support is an issue. First, in order to use controllers, I have to be on "Lock" mode and not "Legacy". Switches are working but knobs twisting and multi-position buttons are not turning. I'm using Oculus Quest 2. Any idea if there are any workarounds and when a support for VR controllers will be avail? VR is what holding me now from moving from XP11 to really enjoy MSFS in a fully immersive environment... Thanks, Gil.
  12. Completely agree. An amazing aircraft so far and yes, I assume more fixes will come as we move forward. Besides, the airplane keeps us pilots at the tip of our toes during those regional hops and I find it exciting. I am mixing wide-body, mostly automated flights with CRJ flights and its fun!
  13. Hi, I tried your method and it worked. The only issue is that it took the A/P NAV off for some reason, I had to re-engage it...
  14. Thank you @KuntaKinte ! Will try it in next flight.
  15. Got it. Not trying to beat this dead horse and I will accept whatever implementation it is (the CRJ is an awesome plane as it is and I love it regardless). IRL, will the CRJ's FMS inject *ALL* the STAR points from the beginning of the STAR's transition after your current position/waypoint just because you have changed a runway? I would be surprised if it did but if it does in real life.. OK.
  16. Is there a way to see the DME to a NAV1/NAV2 when I set the respective "bearing" in the PFD? (meaning: Staying with NAV source of FMS1 so I can use NAV per my plan but seeing the distance to NAV1 when I select it as bearing) If it's not possible in the CRJ, what usually IRL pilots do to get that distance? Thanks.
  17. That's my point. I was below FL100 on the last few waypoints on my STAR, I have changed from 25L to 25R in KLAX per ATC request and my STAR got updated as if I approaching its initial waypoint. Airplane started to turn back. Yes I corrected it but workload exists in that phase and I had to scroll down the CDU to find and select the direct to...
  18. All that is fine but flying on other aircrafts (the B738, Zibo, I think also the A350), while the pilot SHOULD take control on NAV while making changes, the CDU through the FMS on other planes did not add waypoints already passed and in the opposite direction. There is probably a logic for that in the actual airplane to avoid that. Would be good to hear from an actual, IRL CRJ pilot... is changing runway (not changing a STAR) re-injecting the whole STAR plus the new runway procedure with every change? I'd be surprised if it does.
  19. I guess it makes sense. That reminds me that on the A350 (X-plane), you actually get a message in the CDU asking to use track before the CDU will allow you to Exec a change... Well, I will follow that. STILL, it will be nice if the CDU/FMS will realize what is my next fix and will only inject changes post that fix to accommodate a change.
  20. Yeah... As a "workaround" I am activating Heading before the change, then check for duplicates and back to Nav... Just hope we could switch runways without that workaround
  21. Hi, Many times when flying into busy airports with VATSIM, ATC might inform me to "expect RWY 25L" or "expect 25R" when I'm already flying my STAR and with possibly a different runway programmed in. This is all good but when I go into DEP/ARR page and update the runway, clicking Exec will also enter the whole STAR into the FPLAN (which causes next waypoint to be something I already passed) confusing the FMS. What is the correct way to update an approach to a specific runway when I'm already started flying the STAR? Thanks.
  22. Hi, (might need to be moved to another forum but not sure to where 🙂 ) This might be a known issue already but I am using the fix page to set an estimated TOD (rule of 3) but I have noticed that though the FIX (named CLOWD) is on my descent, at about 190-200 miles from my location, the FIX page shows a distance of 935nm(!) Please see image attached (you will see the distance ring on the PFD which is clearly closer than 320nm, FIX page shows 935nm) [BTW, I'm reporting those issues to make the CRJ better but regardless - the best aircraft I've flown so far, excluding Zibo in XP11]
  23. Hmmm.. I think the issue is slightly different from what I thought I am on another flight now, level at FL360 and trying to do the Mach-to-knots-to-Mach to reset the bug speed but this time, when I click on Mach-to-speed, the bug itself jumps down a bit (from 260kias to 240kias for example). The bug should not change location when I switch from Mach to knots, am I right? Clicking again from knots-to-Mach, the bug jumps up again... So I'm not sure what's going on and if that's an unrelated bug?... I don't have a good tool to capture a quick video but I took two images without twisting the speed knob, just switching between Mach to knots, you can see the difference in location
  24. I believe it's exactly what you have described. I've seen VATSIM maps keep reporting me flying FL380 (MSFS reporting 38,200ft) where my alt is set to FL370. Other aircrafts (guessing xPlane, FSX? based on aircrafts models) were reporting close to FL370. Luckily controllers get the transponder alt reporting which will still show FL370 in this case. And yes, I checked yesterday - on a straight and level flight, at FL400, I saw that "refreshing" the bug value (switching to knots and back to Mach) kept getting different values throughout the cruising period due to change in local atmospheric pressure
×
×
  • Create New...