|
Post by pelayo on Oct 8, 2016 13:12:06 GMT -5
Pelayo, You and I are the only two who have seen this and my testing of the "fix" looks good to me. Alpha 8 has just gone out to the testers and I hope to have a public Release Candidate (with some updated docs) ready within a week's time. Regards, Great! Thanks
|
|
TimoDD
Trainee
Find me on Discord by this link: https://discord.gg/XVbzG
Posts: 12
|
Post by TimoDD on Oct 8, 2016 13:40:31 GMT -5
Hope soon to test the new version. Have for the moment too much flight-proposals with no pax. Looks weird to fly jobs with any kind of pax to my tought. Have to much the nota: 'No Flights Found Matching Criteria'.
|
|
|
Post by Travis on Oct 9, 2016 13:51:26 GMT -5
Beta 1 will be released this week - hopefully in a day or so.
Two nights ago I encountered a phenomena which I was safely able to back out of (literally), but which I needed to account and test for: I was approaching my takeoff runway that had a parallel taxiway opposite me. I turned to face the runway, asking for clearance when the AI aircraft on the opposite taxiway was cleared for takeoff. When we were facing one another, I noticed the AI aircraft was frozen by the ACME AI Freeze Ray. (When in development, I normally run in "debug mode" which allows me to stop things when needed to look at the internal variables.) After a minute of thinking, I toggled the invisible pushback to move me backwards far enough so the AI aircraft wasn't affected by my Freeze Ray and could depart. So in 1.7.3, if the AI Freeze Ray is active, the FCDU screen number will be presented in RED (rather than GREEN).
When this happens during taxi-out, clicking on any FCDU button will pause the AI Freeze Ray for 60 seconds (we may reduce the time) to allow AI to proceed as they are driven to.
It's the weirdest things that we run in to....
Regards,
|
|
|
Post by jarkko on Oct 17, 2016 11:28:22 GMT -5
I had this happen to me today with 1.7.2 update (updated today). I needed to do a test flight from LOWS to LIME and this route was not given to be by FSCaptain. I did the optional setup, where I setup departure as LOWS, destination LIME, alternate LIPO, number of passengers 142, cargo 2500 pounds.
I then did the normal planning steps (import flight plan, import winds, expected time, expected fuel). After this, I didn't make sure what the dispatch document said when I confirmed the flight. When I started the flight, I was surprised that I got only 2 passengers onboard for my flight.
Will try a similar flight in the near future.
|
|
|
Post by Travis on Oct 17, 2016 23:32:09 GMT -5
Hallo Jarkko!
By now you will have seen my "please send the appropriate log files" plea, and with luck the 1.7.3 Beta 1 build will have eliminated this negative PAX issue. (It did for me... but what for thee??)
Please follow up within the Testers forum....
Regards,
|
|
|
Post by Travis on Oct 17, 2016 23:37:40 GMT -5
So in 1.7.3, if the AI Freeze Ray is active, the FCDU screen number will be presented in RED (rather than GREEN).
When this happens during taxi-out, clicking on any FCDU button will pause the AI Freeze Ray for 60 seconds (we may reduce the time) to allow AI to proceed as they are driven to. Captains,
There's been a change in this behavior, and starting with 1.7.3 the AI Freeze Ray will only be active if your aircraft's Landing Lights are on. (This includes the Taxi Lights if your aircraft uses the simulator lighting signals.)
We feel this better models "proper behavior" as you should have some form of taxi lighting active when you are in taxi. (We recognize that some aircraft don't have a lighting system where the aircraft's Taxi Lights actually illuminate the ground... so we've made it for either/both Taxi and Landing Lights.)
So if you're in taxi and you are freezing an aircraft which you need to have continue its movement, turn off your Landing and possibly Taxi Lights and that aircraft should continue with its business. You can then turn your lights on as necessary and continue with yours....
|
|
|
Post by Travis on Oct 23, 2016 10:36:30 GMT -5
Just a note that Beta 1 has been released to the test team, and as soon as I have verified that it "loads and works" for someone other than me, we will release this for public testing.
Although... in testing over the past few days I have seen 'negative pax' with some attempts to list flights. I think I know what the issue is, but rather than delay public release, I want to get Beta 1 out, knowing there will be a Beta 2 to follow within a week or so.
|
|