edpatino

Found it!, sorry. But it was Ok, not in "file".

Sorry for the question, but where I can find the codec parameters panel?. Thanks, Ed

Got it, thanks!. Everything works fine for me, except this feature. Will try according to your steps. Nice utility, much needed to enjoy MSFS much more. Thanks again, Ed

I have the same issue when using the VideoCam button in the main interface (similar error message). Additionally, in "Options" I cannot change the FPS dropdown menu from 60 to any other different value, it seems fixed to 60. Would you mind explaining in more detail the steps needed to properly use the VideoCam button to record a video in mp4 format?. Thanks, Ed

I can see why you don't have any issues with performance. Good system, you should be happy with it. Thanks, Ed

I tend to agree that low FPS could be something related to system configuration and hardware. Anyway, since you mention you don't have issues with performance, could you please post your system specs?. Thanks in advance. Cheers, Ed

I'm interested to buy this set of aircraft for P3Dv4 (and future P3D5), but after looking at these reports about low FPS I'm doubtful about purchasing. Wouldn't be easier for Feel There to provide an alternate set of low-res textures to install in place of the HD-res in case someone is experiencing a negative impact on FPS?. I'll put my purchase on hold until further notice. Cheers, Ed

No, regretfully you're not getting my point. I do like the updates, in fact I love them, but prefer those which don't cause crashes of the sim, that's all. If you look at the different forums about people complaining about sim CTDs (FSDT, Avsim, ChasePlane, to mention only a few) that they thought were caused by other applications and that at the end were caused by the single FSUIPC module, you'll see my point, and this is just an opinion from a customer, right?. On Avsim I even helped at least two people that were having CTDs because of their installed versions of FSUIPC, and had no clue at all about what was happening, and at the end they went back to a previous FSUIPC version and no more CTDs. If you don't mind, I would still suggest to separate the places where people could download the latest and stable version of FSUIPC, from the places where people can find the trial versions, and do just that: Test. If you already have separated places for that, please confirm if it's at Schiratti.Com (latest version there is from Jan. 26th.). Thanks. Ed

I'm still with FSUIPC v4.962 and not willing of having CTDs anymore. I suggest keeping FSUIPC as stable as possible, in these times where it's difficult to keep up with all the updates that are coming up almost daily, apart from the hotfixes of P3Dv3.4. Cheers, Ed

Thanks, Pete. Ok, taken. Cheers, Ed

