Search the Community

Hi, first of all, a small disclaimer, I am new to this software. I think what encountered is a bug but I cannot be 100% certain. And another note to mention that I use the software without a microphone (so with the sayit and sayit+ functions), on a second computer, connected via widefs to my p3d v4.1 computer. That being said here is the problem. I flew several flight to LFMN and would like to perform a VOR B 22R, using radar vectors to the IAF BADPO. I am currently using Aerosoft 1711 cycle and pilot2atc 2.3.1.1 I wish to fly the NISAR 6R arrival. In the flight plan I select RW22R, Arrival NISA6R, transition NISAR AND CLICK LOAD. Everything works fine here. But then I select the approach. I select runway RW22R, then VOR_DME - RW22R - D22RB , transition vectors to BADPO. Everything looks fine on the mini map as I can see the procedure and a magenta Line going to BADPO and the following points. But then, when I click on load, what happens is the plan goes direct from MUS (the last waypoint of the NISAR6R arrival) to BADPO. When flying the flight, ATC clears me for the whole procedure from NISAR and expects me to fly that and I am never vectored. In the config menu, I unchecked ATC assigns SIDs STARs and Approaches, and Randomize SID STARS. I checked Force Pilot Runway selection. When I saw I was not being vectored, I wanted to try and ask for vectors using the sayit+ menu. But I then discovered that in this menu, I could request radar vectors for ILS, RNAV or Visual. But I could only request a VOR without vectors. Perhaps this is somehow connected to my issue. I made several attempts with the same result each time. Please tell me if you need some other details. Best regards. Charles MOULIN

Hello Bryan I'm loving your product so far. I have just one question. The FO it is not responding to my transition altitude and level calls. In both cases I think it is because neither the after takeoff checklist nor the approach checklist are completed. I don't know if this is intended, but as you may know, in some places the transition altitudes and levels are quite low and in some cases I need to do the transition call before the takeoff checklist and after the approach checklist. For example: I did a flight from SAEZ (TA 3000) to SBGL (TL090). In this flight the TA came before I could call the after takeoff checklist; and on my way down is the same. Could this be changed? In your other products I know that we can make this call when is needed. Thanks so much.

Hi, Ive been using FS2crew for a while now together with FSX mostly for VATSIM flights. My setup consists of running FSX on my main computer which has 3 21inch lcd monitors connected via a TH2Go. I run all my utilities,weather addons (active sky), FSinn etc on a client networked pc. However in the last few weeks ive started experiencing a weird problem that i havent faced before. To explain, i start a flight and enter transition level into FMC as part of my preflight setup following normal flows and checklist flows. Everything works perfectly up until completion of the after take off checklist. Despite setting the transition level to 10000ft in the FMC on the performance page, when passing 10000ft, FS2crew does not make the normal calls i have heard before "Transition level, flight level 100". Ive flown a number of flights now and the "Transition level, flight level 100" call occurs when i cross 32000ft (weirdlyenough, everytime at this altitude). Apart from this glitch, FSX, my pmdg737ngx-800 addon and all addons work flawlessly. In an effort to problemshoot this occurance, ive checked the fs2crew manual and looked at all otherlocaitons where transition level might need to be entered but cant find anything. The transition call on descent works perfectly based on the transition level i enter into the FMC DES page. Ive also reinstalled pmdg737ngx 1c update, followed by reinstalling fs2crew (voice) but the same error remains. Ive also checked that synch pilot and copilot entries in FMC options is selected. Not sure what i am missing? Any help would be much appreciated. Nabil Abdulbaki

Dave, Greetings!! I hope that you had a pleasant 4th holiday. I need your help in pointing in the correct way to do this. Flight Plan : KMKC ( Wheeler downtown) to KCOS( Colo springs) SID -> Select Runway -> Rwy01; Select Departure -> WLDCTS; Enroute Transition -> SLN. -LOAD Whats with intercept 274 to TYTUS in the flight plan? How do i do this SID correctly ? Best Regards Hari

Hello, When enabling Gimbal, transition in & out is not working any more. BR Eric

After two beta rounds with about 30 forum users, I'd like to invite everyone here in the forum to try out Ventura Sky, now that it is in a pretty solid state. Minor code editing is required during the installation process, that's why I decided not to post the file to the usual outlets yet. I am waiting to hear from Joan, if he'd add official support for Ventura Sky in his NOAA plug-in, installation would truly be plug and play, and that would be a good time for an official release. A user manual with detailed installation instructions is included and should do for now! Ventura Sky Beta 3 is free. It's possible to test Ventura Sky without having SkyMaxx Pro and RWC installed - it's fully functional, however, there won't be any clouds. Official screenshots in this thread: http://www.avsim.com/topic/494639-coming-soon-ventura-sky-for-x-plane-1050/ You can get the full Beta 3 package here, or if you'd just like to take a look at the manual, click here (Corrected) Here is a summary of what Ventura Sky can do for you: Interpolation of real-weather visibilities Smooth shifts (10m per frame in reference mode, 300m per second at 30fps) between visibilities reported by the NOAA plug-in, enabling a consistent, immersive weather and atmosphere experience in X-Plane. No more slap-in-the-face visibility changes on short final, or at anytime during your flight. Visibility limitation Solid visibility limit (25700m or 16sm in reference mode) below 10000 feet, independent from cloud layers (as opposed to standard X-Plane, where visibility will be set to unlimited once you pass the first cloud layer). The limit helps blend autogen and night lighting into the haze, increasing the visual consistency, and as a bonus, it improves performance significantly. Altitude based visibility at high altitudes Above 10000ft (in reference mode), your visibility will be based on your altitude, slowly increasing as you climb, decreasing as you descend. 100sm visibility will be reached at about 40000ft. Once you descend below 10000ft, the nearest METAR station visibility provided by the NOAA plug-in will be deployed seamlessly. Atmospheric scattering will also be interpolated during this transition. Sky colors and aligned lighting The Ventura Sky sky color set as been aligned with (SkyMaxx Pro) cloud lighting and improved atmospheric effects, creating a color calibrated, homogeneous atmosphere at all altitudes and all times of the day. The sky colors have been adjusted to give you a pristine, clear blue sky at the reference limit of 16nm, lower visibilities will gradually receive humidity.