cconesa

There's an alternative way to solve this problem, you can copy the CAMERAS.CFG file from the PW passenger to the PW cargo version and do the same thing with the GE engines. That solved the problem for me without affecting the installation and other views. I did do a backup of the files I replaced, just in case. I am not in my PC to check but it is located inside the SIMOBJECTS folder found inside the inibuilds A300 folder, inside the community folder. I will edit this message later with the exact location.

My custom views are already taken by other panel views. I understood that this issue was resolved in the pax version but was never implemented to the cargo version. When I use the joystick, the left and right buttons get me over-the-shoulder views rather than straight left and right views. Please let me know. Thank you.

Anyone, Inibuilds?

Hello Inibuilds. I have requested this modification for quite some time, and it has not been corrected thus far. Can you be so kind to modify the Left and Right views (POV L & POV R in the joystick) to actual LEFT and RIGHT views as at present using those commands in the freighter version will get you Rear Left and Rear Right (over the shoulder views). This is a small fix that has already been corrected in the pax version but remains unfixed the freighter version since v1.03. These viewpoints are necessary when flying online and entering the runway to make sure there's no other traffic on final or on the runway. Thank you. Christian C./

Can you be so kind to modify the Left and Right views (POV L & POV R in the joystick) to actual LEFT and RIGHT views as at present using those commands in the freighter version will get you Rear Left and Rear Right (over the shoulder views). This is a small fix that has already been corrected in the pax version but remains unfixed the freighter version since v1.03. These viewpoints are necessary when flying online and entering the runway to make sure there's no other traffic on final or on the runway. Thank you. Christian C./

If you are able to find it, please share it with us. I have not been able to find publicly available information with performance tables for the A300-600 😞

@kevink817 thanks for your link but please note that what you found are the tables for the A300 B2, B4 and B2K. The A300-600RF aircraft is substantially different in performance to those aircraft and thus their operating tables are of no use for the Inibuilds A300 aircraft.

Can I have a link for those, please?

I have the same issue. This is not ideal, one thing gets fixed and another one get broken. Christian C./

The max weight seems to be set at 167,000 KG for the conditions detailed in my original post and my suspicion centers in the runway length. At would have thought that at 3,500 meters long it would have been sufficient for a MTOW but would seem not to be the case. I did check with different flap settings and temperatures, but the result was the same. Yes, please, if you can give me the links for the T/O and aircraft performance tables, it would be great. Christian C./

It may well be as you suggest but as we do not have performance table there's no way to know if the limitation is temperature, atmospheric pressure, runway length or a combination of the three that restricts the operation in the example I suggested. If Inibuilds can clarify and/or provide performance tables, it should help. Christian C./

With the latest update v1.08, I am finding that the EFB will not calculate take off speeds close to MTOW. I have set up the flight for a ZFW of 124.66 KG, 44.06 KG of fuel and a TOW of 168.22 KG. The runway is 3,500 meters long, temp 26C, altitude 1,200 ft and 1007 HPG. The EFB shows an "unable to find safe performance data" message. With v1.06 I could obtain T/O data but not with this latest version. Any thoughts?. Christian C./

I appreciate that it has been said before that A300 is not meant to be run at anything but x1 speed but the reality is, that the A300 can be run at x2 quite comfortably. I did one flight today taking 6 hours and I run most of the trip at x2. No problems in the flight but the fuel consumption was halved what was supposed to be. Can this be corrected in an early future update, please?. Christian C.\

Unfortunately, these two items are still not resolved in v1.06. Please, please, can you get them fixed?

TBH, I've given up looking at weights in Simbrief and compare it with the date in the EFB. All I'm interested to check is that the load carried matches what I had set up in simbrief and that all other weights are not off by much. You can always make your own edit of the simbrief official profile and correct what you feel is wrong. Going back to my original post: "The weights are correctly loaded into the EFB, is the FMC LSK when pushed in blank, puts in a ZFW that is 400KG below the ZFW shown in the EFB, in other words, there is discrepancy between the ZFW in the EFB and the one detected by the FMC. If you can check, inibuilds, it will be appreciated."

I had a few CTD when starting the sim after having chosen the aircraft and airport to spawn from. I have noticed that these CTD occur when I have installed a new livery that was not present before or I have modified (i.e. added cargo livery to the pellets or similar). When I do the changes or additions I mentioned before, before starting the sim, I delete the data cache (which is not enabled anyway) and have not had CTD since I've done this. A similar thing occurs with the A310 and does not happen with other aircraft in MSFS. Is it possible that there is a cache of sorts for the aircraft, so it loads more efficiently in MSFS?. If you recall, in P3D it was required to sometimes "clear the shader cache" to stop these sorts of CTD. Does MSFS have a similar thing that is creating a conflict with the inibuilds A310/A300 aircraft?. Just a thought.

Not a Simbrief issue. The weights are correctly loaded into the EFB, is the FMC LSK when pushed in blank, puts in a ZFW that is 400KG below the ZFW shown in the EFB, in other words, there is discrepancy between the ZFW in the EFB and the one detected by the FMC. If you can check, inibuilds, it will be appreciated. Best!.

These may or may not be issues but worth pointing out: 1. I mistakenly pushed the TO/APPR button in the FMC whilst I was setting up the aircraft for taxiing. Once pushed, there was no way to get back to the TO page and remained in APPR mode. Is that how it is meant to be or is it something that needs to be looked at? 2. When simbrief is downloaded into the EFB, at setting up time in the FMC, pushing the ZFW key brings the estimated ZFW in the EFB but the number is off by approx -400KG. Of course, the correct weight can be input into the FMC but there may be an issue when the ZFW is blank, the key is pressed, and the FMC reads an incorrect number. All the best!

Please don't forget to check this issue, it is still present in v1.05. The upper beacon does not show properly (on the F version, haven't checked the Pax version) and with the optimised textures. Thank you.

Stellar support and kudos to inibuilds for bringing out a quick patch to resolve the LNAV (and other) issues!. Hopefully, not much else needs to be done whilst other minor issues are resolved. Great customer support and thank you for listening to us all. Best!. Christian C./

Says it all.

Can I please ask you to revisit this request?. The views remain unchanged when looking left and right (joystick POV). We are still looking over the shoulder. Thank you.

Logo lights, I believe, only come on when the landing gear is down. It is an Airbus trademark of their planes.

This issue still remains following update v1.04 and is restricted to the optimised resolution texture pack. Can you please check and correct (perhaps a hot fix?). Thank you.

Hi, The background lights (indicators) for the ECAM display knob adjustments are not lit up as are other instrumentation around the center pedestal. Worth having a look if this is not intentional (see photo). All the best!