Andiehuk1

Thanks Jorge, seems Captain Sim doesn't follow those rules :huh:

Fixed it. It is the "Prepar3D_Default.fxml" file under "user\appdata\local\lockheed martin\prepar3d v2". I replaced that with a previously saved flight called "Previous Flight.fxml" which was an autosave from FSUIPC, so pleased I turned that feature on now! Hey presto the sim now works. Not 100% sure what caused this but everything points to the Captain Sim 777 as it happened after running that aircraft. What a pain... Hope this helps someone else in the future, last thing you want to do is reinstall everything again! Andy

Hi Jorge, Thanks for the response. Unfortunately that makes no difference. Any other ideas? Thanks Andy

Hi, I've just started getting this problem after re-installing which took two flipping days. I really don't want to have to start from scratch and doing a restore is likely to wipe out good file changes. I do have captain sims 777 but its the P3D2 version. Does anyone know which file has become corrupt please, I can do a temp install on another machine just to get the original files but need to know what needs replacing. It wouldn't be the "Prepar3D_Default.fxml" under appdata\local\LM\P3Dv2 would it? Any help is appreciated, I really don't want to have to start from scratch. I seem to spend more time installing the thing than actually flying these days! Thanks in advance, Andy

Indeed I am Andy

Hi Roland, Excellent update. I left it running with UT2 mode on (not networked) for about 4 hours last night and the approaches into EGLL were very impressive, very few go arounds. Departures working well also. Andy

Thanks for the heads up Clive. Surely it should be set to 50 though or there is still the potential for aircraft turning round to join a star and disappearing when they get 50nm's away from the users aircraft. I'll give it a go and report back. Best Andy

Hi Roland, Re UT2. One thing to note about that software is it only spawns aircraft within a 50nm radius of the users aircraft. I had mixed results with UT2 because aircraft would get picked up by your software and then vectored to the nearest STAR but because it began more than 50nm from my aircraft they would then drop off the radar never to return. Your program therefore does not work too well with UT2 due to this. Unfortunately there is no way to increase the spawning radius with UT2 which is a real pain tbh. It should have been a user configurable setting. Andy

You could create your own SID and STAR for the airfield and get the program to use them.

Hi Roland, Not sure if this is possible for the future but the AI doesn't always update it's landing runway if the wind changes. That just happened to me. Departing aircraft switched but I ended up with arrivals coming into both 9L and 27R at the same time for a bit. I realise this is a limitation of FSX AI but if there was a way to push/refresh the active runway out to all AI aircraft when you hand them over that would be great. Just a thought anyway. Andy

Hi Roland, Thanks for the explanation, it makes sense to me. I use UK2000 Extreme EGLL v2 so indeed an addon. You can download a freeware version from their site should you want to try it as I see it. Obviously its less cluttered but I'm sure the approach etc is the same setup. I have it working pretty well now. I got to this stage by removing a number of the STARs so that aircraft only go onto final from a few locations around EGLL rather than all over the place and setting the separation to 6nm. I've only seen a few go arounds and the arrivals are fairly consistent every 2mins or so now. Pretty good if you ask me! It's very cool seeing one taxi off (that can take a while) whilst another couple are on approach. I also reduced my traffic slider from 45 to 35 as I think it was getting overwhelmed after a while and the aircraft just couldn't get the separation required so just went into a loop almost. I'm not using holding either as when I turn that on I rarely get any arrivals. I might try that again now that the traffic flow is a little less. I'll let you know how it goes. A simply gui would be great, it would be very interesting to see a live arrival/departure board of sorts. Thanks for bringing us this software, it makes a huge difference once you find that sweet spot for your system and airport. All the best Andy

Hi Roland, I've been testing the new release. It now picks up the correct STAR and doesn't vector the aircraft over to the other side of Heathrow which is great. I'm still having probs though with only the occasionally arrival, I've had 1 in the last 30 mins although there is a build up of aircraft now trying to get to land they just never manage to make it. Here are my findings. Holding set to 1 Minimum sep ranges from 0,1-4. - I've noticed aircraft that are miles apart (I'm talking at least 30nm here) are being turned around and put back into the hold due to minimum separation being reached. See screenshot 1 for an example. This happens constantly. - Your program takes control again of the aircraft released to FSX ATC for final approach. They get directed back to the STAR entry point and the whole process starts again. The reason they are taken control of again is due to minimum separation. I didn't think once they are released that your program would take control again. Even with this set to off i.e. 0.0 it still happens when holding is enabled. See screenshot 2. Holding set to 0 Minimum sep set to 0 - Some aircraft after being released for approach close to the airfield turn around and head off in the wrong direction for miles. They don't appear to be controlled by your program going by the output but this does seem very odd. Could be FSX ATC of course. See my comment about the aircraft height below, this may explain it. - Certainly more approaches but many go arounds due to no separation. Holding set to 0 Minimum sep ranges from 0,1-4. - Seems better, still very few approaches but the best I have had it so far. More often than not with any settings aircraft are being released to FSX ATC far too high. I think this might be why they get vectored away from the airfield again before finaly trying to land. I just noticed and aircraft being released at FL100, after release it climbed back to FL180 and headed off away from the airfield. Is there a minimum height that FSX ATC wants the aircraft at before it's ready to vector them onto the approach? Some ideas for enhancement. Whilst it's nice to see the text scrolling through the window it's not always easy to follow what's going on. One thing that would really enhance your program is to change your scrolling list into an auto updating table. The table could show for example... flight number aircraft type departure airfield arrival airfield assigned sid/star status i.e. holding, on approach, going around, next waypoint etc. This table would be great asset to the program. Just a thought anyway. Hope the above helps. All the best Andy

Hi, Download working ok for me. Andy

Hi Roland, Thanks for the reply and for continuing to develop the software. It sounds like you have seen and fixed all the probs I was experiencing so as and when you get the new release out I'll certainly give it another go and let you know the outcome. I like the idea of the assigned SID taking into consideration the destination airport, I had noticed that, nice fix! Any ideas when you can put the new release out? No pressure just want to know when to come back here and test that's all. All the best Andy

Hi, I've been testing out the software today with unfortunately not with a great deal of success. I really like the idea so hopefully any bugs etc can be ironed out eventually. I've been basing my tests around EGLL and only EGLL. I did an aiconv from the latest PMDG sids and stars for EGLL and made no other changes to the files. After starting up FSX it took something like 40mins before I had an arrival with the aircraft seemingly being vectored to STARs on the other side of Heathrow. For example aircraft close to LOGON where being told to direct to OCK2C which made little sense when a LAM3A would have been far better. Correct me if I am wrong but I thing pretty much all STARs are available to use no matter what runway is in use at EGLL. I changed the option AIautostar to AIautostar=0 in the hope this may help but the program does not honor that change, it stays at 1 as shown when the program loads regardless of what you set that to in the ini file. Another issue I came across is when I did actually have some arrivals the first one would land and then any other aircraft afterwards would get to say 50ft above the ground before climbing away and being vectored to a SID. The runway was clear all times. I was trying to figure out why it too so long for the arrivals to start coming in but there didn't really appear to be any pattern. The aircraft were just going all over the place at odd heights must of which were far too higher for an approach to work. The most I had was two aircraft on approach at the same time with the next aircraft coming in probably about 15 mins later. I'm happy to produce a logfile for you should this help. In fact I'll kick it all off again now and start logging for the next hour. Thanks for having a go and trying to crack this. Best Andy