MD82
-
Posts
43 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Downloads
Posts posted by MD82
-
-
On KRFD to KSLC. Via NORDK6, OCS transition. ILS 16L via WEBER. On the ground, I set both departure and arrival. No issues. I removed STAR WEBER and connected ILS 16L WEBER under NORDK. No issues. I took off and flew to about 500 miles to destination. I manually set 15000 at CARTR, then set a speed transition of 250/15000. Total freeze MSFS.
-
Referencing the A310 Sperry manual p. 38 Chapter 3.2 1st sentence.
- The FROM waypoint (or the waypoint you have passed) should be the actual time you crossed it. As of now, the FMC just calculates the estimated time overhead from actual position back to that waypoint.
Referencing the A310 Sperry manual p. 38 Chapter 3.3, bullet points 2 and 3.
- The distance between the FROM waypoint to the current active fly-to waypoint should display actual distance between the aircraft and the waypoint. As of now, total leg distance remains displayed.
- In addition to the leg distance between the waypoints (which ever you have slewed the F-PLN to) in lines 2 and 3 should display the course in addition to the usual distance, in the format of DIS/CRS°. As of now, only distance is shown between all waypoints .... including the ones between lines 2 and 3.
Xander
-
2
-
-
Please the below forum post. It is still the same in 1.10. It's not an install issue. I tested it yesterday, and I don't remember a changelog item where this is addressed.
-
1
-
-
-
Let me correct. it is the same problems as are being reported. Airplane flies, but panel is unresponsive.
ini livery N173UP
-
Hello,
planned on doing the SCOLA1 STAR into KRNO. MVA transition. And the RNP Y 17L.
- 1st step I did was to edit the 250-knot restriction from 250/FL100 to 250/FL150 as per my preference. No problem.
- 2nd step was to connect the STAR to the APPR as it finishes on a heading of 333 after KLOCK.
- I deleted KLOCK from the STAR end, and poof. Both FMCs stuck. Airplane flies. Just that I have no FMC's anymore. FMC 1 went blank together with a DSPLY legend light. FMC 2 froze where it was last at F-PLN.
- Also, the route is completely gone from the ND and certain instruments are behaving strangely.
Xander
-
To revisit the FCU brightness. Although what the brightness knob controls have been fixed, there is still a misunderstanding of what it actually dims. It dims the FCU Window "LIGHTS" not the FCU window LCD current. Think of the FCU digits as being the same as a classic digital watch. The digits themselves are energized liquid crystals. The A300 FCU is the same as that, but in reverse. The whole display is energized (black) and where a digit is needed, that area is de-energized so the digit forms white.
What I am getting at is that the FCU brightness knob does not control that operation, it only adjusts the brightness of the lightbulbs behind and around each of those windows. This means that even if the FCU brightness light is fully turned off, you can read the digits if there is sufficient light to see the window.
https://youtu.be/-U60iLommyI?si=9doRFfGqkjyQaHQ0&t=73
https://youtu.be/5rNgIO5b7mQ?si=YSLJcL-q-RSbw3bl&t=78Look at these time stamps. It is daylight and the sunlight lets you clearly see the digits. It is exactly the same as if I have a simple Casio digital watch on my wrist. In the day, I can see it. If it is pitch black of course I can't see it. Press the light button casts light on the display and I can see it again. Without the FCU brightness, my ability to see the digits should be governed by light or shadow cast onto it. In daylight, turning the FCU brightness fully off, should only remove the yellowish glow of the light bulbs and leave the white over black effect of the LCD.
-
Hello,
the engine reverse sleeves are an open/close operation. Meaning, it does not matter if you have selected idle reverse or full reverse, the sleeves will fully open. As it is now, the amount of reverse sleeve operation is equal to the amount of reverse thrust applied.
Xander
-
Saw this too. Even if the max altitude for TO and LDG was 8000, the minima can never be 8000 as well as MDA is always higher. In the SPerry FMS manual, there is no mention of character limitations in this field.
-
I can't find any reference to it in the Sperry FMS manual.
-
1
-
-
That's correct. But now I have no official reference. So you can close this as I can't officially verify.
-
Hello,
when selecting V/S mode and confirming on the FMA. I select V/S 0.0. If I now change the altimeter setting to a new value, and with V/S still active and 0.0, the autopilot will climb/descent to regain the original altitude. In other words, V/S will increase or decrease without pilot input and without a change in the selected V/S to regain an altitude which should not be the case. VS mode at VS 0.0 should be just that if I'm not mistaken. At least it is on all other autopilot systems I know.
-
1
-
-
Disregard above as my % reference is a B4 model. However, the difference in trip fuel remains.
-
1
-
-
Hello,
if you have an airplane set up for pounds, the fuel weight correctly populates when imported from SimBrief (Have not tried manually entering a value), but when you apply the load to the aircraft, the fuel weight remains in kilograms. In other words you will see a pounds value in the top data field and a kilogram value at the bottom field (even though the unit says lbs.)
-
Hello Ini,
I have noticed for some time now a discrepancy in fuel planned and fuel used. Today I am investigating. So, I opened up an A300-600 FCOM and went to the cruise performance tables. While cruising at 140.000 kg at FL330 in ISA+10, I interpolated a cruise fuel flow of 6.983 lbs/hr. On the gauges in the cockpit, I can read around 6.150 lbs/hr. In other words, around 13% less. Now this was a spot measurement, and more tests have to be carried out, however in any case the fuel flow seems a little frugal for these engines.
I was curious if you show different data or if you know that extensive testing has already been done to match these figures. I crunched out OFP's in both PFPX and SimBrief and in both I am using less fuel than planned.
Regards,
Xander
-
Hello Nico,
on subsequent session I had it once more. So, I exited and tried with a Freighter base model and the hydraulics pressurized. After that all was good. 😉
-
1
-
-
As the title says. I tried cycling the pumps, the yellow servo control and the affected and the affected pitch feel and spoilers. I tried with all combinations of PTU ON. I have tried shutting down the engine and servicing both the hydraulics and engine 2. After start, exactly the same.
-
This fix; "Fixed - STEP ALTS page bringing up the wrong page"
I can't find the vertical revision page on the A300-600 anyways. And an FCOM search didn't yield a result. So not like the A310. But if so, what does this fix actually indicate?
-
Unfortunately it still crashes 😞
-
11 hours ago, Crabby said:
That would be an amazing suggestion/answer had my question been “Where can I find the A-310 enhanced version”.
My apologies your highness.
-
Search for it in Marketplace
-
As an update to this, I have removed Content.xml, All a310 folders and all liveries. I also uninstalled the NG Data cycle. I let the SIM reinstall the A310.
1. After install, A310 loads successfully.
2. Installed data cycle 2312 Rev. 1.
3. A310 loads successfully.
4. Back to the main menu to install A310 enhanced.
5. Loaded the flight in the exact same spot as before the Enhanced install.
6. SIM crash on flight loading.
7. Restarted the SIM.
8. Went to the same location.
9. And viola. In the SIM.
So I'll call this fixed for now. Hopefully it is permanently fixed.
-
Hello,
I have not been able to start the A310 in MSFS. After starting with an empty Community folder and verifying the A310 loads I started checking what I installed last. I found out that having only NaviGraph in the Community already caused the SIM to crash.
The SIM loads fine, and I can select the flight and click Fly. The load bar reaches around 30-40%, the MSFS music stops and the SIM crashes. Tested with other add ons and the Data Cycle works. This is with the latest SU14 Beta build and the latest NG Data Cycle.
-
1. In the REF pages, when selecting the NAVAIDS and WAYPOINTS reference page. Both options of each, take you to the new waypoint or navaid. Meaning, if I press "defined waypoints", I can create a waypoint. When I press "waypoints", which should tell me information about waypoints in the NAV database, it also takes me to the "New waypoints" page. Which is incorrect. Same goes for the NAVAIDS. Both options lead me to create a new NAVAID.
2. When inserting a STEP PREDICT., and after inserting it, all waypoints prior to the step waypoint (except the one before the set waypoint) populate with the STEP TO altitude. In other words, I insert DITAL step to FL370, I get in the F=PLN page.
XXXXX FL370
XXXXX FL370
XXXXX FL370
XXXXX FL350
S/C
DITAL FL370
-
1
-
Modified a STAR. Boom. CTD.
in Systems
Posted · Edited by MD82
Forgot to mention. Navigraph NavData and SU15 Beta (.12) and ini livery N173UP -600F.