flystaralliance

Fly Star Alliance is proud to announce that it will be a primary sponsor in the upcoming amazing week-long VatVenture Event. We are less than two weeks away from the beginning of this fantastic event and we really look forward to open the celebrations on Monday, July 23rd during the "VFR Day" theme with the Pattern Work Competition!! The event schedule and related "Themes" is as follow: Fly Star Alliance: MONDAY VFR DAY PATTERN WORK COMPETITION (Night) Virtual United: MONDAY VFR DAY PATTERN WORK COMPETITION (Night) Canadian Express: TUESDAY IFR DAY Virtual Delta: TUESDAY IFR DAY XOJET Virtual (BIZ JET): WEDNESDAY BIZJET DAY LJ45 RACE (Night) Freight Dogs (Cargo): THURSDAY CARGO DAY UPS Virtual Air Cargo: THURSDAY CARGO DAY Delta Virtual: FRIDAY ANYTHING GOES DAY American Virtual: SATURDAY AIRLINER DAY American Pacific Group: SUNDAY GA DAY C172 RACE (Afternoon) Participating to the competition is not mandatory, but if you do you will have the ability to win one of the many prizes provided by PMDG, Flight1 and Feelthere. All charts, procedures and more will be published and available in our Forum (Events Section) as well as packaged in the Downloads section of the website. You can watch the Event promo here: For more details and briefing don't forget to visit the main website event at: http://www.vatventure.org/index.php Let's show our strong presence within the VA community and bring some Star Alliance planes in the air around Oshkosh airspace!! I'm always available to answer any questions you might have via AirMail, Forum and Fly Star Alliance Facebook page and also to coordinate an eventual group flight. Every Fly Star Alliance pilot participating to this event will receive a one-time special "signature style" award.

It used to be there in quite a few FS2Crew versions before. Especially the very first Level-D 767 button edition had a whole slew of recorded dialogues between the PF and the FO where they used to talk about family, kids and salary issues.......The current Level-D 767 voice version starts with: "Hi Captain, how are you today?" and you'll respond: "Any snags with the plane?" My guess is that, following the program evolution they realized it wasn't a feature that users really required/needed and the focus has shifted more onto the real core features like FO's flows and ability to carry actions and given commands. Again, keep in mind this is just my opinion and I'm sure Brian will certainly tell more about it. Cheers Will

Another quick workaround if you are a part of those users that "DO" get the SDK erroor: Load the AC straight from the 3D VC. Start FS2Crew and let it tell you about the SDK error. Go to "Select Aircraft" and reload the aircraft. Once the AC reloads and you re-click the hotspot to start FS2Crew you will be SDK error free. Cheers Will

Not sure it's a matter of settings, but instead a GSX issue. Same thing is happening here randomly with exactly the same add-ons. Will keep investigating and posting if/when a solution is found.Cheers

