Rene Feijen
-
Posts
65 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by Rene Feijen
-
-
SU4beta: All is now good after complete deinstall and reinstall. In fact today I am in sim heaven, Inibuilds A350 at EGBB, totally smooth takeoff and 55-60 fps, very very very smooth! No stutters while panning my head, all clear and readable in the cockpit. WOW!
Latest Nvidia driver DLSS4 3.10.3 preset K
-
41 minutes ago, Rene Feijen said:
5GB, I have no stutters except for the A350 with this fix applied
1 hour ago, ben4muk said:What's your Shader Cache set to in the NVidia Control Panel? I increased mine to 100GB in non VR and it sorted my stutters.
Set it at 100GB and now it is smooth!! Thanks!
-
1
-
-
1 hour ago, ben4muk said:
What's your Shader Cache set to in the NVidia Control Panel? I increased mine to 100GB in non VR and it sorted my stutters.
5GB, I have no stutters except for the A350 with this fix applied
-
The fix works, graphically, SU3 final release. But results in 15 fps instead of 40 fps, making it unflyable. RTX5090 VR.
-
1
-
-
I can confirm I have the same issue in SU3beta VR.
-
I had the same. I knew already of the DH speed bug, but thought it was only optical, because we could also (hope to) rely on the blue line for set speed on the speed tape. But apparently the DH bug not only prevents showing a set speed but also actually setting a speed.
-
-
After about 25 flights without taxi steering problems, today , after pushback, I could only taxi steer -after pushback stopped- to the right with my TPR pedals. (although rudder pedals and tiller in cocpit turned left) . I pressed pushback STOP again , and a bit random again pushback straight and then pushed for a turn. Then STOP again... et voila... my rudders worked again for taxi steering. My 2 cents.
-
Aha... activating the approach phase on the FMCG. Never done that before. Cant remember seeing youtubers doing that but maybe overlooked? Will try.
-
A friend on mine (living in another country) practical always has autothrottle kicking in in the approach phase. I suspect his speeds are outside limits for normal (auto)land. Now I dont have this problem. Am I right to think that I first have to select a stage of flaps, thus allowing AT in PROF mode to let the speed go down, do a next stage of flaps, etc. And not the other way around: waiting for the speed to come down (which I would say will not happen in PROF mode but in some manual speed mode), and only then selecting flaps?
Is somewhere in an SOP or FCOM described what to do in what order?
-
9 hours ago, Alexair said:
If you want more details, have a look here: https://skybrary.aero/articles/mean-aerodynamic-chord-mac
Thanks, nice to know, I have just started part 4 of my RPL MLA theoretical lessons, about Aircraft Aerodynamics and Performance.
-
1
-
-
I read in the A310 FMS Pilot's Guide:
CG is displayed as a % of MAC [?] with a default value of 25%. If a trim tank is not fitted the field displays GWCG. With a trim tank it displays ZFWCG. Entry is mandatory to initialize the trim tank computer.
I guess I will use indeed MACZFW.
PS A guess: MAC = moment of aircraft?
-
-
I had this starting to fall out of the sky but it was pilot error: I set a too high VS climb speed so the autothrottle could not manage the speed anymore, plane slowed down too much, began rolling to one side and AP disengaged. Managed within seconds to recover an engage AP again.
-
-
BTW EGCC RWY23R KUXEM1R departure went well in PROF mode with NAV armed and on takeoff HDG mode 273degr and I think it autoswitched to D8.0 MCT.
And EKCH LANGO2C departure also went flawless in PROF NAV mode.
-
I dont completely mind not to be able to AUTOLAND, but I DO mind not seeing the GS and LOC diamonds.. without them I cannot fly the ILS of course.
-
12 minutes ago, Crabby said:
I have to ask, because I can't determine from the post. Did you set the flight directors to ILS mode on the glareshield?
Yup, as always. (Now I did recycle the AP and LAND switches, but not the ILS mode selector. But... that should not be necessary in the first place). Also set on the copilot PFD and not showing the diamonds btw, as I tend to do long before I do that also on the pilot flying side.
-
1.03 Same here, no digits, but there was a moving blue line on the speed tape. All was good on 1.02.
Also on ILS landing I did not see the GS and LOC diamonds on the PFD, although LAND was armed as I could see blue G/S and LOC indications on the PFD and PFD to ILS display set. Autoland did not kick in though, in spite of complete landing config and correct approach speed. That was on EHGG OLWOF1 arrival and then via HECTI ILS RWY23 approach. This also was good on 1.02.
-
2 hours ago, Rene Feijen said:
The use of Navigraph is interesting here. I will test without it.
I did one good approach without Navigraph, and then it failed again on the SID. So seems not to depend on that. Will continue testing. Maybe.
-
1 hour ago, Crabby said:
Well, I guess I ran into something similar on departure from KGPI.
1. Addon airport
2. I use and will continue to use Navigraph in the sim
I was on the RIDDG2 departure to RIDDG. The plane flew the departure with zero issues on NAV. It was at RIDDG where I saw a hiccup. The next waypoint after RIDDG in my flight plan was ANN. My plane crossed RIDDG without turning. I corrected by using the direct to button.Now, I will say this. ATC gave a reroute during cruise and the entry of the reroute and the plane's reaction to it was spot on.
What I take away is that I have to stay ahead of the plane, as I would in any plane in real life. I do not know if my use of Navigraph caused this or if it is a bug in the LNAV. I am not going to remove Navigraph to test, so I will just monitor. This has been the only case of weird LNAV behavior that I have seen though a couple of my buddies from the VA reported similar but spurious incidents too. The commonality is we all use Navigraph.
The use of Navigraph is interesting here. I will test without it.
-
5 hours ago, kevink817 said:
Just experienced this twice in a row on a departure from OMDB - RWY 30R on the ANVI7F departure. Even with NAV mode engaged, it flew straight through DB570. I gave it a DIR TO DB587 to get it back on track. It flew the rest of the SID perfectly, but after the transition ANVIX it did not turn towards the first enroute waypoint of GIDIS. I gave it another DIR TO for VAVIM, and now it seems to be following the rest of my route correctly.
For reference, here is my complete routing: OMDB/30R ANVI7F ANVIX R401 GIDIS G783 UKRAG L710 KUKDI B400 RIGAM B403 BOMIX UB403 MAV UP312 WAV WAJI1A HKJK/JOM2C.I06
Please note that after I imported the flight plan from Simbrief I selected RWY 30L that simbrief had selected for me. I later changed the runway to 30R with the same SID.
Thanks for looking into this.
Tested that and same experience on the SID. Had to handfly first waypoint but already had second one preselected DCT so then switched to NAV mode and it works fine. As Crabby (?) said, some SIDs you have to fly first a heading by hand/HDG mode if so instructed on the SID. Now I must say, on this SID it is not in the verbal description, on some SID's that is clearly the instruction. So , not sure what real life behaviour should be.
-
Or are they by definition the speeds depicted with flightlevel in the flightplan pages.
And then: why cant I manually change the restriced speeds/altitude?
QuoteVertical revisions to the flightplan can be made at any point along the
route of flightQuoteIt says in the A310 FMS Pilot's Guide. Or is it only possible in a A310 and not A300?
-
In PROFILE mode is it shown somewhere what expected (indicated airspeed en vertical speed) speeds are?
LOD Issues in VR in SU3
in Modelling & Texturing
Posted
I can imagine. BUT. The developers of addon planes complain they have to adjust their plane for bugs in a final SU. And then it takes time to fix it. The beta is for testing purposes. So imho the developers have to start fixing bugs in the BETA time already, to get fixes out in time when the finale SU is released. And what better to get a group of end users cooperating with the developers to test already in the testing/beta phase!