January 6, 201115 yr Hi JD,I don't know wether this is just a fluke, but recently I have been getting vectored at the destination airport to the incorrect runways,When I try to get a weather report for the destination airport, it is totally different than what ASE is depicting.I use ASE SP2 and radar Contact via networked Laptop, with wide fS. FSX SP2 on W7 64. FSUIPC ver 465 and USEASE=YES in fsuipc.iniNow this is where it get's interesting, I downloaded http://fsuipc.simfli.../FSUIPC4648.zip and with 648 I did a flight from KORD to KPTA and RC peformed 100%. Accurate weather report for KTPA and landed on correct runway. I did do a "Debug" but the file is about 250meg, so would need to do a shorter flight. I thought a debug might show something. Look forward to your comments.CheersJulian
January 6, 201115 yr Commercial Member When I try to get a weather report for the destination airport, it is totally different than what ASE is depicting.I use ASE SP2 and radar Contact via networked Laptop, with wide fS. FSX SP2 on W7 64. FSUIPC ver 465 and USEASE=YES in fsuipc.ini1. There's not yet a release of FSUIPC numbered 4.65. I am hoping to release that by the end of this month, or soon thereafter.2. UseASEweather should normally be omitted. You only want to set it to Yes if you want to force FSUIPC to get the weather from ASE no matter what mode it is in. There's really no point in doing that except in DWC mode, in which case it is automatic in any case.So why are you setting that parameter at all?Now this is where it get's interesting, I downloaded http://fsuipc.simfli.../FSUIPC4648.zip and with 648 I did a flight from KORD to KPTA and RC peformed 100%.Accurate weather report for KTPA and landed on correct runway.Sounds like you are using DWC in ASE, and whatever version of FSUIPC you were using instead of the non-existent 4.65 was made before the ASE weather reading facilities were added.Just delete that UseASEweather parameter.Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 6, 201115 yr 1. There's not yet a release of FSUIPC numbered 4.65. I am hoping to release that by the end of this month, or soon thereafter.2. UseASEweather should normally be omitted. You only want to set it to Yes if you want to force FSUIPC to get the weather from ASE no matter what mode it is in. There's really no point in doing that except in DWC mode, in which case it is automatic in any case.So why are you setting that parameter at all?Sounds like you are using DWC in ASE, and whatever version of FSUIPC you were using instead of the non-existent 4.65 was made before the ASE weather reading facilities were added.Just delete that UseASEweather parameter.PeteHi Pete,Thanks for your reply. My mistake, it was version FSUIPC4645. UseAseWeather=Yes was in the fsuipc.ini file. I did not type it in there. I assume it was automatic ? Anyway will remove it.Maybe I will get consistent destination weather now.Thanks for your helpCheersJulian
January 7, 201115 yr Commercial Member Thanks for your reply. My mistake, it was version FSUIPC4645. UseAseWeather=Yes was in the fsuipc.ini file. I did not type it in there. I assume it was automatic ?If you did not put it in then someone must have done behind your back, because FSUIPC most certainly NEVER adds that paramter itself. There's no code for it at all.Maybe I will get consistent destination weather now.I thought you just said you did, with 4.648? Is it me that's confused?RegardsPete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 7, 201115 yr If you did not put it in then someone must have done behind your back, because FSUIPC most certainly NEVER adds that paramter itself. There's no code for it at all.It's ok Pete, I must have and forgot I did :blush:I thought you just said you did, with 4.648? Is it me that's confused? Confused myself as well, what I meant to say was " I will now have consistent destination weather" <sigh> Thanks for helping and sorry for the confusion.Edit: This is the info I based my decision to add UseAseweather=yes from the sticky on this forum," UseASEweather=Yes as instructed would be beneficial in all modes".So is that incorrect, and if it is should in be edited, or am I wrong ? reading that paragraph and from a user pespective, have I read that wrong ?CheersJulian
January 7, 201115 yr Commercial Member This is the info I based my decision to add UseAseweather=yes from the sticky on this forum," UseASEweather=Yes as instructed would be beneficial in all modes".So is that incorrect, and if it is should in be edited, or am I wrong ? reading that paragraph and from a user pespective, have I read that wrong ?No, obviously you are reading what it says, but I don't understand why it was written.Perhaps the author could explain? I thought the only problem with ASE weather was when DWC was in use, so making it impossible to supply correct weather for anywhere but at the aircraft without using ASE-supplied weather. When DWC is not in use, ASE is populating the weather around properly, just as FSX does by default, and so FSUIPC can read it directly from FSX -- rather more efficiently.The only advantage would be if you wanted to get weather for a station a long long way away. Using ASE weather, for example, will allow you to get KJFK weather whilst in EGLL. But this wouldn't be ATIS -- ATIS range is only about 80 nm or so. For flight planning purposes you'd be using ACARS, or the MET reports, and most of that is done in the planning stage before you get into the aircraft.Maybe the author of that "stickie" (which I'd not read before) has a different modus operandi to myself. If I thought it was generally better to always use ASE weather I'd have made it default. As it is I preferred to go for maximum efficiency.RegardsPete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
January 7, 201115 yr Commercial Member No, obviously you are reading what it says, but I don't understand why it was written.Perhaps the author could explain? I thought the only problem with ASE weather was when DWC was in use, so making it impossible to supply correct weather for anywhere but at the aircraft without using ASE-supplied weather. When DWC is not in use, ASE is populating the weather around properly, just as FSX does by default, and so FSUIPC can read it directly from FSX -- rather more efficiently.The only advantage would be if you wanted to get weather for a station a long long way away. Using ASE weather, for example, will allow you to get KJFK weather whilst in EGLL. But this wouldn't be ATIS -- ATIS range is only about 80 nm or so. For flight planning purposes you'd be using ACARS, or the MET reports, and most of that is done in the planning stage before you get into the aircraft.Maybe the author of that "stickie" (which I'd not read before) has a different modus operandi to myself. If I thought it was generally better to always use ASE weather I'd have made it default. As it is I preferred to go for maximum efficiency.RegardsPetei'll contact ronjd JD Read my blog
January 7, 201115 yr I think I'll let someone else notably Bob Johnson who is actually running this environment modify it. I did post a later reply incorporating what service notes were on the hi-fi AS forum.
January 8, 201115 yr Hello Everyone,This issue with slow response is very puzzeling to me since I don't have this same issue at all. Let me start this discussion with a description of my environment. I am using a PC that utilizes a Windows Vista 32bit version, FSX sp2, with the following cfg / This file was tweaked on Dec 28, 2010 at 22:11 GMT using Bojote's automated FSX Tweaking & Tuning Service: SHOW_AIRPORTS=1SHOW_AIRSPACE=1SHOW_APPROACHES=1SHOW_DATATAGS=1SHOW_FLIGHTPLAN=1SHOW_INTERSECTIONS=0SHOW_JET=0SHOW_NDBS=1SHOW_TERRAIN=1SHOW_VICTOR=0SHOW_VORS=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1show_flight_history=1[RWW_WEATHER_MAP]SHOW_AIRPORTS=0SHOW_AIRSPACE=0SHOW_APPROACHES=0SHOW_DATATAGS=1SHOW_FLIGHTPLAN=1SHOW_INTERSECTIONS=0SHOW_JET=0SHOW_NDBS=0SHOW_TERRAIN=1SHOW_VICTOR=0SHOW_VORS=0SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1[bufferPools]PoolSize=0RejectThreshold=131072[VirtualCopilot]VirtualCopilotActive=0[sOUND]AmbientUI=6AmbientUIMusic=FSX01AmbientUIMusicVolume=-6.000000PrimaryDevice={DEF00000-9C6D-47ED-AAF1-4DDA8F2B5C03}SOUND=1SOUND_FADER1=0.500000SOUND_FADER2=0.500000SOUND_FADER3=0.500000SOUND_FADER4=-0.000000SOUND_LOD=0SOUND_QUALITY=2UISound=1VoiceDevice={DEF00002-9C6D-47ED-AAF1-4DDA8F2B5C03}[slewTextInfo.1]AirSpeed=1,5Altitude=1,3Heading=1,4Latitude=1,1Longitude=1,2[DISPLAY.Device.NVIDIA GeForce 8800 GT.0]Mode=1680x1050x32[AContain]LabelColor=FFFF0000LabelDelay=4000ShowLabelAirline=1ShowLabelAirlineAndFlightNumber=0ShowLabelAirspeed=0ShowLabelAltitude=0ShowLabelContainerId=0ShowLabelDistance=0ShowLabelFlightPlan=0ShowLabelHeading=0ShowLabelManufacturer=0ShowLabelModel=0ShowLabelTailNumber=0ShowLabels=1ShowUserLabel=1[ATC]AutoOpenAirTrafficWindow=0COMM_MSG_AI_ATC_COLOR=FFFF7840COMM_MSG_ATC_AI_COLOR=FF00FF00COMM_MSG_ATC_USER_COLOR=FFB6FFB6COMM_MSG_NONE_COLOR=FFFFFFFFCOMM_MSG_USER_ATC_COLOR=FFFFD21BPilotVoice=0ShowATCText=0UsePilotVoice=0[TextInfo.1]AirSpeed=1,5Altitude=1,3Heading=1,4Latitude=1,1Longitude=1,2WindDirectionAndSpeed=1,6[iNTERNATIONAL]ASLAT=2ASLON=1MEASURE=0[CONTROLS]Controls_Current=StandardControls_Default=StandardKBDAIL=64KBDELEV=64KBDRUD=64STICK_SENSITIVITY_MODE=0[FACILITIES]CITY=COUNTRY=Puerto RicoGTL_BUTTON=1358STATE=[TextInfo.3]AirSpeed=1,5Altitude=1,3FrameRate=2,1FuelPercentage=2,4GForce=2,3Heading=1,4Latitude=1,1LockedFrameRate=2,2Longitude=1,2WindDirectionAndSpeed=1,6[PointOfInterestSystem]CycleSetting=0[GRAPHICS]AC_SELF_SHADOW=1AIRCRAFT_REFLECTIONS=1AIRCRAFT_SHADOWS=0ALLOW_SHADER_30=1COCKPIT_HIGH_LOD=1D3D10=0EFFECTS_QUALITY=2ForceFullScreenVSync=0ForceWindowedVSync=0GROUND_SHADOWS=0HIGHMEMFIX=1IMAGE_QUALITY=0LANDING_LIGHTS=1NUM_LIGHTS=8See_Self=1TEXTURE_MAX_LOAD=1024TEXTURE_QUALITY=3Text_Scroll=1SHADER_CACHE_PRIMED_10=1693458432SHADER_CACHE_PRIMED=1693458432[DISPLAY.Device.NVIDIA GeForce 8800 GT .0]Mode=1680x1050x32[TrafficManager]AIRPORT_SCENERY_DENSITY=3AirlineDensity=49FreewayDensity=80GADensity=11IFROnly=0LeisureBoatsDensity=0ShipsAndFerriesDensity=0[DynamicHeadMovement]HeadMoveTimeConstant=1.000000LonAccelOnHeadLon=-0.020000LonAccelOnHeadPitch=-0.010000MaxHeadAngle=5.000000MaxHeadOffset=0.300000RollAccelOnHeadLat=0.010000RollAccelOnHeadRoll=0.100000YawAccelOnHeadLat=-0.100000[REALISM]AutoCoord=FalseAutoTrim=FalseCrashDetection=TrueCrashTolerance=1.000000CrashWithDyn=FalseGEffect=FalseGeneral=1.000000GyroDrift=FalseGyroEffect=0.000000ManualLights=TruePFactor=0.000000RealMixture=TrueStressDamage=TrueTorque=0.000000TrueAirspeed=FalseUnlimitedFuel=False[Weather]AdjustForMagVarInDialog=1CLOUD_COVERAGE_DENSITY=8CLOUD_DRAW_DISTANCE=3DETAILED_CLOUDS=1DisableTurbulence=0DownloadWindsAloft=0DynamicWeather=0MaxGustRampSpeed=200MaxGustTime=500MaxVarRampSpeed=75MaxVarTime=50MinGustRampSpeed=1MinGustTime=10MinVarRampSpeed=10MinVarTime=5THERMAL_VISUALS=0TurbulenceScale=1.000000WeatherGraphDataInDialog=0WeatherServerAddress=fs2k.zone.comWeatherServerPort=80WindshieldPrecipitationEffects=1[Misc]Com_Rate=7[Main]FIBER_FRAME_TIME_FRACTION=0.33HideMenuFullscreen=1HideMenuNormal=0Location=320,117,1360,893,\\.\DISPLAY1Maximized=1SimObjectPaths.0=SimObjects\AirplanesSimObjectPaths.1=SimObjects\RotorcraftSimObjectPaths.2=SimObjects\GroundVehiclesSimObjectPaths.3=SimObjects\BoatsSimObjectPaths.4=SimObjects\AnimalsSimObjectPaths.5=SimObjects\MiscSimObjectPaths.6=MyTraffic\AircraftUser Objects=Airplane, HelicopterProcSpeed=4432PerfBucket=7[TextInfo.2]FrameRate=1,1FuelPercentage=1,4GForce=1,3LockedFrameRate=1,2[uSERINTERFACE]DisplayFuelAsWeight=1Map_Orientation=2OpenATCOnCreate=0PAUSE_ON_LOST_FOCUS=0PROMPT_ON_EXIT=0PageID=1SHOW_MISSION_CAPTIONS=0SITUATION=C:\Users\Owner\Documents\Flight Simulator X Files\TJSJSelectAircraftManufacturer=AllSelectAircraftPublisher=AllSelectAircraftType=AllShowAllACPaintSchemes=1[sIM]SYSCLOCK=1[Display]ActiveWindowTitleBackGroundColor=0,28,140,64ActiveWindowTitleTextColor=255,255,255BLOOM_EFFECTS=0ChangeTime=2.000000InfoBrakesEnable=TrueInfoLowerLeftBackGroundColor=255,0,0,128InfoLowerLeftTextColor=255,255,255InfoLowerRightBackGroundColor=255,0,0,128InfoLowerRightTextColor=255,255,255InfoOverspeedEnable=TrueInfoParkingBrakesEnable=TrueInfoPauseEnable=TrueInfoSlewEnable=TrueInfoStallEnable=TrueInfoUpperRightBackGroundColor=0,0,0,0InfoUpperRightTextColor=255,0,0NonActiveWindowTitleBackGroundColor=24,33,87,64NonActiveWindowTitleTextColor=255,255,255RUNWAY_LIGHTS_APPROACH_SCALAR=0.8RUNWAY_LIGHTS_STROBE_SCALAR=0.8RUNWAY_LIGHTS_SURFACE_SCALAR=0.8RUNWAY_LIGHTS_VASI_SCALAR=0.8SKINNED_ANIMATIONS=1TEXTURE_BANDWIDTH_MULT=40TextureMaxLoad=30TransitionTime=2.000000UPPER_FRAMERATE_LIMIT=0WideViewAspect=False[WeatherMap]SHOW_AIRPORTS=0SHOW_AIRSPACE=0SHOW_APPROACHES=0SHOW_DATATAGS=1SHOW_FLIGHTPLAN=1SHOW_INTERSECTIONS=0SHOW_JET=0SHOW_NDBS=0SHOW_TERRAIN=1SHOW_VICTOR=0SHOW_VORS=0SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1[slewTextInfo.3]AirSpeed=1,5Altitude=1,3FrameRate=2,1Heading=1,4Latitude=1,1LockedFrameRate=2,2Longitude=1,2[PANELS]DEFAULT_VIEW=1IMAGE_QUALITY=1PANEL_MASKING=1PANEL_OPACITY=100PANEL_STRETCHING=1QUICKTIPS=0UNITS_OF_MEASURE=0[sTARTUP]DEMO=0LoadWindow=1SHOW_OPENING_SCREEN=1STARTUP_DEMO=0[slewTextInfo.2]FrameRate=1,1LockedFrameRate=1,2[TERRAIN]AUTOGEN_DENSITY=2BATCH_AUTOGEN2=1DETAIL_TEXTURE=1LOD_RADIUS=4.500000MESH_COMPLEXITY=75MESH_RESOLUTION=20SWAP_WAIT_TIMEOUT=2TERRAIN_MAX_AUTOGEN_BUILDINGS_PER_CELL=2000TERRAIN_MAX_AUTOGEN_TREES_PER_CELL=4000TEXTURE_RESOLUTION=27WATER_EFFECTS=6[sCENERY]DAWN_DUSK_SMOOTHING=1IMAGE_COMPLEXITY=4LENSFLARE=0SmallPartRejectRadius=4.0[FlightPlanMap]LineWidth=2SHOW_AIRPORTS=1SHOW_AIRSPACE=1SHOW_APPROACHES=1SHOW_DATATAGS=1SHOW_FLIGHTPLAN=1SHOW_INTERSECTIONS=1SHOW_JET=0SHOW_NDBS=1SHOW_TERRAIN=1SHOW_VICTOR=0SHOW_VORS=1SHOW_WEATHERSTATIONS=1SHOW_WEATHERSYSTEMS=1show_ac_twr=1show_airways=1show_markers=1show_volume_boundaries=1show_waypoints=1[MULTIPLAYER]condAccoutPassword=0VoiceVolume=0.000000ASE sp2 build 642, FSUIPC4 (registered) v4.648, Radar Contact v4.3.3843, (the following modes selected Play Pilot wav's, Pilot Auto Reply, Interact with AI, Tune on Contact and IR Training) in addition I use both AI chatter and prerecorded chatter), LDS 767300 winglet version, all running in full display mode.With this environment I experience NO slowdown of RC keystrokes or Otto responses, with the exception when a chatter wav is playing. When Radar Contact ask for destination weather, I get pretty accurate winds and conditions 90% of the time at destination, the other 10% variance is due to AFCADS that utilize the cross-wind option for runway selection. I compare Radar Contact reported weather against my NWC (National Weather Center) forecast metar. I have not done a comparison using the "shift Z" mode.For techncial updates I am going to rely Pete Dowson for FSUIPC logs, however I don't think that Radar Contact logs have anything to relate to ASE or any other weather program to cause a slowdown response. Having said that, I did use just for test purposes the freeware program Open Clouds on my last flight. I got a very accurate forecast when RC requested weather, but the Open Cloud program has other issues which I was not impressed with.If the poster have additional issues or feedback, please share them and one us will get back with you.Bob Johnson
January 8, 201115 yr Hi Bob,Thanks for jumping in on this discussion, you may have me confused with another user, like yourself, I do not experience slow downs.I have an almost identical set up, except I am running W7 64 and nothing related to fsx in program files (x86).My issue was incorrect destination weather, and my discussion with Pete(after confusing the hell out of him) has resolved that by removing UseAse=Yes with DWC.One thing I do that maybe different,certainly different from what Hi Fi recommend, and that is I use Fsuipc to smooth winds to remove "S" turns in payware aircraft like the PMDG MD11, 747 and LvlD 763 when using DWC. The Alternative using Standard mode is not an option for me personally, flickering screen during weather update and stutters. The weather depiction is far more realistic using DWC. And that is why using DWC with RC is important to me.CheersJulian
January 8, 201115 yr Hi all,Just a quick FYI, as of late I have been supplying Pete with repeatable FSUIPC logs recording low-level IPC timing events while ASE is running in DWC mode. As requested, JD now also has matching RC4 debug logs for his own parallel investigation. Lets just wait and see if the issue can finally be put to rest. :( :( Regards, Al Jordan | KCAE
January 8, 201115 yr Hi Bob,Thanks for jumping in on this discussion, you may have me confused with another user, like yourself, I do not experience slow downs.I have an almost identical set up, except I am running W7 64 and nothing related to fsx in program files (x86).My issue was incorrect destination weather, and my discussion with Pete(after confusing the hell out of him) has resolved that by removing UseAse=Yes with DWC.One thing I do that maybe different,certainly different from what Hi Fi recommend, and that is I use Fsuipc to smooth winds to remove "S" turns in payware aircraft like the PMDG MD11, 747 and LvlD 763 when using DWC. The Alternative using Standard mode is not an option for me personally, flickering screen during weather update and stutters. The weather depiction is far more realistic using DWC. And that is why using DWC with RC is important to me.CheersJulianHi Julian, yup did confuse you with Zach on another post. Yes we are all trying to understand the "slowness" issue with ASE, sent JD and Pete a bunch of settings to hopfully identify what folks are doing that slows there RC responses.All the BestBob
January 8, 201115 yr Hi Julian, yup did confuse you with Zach on another post. Yes we are all trying to understand the "slowness" issue with ASE, sent JD and Pete a bunch of settings to hopfully identify what folks are doing that slows there RC responses.All the BestBobHi Bob,I was getting the slows when I first started using RC4 several weeks ago.( Put it down to new user error) Don't know what I did that changed that. I get cleared to land 3 miles from touch down instaed of halfway down the runway. The only thing I can think of is I changed how DWC (wind smoothing and turbulence values in fsx config) is used in conjucntion with FSUIPC. I suppose even 3 miles might be a bit close for comfort but better than on the runway.CheersJulian
January 8, 201115 yr Bobby or anyone,On Bojote's automated FSX Tweaking & Tuning Service, where does the downloaded FPS Limiter file go?Thanks,zach Digital Storm, Win 7 64-bit, Intel i5 4690k (OC 4.5 GHz), ASRock Z97, FSX Gold,two Dell monitors, 1x Samsung 500GB DDR, PC 8GB DDR3 (1866), RC4, DX10 Fixer,nVidia Inspector tuned by FSX DX10 "How To" Guide, nVidia GeForce GTX 970 (4GB),Opus, GEX, UTX, UT2, REX (4, Soft, Airports) FS Global 2008, PMDG JS41 & 737NGX, 750W Corsair
January 8, 201115 yr Bobby or anyone,On Bojote's automated FSX Tweaking & Tuning Service, where does the downloaded FPS Limiter file go?Thanks,zachHi Zach,Create a folder, example X:\FPS and uncompress the files into the newly created folder. Once you have done that you have set up the batch file (there is instructions for that in the msfs forum) create a short cut for the batch file on your desktop, and run it from there. You need to visit the msfs forum for further info as it has no connection to RC.CheersJulian
Create an account or sign in to comment