curt1
-
Posts
110 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Downloads
Posts posted by curt1
-
-
To put the issue another way, the CRJ was far better performance wise than my FSL Airbus in P3D4.5. In V5, the CRJ now lags way behind FSL. Something is chewing up frames in a major way.
-
1
-
-
Good morning,
04:10 am here, was a little boring, so i fixed this sound File for you, sounds ok to me now.
Greetings,
schleicher77
I appreciate your sound file, it is better than my edit; however, there's still a noticeable break in the sound where it loops. This is a file that will be very difficult to make perfect.
-
The file ASC_GenRunLoop is the offending sound file with the tick. I've been unable to do a satisfactory edit on it, maybe someone else has had better luck. I did post a modified file that adjusts the wind volume as you increase airspeed. It works fine with the default VC cooling fans, but it may be too strong if you use the alternates.
Curt
-
I just double checked it in the sim. I was right before, when you go into pause mode, the MCDU looks exactly like your screenshot above. Just unpause the sim to get the MCDU active.
Curt
-
I may be off track here, but I think this can happen simply by hitting the pause hotkey (letter P). With this addon, sometimes you can't tell you've paused the sim because the sound files are still heard. Hitting the P key will return the MCDU to it's live state. There have been several times I thought the Airbus X had locked up on me, when actually my use of other addons were placing the plane into pause mode; but again, I didn't know it because I still heard the air cooling fans.
Curt
-
I'm another user with the same problem. When I click off the APU generator, the battery voltage increases, the exact opposite of what should happen. If I leave the generator on, the battery will decrease until it's exhausted.
-
From the first paragraph of the Owner's Manual:
"This Airbus had a long and complex history and to be honest everybody in the project is happy we reached the end. Doing a complex modern airliner is not easy-- we underestimated that for sure! But it was great fun and a learning experience like nothing else".
With all due respect to Aerosoft, and I do like them a lot, isn't this statement telling us why they did just a basic version? I don't think they desired to tackle a complete airliner project, because it's not their specialty. They probably didn't think they would make a profit on it if they invested numerous more hours on development. I think they're uncertain if a complete Airbus can occur...and don't want to have wasted many hours for nothing. That quote above caught my eye immediately, and I think many overlooked it. If you were to ask anyone with Aerosoft if they are capable of doing a complete Airbus with all MCDU features, customized FDE, etc...I think the answer would be 'maybe'. There would be no shame in that either, because no one else has developed an Airbus sim that appeals to hardcore simmers...the closest one is Wilco.
Curt
-
I'm no expert on this, but wouldn't deleting the entry in the aircraft.cfg be sufficient? I don't think the hassle of deleting the fsx.cfg would be necessary, but perhaps I'm wrong. Unless you're saying the installer requires an entry in the "trusted software" field. If that's the case, I would probably do a line edit only. I'm curious as to how wide a problem this is?
-
Great to hear, thanks for your strong customer support.
Curt
-
You're so right, Michael, thank you. I did an uninstall on the first bus, forgot to run the EZCA config utility when I installed v1.11. I feel like such a dope!
-
Well, something really weird is going on. I'm using the 1.11 product and saved numerous camera views with EZdok earlier. VC views as well as different wing views and external views to my satisfaction. I closed FSX, restarted it and chose the Airbus X. I started checking all of my camera views, and the VC ones are all fine; the wing and exterior views are still in EZdok, but the textures for the Airbus have disappeared! The only visible part of the Airbus X is the exterior of the cockpit. Someone else want to test this out with EZdok and confirm I'm not totally bananas?
Curt
-
I've determined the problem to be with EZdok, not the Airbus. Sorry for the false alarm.
Curt
-
I don't care about passenger cabins per se; but in the first version, you had a view that allowed access into it, making the creation of wing views possible with the EZdok camera utility. In version 1.11, I can't find a way to enter the cabin and move around, therefore, no ability to create the views with EZdok. Small request, but hope that feature can be reincluded in the next patch or version.
Curt
-
1
-
-
I know the PFD is to show the CLB and RWY TRK annunciations in blue for takeoff. I can make this happen by selecting an aircraft state from the MCDU, but I can't get the proper annunciation in blue from a cold and dark state. Would someone please explain what is the key procedural step required to get the proper PFD annunciation?
Well, I just took another look. If I just select the Airbus from the aircraft menu, it's running in idle on the runway. I guess it's from the initial loadup position that I can't the get proper annunciation. It's weird, maybe someone knows what I'm talking about.
Curt
-
Thanks, Timo, I don't know how I missed that.
Curt
-
The GPWS Test is mentioned in the documents, and I found a sound file for it also. I don't find a switch to actually run the test. What switch or steps do I need to take to activate it?
Curt
-
Er... in that case I wonder what your keys actually did before you installed the Airbus...?
I had the "top down view", "spot view", and a specially tweaked camera view for landing replays. These occupied the F9, F10 and F11 keys. They could be used for all addons...except this one. So deleting the key assignments in settings prevents the Airbus X views, but also renders my current hotkeys useless. So I will reassign those views to other keys, I guess...and the F9 to F12 keys will stay unused. I hope I'm making sense here.
Curt
-
Maybe I'm overreacting a bit, but I just wish Aerosoft had designed a hotkey interface like other developers, so we can decide what hotkeys we want. Having them predetermined means we have to reconform our configuration around their one addon. Oh well, maybe this could be addressed in the patch.
Curt
-
Simply go to the FSX controls page and look for F9 to F12 and delete the assignements.
EDIT:
To make it easier for you:
F9 = Virtual Cockpit (shortcut)
F10 = 2-D Cockpit View (shortcut)
F11 = Locked Spot View (shortcut)
F12 = View camera 4 (select)
Look for them, select them and press Delete Key Assignement.
Thanks for the reply; however, by deleting the key assignments, it eliminates the use of those keys as hotkeys to the camera.cfg file. This addon is going to require me to reassign many hotkeys, and I'm quite dissappointed.
-
Just as I thouht, the Airbus X hotkeys for F9 thru F12 are overriding my previously assigned hotkeys. I have assigned hotkeys in the camera.cfg file, and they no longer work. I would appreciate advice on how to deactivate the Aerosoft hotkey commands.
Curt
-
Yes, please the manuals, I was going to read them first anyway!
Curt
-
5
-
-
I mentioned here about a week ago about a possible conflict with the EZCA camera addon. I didn't see a response so I forgot about it, but I bring this up because you have assigned Airbus X views to the F9 through F12 keys. My understanding is EZCA has required use of the F9 and F12 keys for it to function properly. The developer at EZCA gave me the following list earlier in the year:
Table of reserved EZCA hotkeyselect
For VC :
HotKeySelect=1 (default) (my remark; F9 key)
For EZDOK universal camera :
HotKeySelect=4 (default ) (my remark; F12 key)
For world cameras:
HotKeySelect=5
HotKeySelect=6
HotKeySelect=7
HotKeySelect=8
HotKeySelect=9
HotKeySelect=10
The
HotKeySelect=2 (my remark, F10 key)
HotKeySelect=3 (my remark, F11 key)
free for use.
I don't know if you beta tested this along with the EZCA camera, but if not I'm concerned about a potential conflict. I'm just offering this information in case a problem pops up.
Curt
-
I have a question from the owner's manual, something that's significant in any aircraft addon. It discusses the ability to save the aircraft in various states (cold and dark, take-off, taxi state, etc..) but goes on to say the flight plan is excluded due to technical reasons. How does one resume a flight from the cruise state if the flight plan isn't loaded in the MCDU? I guess you can import it back in from your flight planner, then do a 'direct' to the next waypoint to re-initiate the flight? If that's the case, I guess no major problem exists. Still, it's unfortunate that it couldn't have been retained with the rest of the settings.
Curt
-
Just curious, the manual speaks of mouse usage, left click, right click etc...but doesn't discuss how to apply the "push" button that's necessary on the FCU. Hoping it's not the middle mouse button, as EZCA camera controls that for it's pan view feature. What's working out for the beta testers on this?
Curt
CRJ pro performance issues in both p3dv5 and v4.5
in General discussion and support
Posted
I don't know where we go from here. Users complain about poor performance, but Hans can't duplicate the issues on his system. In addition to that, it appears all development is now focused on the MSFS version. If nothing can be done to improve the performance, then I may as well uninstall this because I can't fly it as is.