1. Timer records BLOCK TIME only, i.e. Parking Brake off to Engine Shut down. It could continue to limit the ground time because of lengthy taxis.
2. Option for no movie on low-cost airlines or aircraft that would not normally have movies (ie. Small turbo-props)
3. Option to record to HDD (similar to MyAAS) at the same time in case the server stops for some reason so that flights would still be verifiable. This file could get deleted when successful filing of an online flight is achieved to avoid double recording.
4. Option to show if the user is online on VATSIM (similar to FSHost and Team Speak currently) by user entering their VATSIM ID in the settings.
5. User-Customisable sounds for events (Laura, Debbie and the girls need a vacation!)
6. Adding numbers of PAX like you can when you manually PIREP so that earnings/losses are reflected to the airline/bid etc.
AS 2 Tom Little wrote:How about super-random failures on/off? Random? Hmm- maybe, or maybe if you put them ol' engines at 100% for 15 minutes on takeoff there might be a higher chance of... Or - 3.5g's on landing MAY have hurt the gear? Or - Complete hydraulic failure just becuase we're lucky
afluhart wrote:I was wondering if it would be possible to make AAS a module. So that I could access inside of FS without having to Alt Tab out of it (i.e. to start AAS or to pirep) or at least to start the "timer" or to stop the "timer".
AS 77 John McCormack wrote:Mark,
Thanks for your suggestions. I just have a few questions and comments below.
Mark what did you mean by1. Timer records BLOCK TIME only, i.e. Parking Brake off to Engine Shut down. It could continue to limit the ground time because of lengthy taxis.
Are you suggesting changing the amount of time allowed or changing when it starts and stops based on condition of aircraft. Can you explain further?
2. Option for no movie on low-cost airlines or aircraft that would not normally have movies (ie. Small turbo-props)
Not sure if I would able to tell from the 400+ airlines which ones would not show movies, however it is based on flights that are at least approx. 3 hours or longer, but I could also check the engine types and limit it to only jets I believe. I would have to check into that.
3. Option to record to HDD (similar to MyAAS) at the same time in case the server stops for some reason so that flights would still be verifiable. This file could get deleted when successful filing of an online flight is achieved to avoid double recording.
My initial thought would be that this could be a really tough one to try to achieve, but it might mean integrating myAAS with AAS and have some sort of cross-over during temporary server/internet issues, which could require the pilot to finish and PIREP flight using myAAS.
4. Option to show if the user is online on VATSIM (similar to FSHost and Team Speak currently) by user entering their VATSIM ID in the settings.
I could prompt for and allow the pilot to enter in their VATSIM ID, however FSHost and TeamSpeak images shown on the AAS map pages are only shown if the pilot clicks on them through AAS and it doesn't try to validate if they are really using either of them. But, doing the same for VATSIM would be easy enough. I just need a good quality small image that I could use within AAS and on the map pages. If you have one, please send to me via email - thanks.
5. User-Customisable sounds for events (Laura, Debbie and the girls need a vacation!)
I agree that the sounds could get old fairly quickly. Adding some functionality to allow the pilot to choose their own files from their hard drive wouldn't take too much work. I had looked into buying some speech generating software that would have the pilot and crew speech based on the actual condition of the aircraft and environment. Such events would be the pilot telling the passengers that actual altitude, estimate arrival time and weather condition expected, however it was extremely expensive at the time. I even look into trying to use Microsoft agent to generate speech but it just didn't sound good enough. If anyone has any suggestions on something to look at or has done something similar to this, I would be very interested in discussing this further. But, a good work around would be to save off the current sound files and change the existing ones in /SOUND folder where ActiveAirSource.exe is located, just making sure that the sound files have the same filenames that is listed in the sndlist.txt file.
6. Adding numbers of PAX like you can when you manually PIREP so that earnings/losses are reflected to the airline/bid etc.
Not really sure what part PAX will play for the new website design that is in the works. But, if PAX will play a part in the data collection for the new site, we will have to come up with something.
Thanks again for all your suggestions. I???ll see what else comes along before compiling any kind of list of items to tackle.
AS 77 John McCormack wrote:AS 2 Tom Little wrote:How about super-random failures on/off? Random? Hmm- maybe, or maybe if you put them ol' engines at 100% for 15 minutes on takeoff there might be a higher chance of... Or - 3.5g's on landing MAY have hurt the gear? Or - Complete hydraulic failure just becuase we're lucky
OMG, I have a hard enough time flying with all failures off, I would be making ASHA work really hard everytime I fly doing search and rescue flights to fnd where my plane went down
I can hear it now... the reason why my 1 hour flight took 5 hours was because my landing gear busted on landing and I had to have all the passengers get out and push the aircraft to the gate...lol
But, a good work around would be to save off the current sound files and change the existing ones in /SOUND folder where ActiveAirSource.exe is located, just making sure that the sound files have the same filenames that is listed in the sndlist.txt file.
AS 77 John McCormack wrote:Good idea Ken, sounds like that will work nicely.
Return to Active AirSource [AAS]
Users browsing this forum: No registered users and 1 guest