Ok, changed my glasses and now found it right away. Thanks!. Regarding the VAS display, don't really like to populate everything with lots of numbers like FPS and VAS block, etc. For me, the simplest way it's just fine!. Ok, now the good news!!!: Fired up P3D again on both machines and noticed that now the VAS display takes about half a minute to show (just using the settings on the picture I've sent, and it happens for both PCs). Before the v4.962 the display came in immediately, I can assure you. Probably, I was already accostumed to its inmediate-display behavior and did not wait enough for it to show. Now, this delay is not bothering me too much, but it has to do with something that had surely changed in the latest version, IMO. Thanks again, Ed

Nothing shown in the title bar. My settings are as follows: Here's my INI file (complete), of one of my two machines (gaming laptop): [General] UpdatedByVersion=4962 History=RFITRU80IGMUC81VRD7SX InitDelayDevicesToo=No Annotate=Yes NewInterceptTextMenu=No UseSystemTime=No UseMidMouseBtn=Yes MouseWheelMove=No MouseWheelTrim=No MouseWheelTrimSpeed=1 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No FixControlAccel=No FixMachSpeedBug=No NewDeleteVehiclesForAES=No AutoScanDevices=Yes AssignJoystickIDs=Yes VisibilityOptions=No OneCloudLayer=No CloudTurbulence=No CloudIcing=No GenerateCirrus=No SuppressCloudTurbulence=No MaxIce=-4 MinIce=-4 UpperWindGusts=No SuppressWindTurbulence=No SuppressWindVariance=No WindTurbulence=No TurbulenceRate=1.0,5.0 TurbulenceDivisor=20,20,40,40 SuppressAllGusts=No MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 SmoothBySimTime=No WindSmoothing=No WindSmoothness=2 WindSmoothAirborneOnly=Yes PressureSmoothness=0 TemperatureSmoothness=0 DisconnTrimForAP=No ZeroElevForAPAlt=No ThrottleSyncAll=No WhiteMessages=No ShowPMcontrols=No SpoilerIncrement=512 MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No ClockSync=No ClockSyncMins=5 ClearWeatherDynamics=No OwnWeatherChanges=No TimeForSelect=4 LoadFlightMenu=No LoadPlanMenu=No PauseAfterCrash=No BrakeReleaseThreshold=75 SaveDataWithFlights=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes EnableMouseLook=No DelayedMouseLookZoom=No AxesWrongRange=No TCASid=Flight TCASrange=40 AxisCalibration=No DirectAxesToCalibs=No ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No AxisIntercepts=No DontResetAxes=No InitDelay=0 GetNearestAirports=Yes LogOptionProtect=Yes OOMcheck=Yes OOMcheckInterval=10 TimeForLuaClosing=1 WeatherReadFactor=2 WeatherRewriteSeconds=1 CustomWeatherModify=No SimConnectStallTime=7 InitialStallTime=10 NormalStallTime=1 LuaRerunDelay=66 Console=No LogReads=Yes PatchSIM1friction=Yes WideLuaGlobals=Yes ThreadAffinityMask=x0 LuaAffinityMask=x0 FSVersionUsed="Lockheed Martin® Prepar3D® v3",3.4.18.19475 SimConnectUsed=3.4.0.0 [JoyNames] AutoAssignLetters=No 0=T.16000M 0.GUID={412FA4D0-D738-11E5-8001-444553540000} 1=Controller (XBOX 360 For Windows) 1.GUID={AE4AC120-B573-11E6-8001-444553540000} [Axes] PollInterval=10 RangeRepeatRate=10 [LuaFiles] 1=Aerosoft_F14AB 2=UC 3=VASWarnings [Buttons] PollInterval=25 ButtonRepeat=20,10 [AutoSave] Next=1 Interval=60 Files=10 SaveOnGround=No AutoSaveEnabled=No [GPSout] GPSoutEnabled=No Port=COM10 Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [GPSout2] GPSoutEnabled=No Port=<none set> Speed=4800 Interval=2000 PosTo6Decimal=No SimModeIndicator=No Sentences= [WideServer] WideFSenabled=Yes AdvertiseService=1 Port=8002 Port2=9002 [Sounds] Path=D:\Lockheed Martin\Prepar3D v3\Sound\ Device1=Primary Sound Driver Device2=Speakers (Realtek High Definition Audio) [Monitor] Monitor0=0,024C,4,0 Display=2 [Traffic Limiter] TrafficLimit=0 AirportPreference=50 GroundPreference=50 NearerPreference=50 [Auto] 1=Lua VASWarnings [Window.LUA display] Docked=7637, 303, 2133, 758 Could you pls indicate where exactly this option should be placed? INI file?, where?. I have not made any changes myself to that INI file, except the addition of a LUA script to obtain warning messages about VAS being under 500 MB (WASWarnings). This LUA script was working Ok all the time, and I have not tested it yet with FSUIPC v4.962, but it worked Ok -with the previous display of VAS remaining- and previuos FSUIPC versions. Hopefully you could find the culprit. This VAS utility is quite good and I'm accostumed to use it. Thanks again, Ed

Hi Pete: There is no display at all. OOMcheck is set to YES. Please know that I have two computers with P3D installed and in both there are no displays of VAS remaining anymore, after updating to v4.962 on both machines. Thanks, Ed

Hi: With the newly released FSUIPC v4.962 the Offset 024C and S32 type, used to display the VAS remaining is no longer working. Do we need to use now different settings?. Thanks, Ed

And, in my case, I'm using P3Dv3.4.18.19475 still, not the new HF3. I've been using FSUIPC for a long time, but this had never happened to me before. Thanks, Ed