After quite a bit of testing I found this settings to work very well on my machine. Try it on and see how it goes: [PROXY]EnableProxyLibrary=0InitProxyFunctions=0ProxyLibrary=[GLOBAL]UseEffect=1AlternativeDepth=1AllowAntialias=1BugFixMode=0SkipShaderOptimization=0QuadVertexBuffer=0EnableShaders_3_0=1UseMRTRendering=0AdditionalConfigFile=enbseries2.ini[EFFECT]EnableBloom=1EnableOcclusion=0EnableReflection=0EnableMotionBlur=0EnableWater=0EnableShadow=0DepthBias=0EnableDepthOfField=0[iNPUT]KeyUseEffect=123KeyBloom=120KeyOcclusion=121KeyReflection=122KeyCombination=16KeyScreenshot=44KeyShadow=119KeyWater=118KeyShowFPS=106[REFLECTION]ReflectionPower=100ChromePower=100UseCurrentFrameReflection=1ReflectionQuality=1ReflectionSourceSpecular=50ReflectionSourceTFactor=50UseAdditiveReflection=1ReflectionDepthBias=0UseLowResReflection=1ReflectionSinglePass=1UseEnvBump=1EnvBumpAmount=100EnvBumpOffset=100ReflectionFlip=0[bLOOM]BloomPowerDay=7BloomFadeTime=400BloomConstantDay=1BloomQuality=0BloomScreenLevelDay=75BloomCurveDay=0BloomPowerNight=18BloomConstantNight=2BloomCurveNight=0BloomScreenLevelNight=20BloomAdaptationScreenLevel=40BloomAdaptationMultiplier=50BloomAllowOversaturation=1BloomMaxLimit=100[sSAO]UseFilter=1OcclusionQuality=2FilterQuality=1DarkeningLevel=30BrighteningLevel=30IlluminationLevel=30AdditiveIlluminationLevel=30UseAmbientOcclusion=1UseIndirectLighting=1FadeDistance=50UseForAlphaTest=0UseForAlphaBlend=0 [colorCORRECTION]DarkeningAmountDay=30ScreenLevelDay=70ScreenLevelNight=1DarkeningAmountNight=15GammaCurveDay=0GammaCurveNight=-2ColorSaturationDay=2ColorSaturationNight=0UsePaletteTexture=0[WATER]UseWaterDeep=0WaterDeepness=20WaterQuality=0[sHADOW]ShadowFadeStart=40ShadowFadeEnd=80ShadowAmountDay=100ShadowAmountNight=30ShadowScreenLevelDay=60ShadowScreenLevelNight=20ShadowQuality=2UseShadowFilter=0FilterQuality=2ShadowBlurRange=30[ENGINE]ForceAnisotropicFiltering=1MaxAnisotropy=16ForceDisplayRefreshRate=0DisplayRefreshRateHz=60[MOTIONBLUR]MotionBlurQuality=1MotionBlurVelocity=0MotionBlurRotation=0[PERPIXELLIGHTING]SpecularColorMin=0SpecularColorMax=100SpecularColorMultiplier=100SpecularGlossinessMin=0SpecularGlossinessMax=100SpecularGlossinessMultiplier=100[DEPTHOFFIELD]DOFQuality=2DOFNumberOfPasses=1DOFFocusRange=50DOFBlurinessRange=10 Cheers Will

Thanks for the prompt response. I know, I searched the forum before posting but couldn't find anything about this. I do not use any external hardware Brian like MCP or anything alike, just a Saitek Pro Flight Yoke which of course has nothing to do with my problem. Also the problem is not happening when I send a command to the FO like: "Set HDG 316", but instead it's there since FS2Crew start-up (Yes, it does work fine without FS2crew). Like I said in my original post, It used to happen also with the Wilco PIC733, although a little different because the HDG number would keep turning in search for the wrong number, but then again in that case, stopping/restarting the voice control was good enough to regain control. Now instead, it doesn't matter if I try to change the HDG manually or if I command the FO to do it, both ways it will return exactly to where it was stuck before the change, whatever the number was. Sorry, I forgot to say, I'm a real world pilot too and I do use LNAV for initial decent and all the way down to final APP, but there are times when I need the AP HDG to properly vector the aircraft to complete the final APP and landing. This is not a NO GO problem, it's just annoying when you're on Approach, especially if you always fly online like me and you get vectored a lot. Anyway, please let me know if any idea pops up and in the meantime I will keep tinkering around to see if I can find out why it's happening or find a way to prevent it.CheersWill

Hi guys,I'm an avid FS2Crew products user and very familiar with the voice editions since I pretty much own all of them. I have a little problem with the iFly one on FSX that I cannot seem to sort out. Basically, everything is working perfectly, beside one little thing. The AP HDG gets stuck to whatever value is there, let's say 317 and there's no way to move it from there or, for better saying, you can change the number, but it immediately gets right back to where it was.In other instances/aircraft with the same issue, turning the Voice off and then back on would work and solve the problem, but not with the iFly. Any ideas ??Thanks for all your help and the great quality products you always provide to us.CheersWilliam M.

Your FSX.CFG file is located here: C:\users\yourusername\app data\roaming\microsoft\FSXMake sure you have the "Show hidden files & folders" option unchecked in your folder options.Hope this helps.CheersWill

Excuse me but with all those zeros I will buy the real thing !!!! LOL