marcofa Posted April 10, 2013 Report Share Posted April 10, 2013 I have some problem with 0x3364, 0x3365, 0x0840 . During normal flight they are set to 0. In my case they are alwais set to 2 , also if I crash. I disinstalled version W and installed new version Z. Nothing change. I have software for control loader that dont work because read these values and disengage the power when that data are different to 0. Sorry for writing but there is problem with Enter in this portal. Regards Marco Fantino Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 10, 2013 Report Share Posted April 10, 2013 I have some problem with 0x3364, 0x3365, 0x0840 . During normal flight they are set to 0. In my case they are alwais set to 2 , also if I crash. I disinstalled version W and installed new version Z. Nothing change. I have software for control loader that dont work because read these values and disengage the power when that data are different to 0. Sorry for writing but there is problem with Enter in this portal. Regards Marco Fantino By "W" and "Z" I take it you are talking about FSUIPC3.999? You don't bother to say. FSUIPC never writes "2 to 3364. It is either FF or 00. The 0840 "crashed" flag is set by FS, not by FSUIPC. What do you mean by "there is problem with Enter in this portal"? Show me a log file -- close FS down first. Pete Link to comment Share on other sites More sharing options...
marcofa Posted April 10, 2013 Author Report Share Posted April 10, 2013 Yes 3.999Z. During a normal flight using logging facilities and displaing value on the screen I found 3364=2, 3365=2, and 0840=2 (exadecimal option not selected) I am testing a forcefeedback yoke with software from http://bffsimulation.com/FFB-yoke-1.php but dont work. Ian at BuiltForFun told me that software dont work (for safety) when theses value are set by FS9 different from 0. Where is and how can I save a log file? "Enter" sometime in this portal and only in this portal, enter keyboard button dont work Marco Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 10, 2013 Report Share Posted April 10, 2013 During a normal flight using logging facilities and displaing value on the screen I found 3364=2, 3365=2, and 0840=2 (exadecimal option not selected) Sounds like either some other software is corrupting this, or your registration is bad. I am testing a forcefeedback yoke with software from http://bffsimulation.../FFB-yoke-1.php but dont work. FSUIPC doesn't support force feedback. You'd need to assign in FS for that. Where is and how can I save a log file? FSUIPC always makes a log file, and it is in the Modules folder right next to FSUIPC itself. close FS down first. Paste the complete log fine into a message here. "Enter" sometime in this portal and only in this portal, enter keyboard button dont work Sorry but I've no idea what all that means. What's a "portal" (a door? Which and why?), and what do you mean by a keyboard button not working? You aren't making sense I'm afraid. Pete Link to comment Share on other sites More sharing options...
marcofa Posted April 11, 2013 Author Report Share Posted April 11, 2013 I make the following test: I installed FS9, FS9.1 and FSUIPC on my notebook with Window 7 64 bit I checked values ...ALL = 0 I come back on PC (Window XP 32 bit) where there is a problem I disinstall FS9, deleted all remaining files I reinstalled FS9, FS9.1, and FSUIPC I checked values...ALL = 2 Its a very big mistery I cannot attach logs because I receive the following message for zip and txt files FSUIPC LOGS. You aren't permitted to upload this kind of file How can I send to you logs? Marco Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 11, 2013 Report Share Posted April 11, 2013 How can I send to you logs? The log is a short text file. Just paste its contents into a message here. Pete Link to comment Share on other sites More sharing options...
marcofa Posted April 11, 2013 Author Report Share Posted April 11, 2013 Installer for FSUIPC.DLL version 3.999z Looking in registry for FS9.1 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1 Parameter"EXE Path" Not there, so looking in: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1 Parameter"EXE Path" ... NOT found! ... Looking in registry for FS9 install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0 Parameter"EXE Path" ... >>> OK! FOUND FS9! <<< ... =========================================================== INSTALLATION FOR FS9: EXE Path="C:\Programmi\Microsoft Games\Flight Simulator 9" Checking if there's already a version of FSUIPC installed in: C:\Programmi\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL ... No previous valid version found. Okay -- installed FSUIPC into "C:\Programmi\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL" "Modules\FSUIPC Documents" folder created okay! Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC User Guide.pdf" okay Installed "FSUIPC for Advanced Users.pdf" okay Installed "FSUIPC History.pdf" okay Installed "List of FS2004 controls.pdf" okay Installed "GlobalSign Root.exe" okay Installed "FSUIPC Lua Library.pdf" okay Installed "FSUIPC Lua Plug-Ins.pdf" okay Installed "Lua License.pdf" okay Installed "Lua Plugins for VRInsight Devices.pdf" okay Installed "LuaFileSystem.pdf" okay Installed "Example LUA plugins.zip" okay Installed "SIMSAMURAI+FSUIPC+TUTORIAL.pdf" okay Installed "FSUIPC for Programmers.pdf" okay FSUIPC.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== All installer tasks completed okay! Registration for FSUIPC was successful! (result code 00) *************** End of Install Log *************** [JoyNames] AutoAssignLetters=No 0=BU0836 Interface 0.GUID={C9DC34A0-0133-11D6-8001-444553540000} 1=CH FLIGHT SIM YOKE USB 1.GUID={36634F40-01FD-11D6-8001-444553540000} [General] UpdatedByVersion=3999z WindSmoothing=No AutoTaxiWind=No PropTaxiWind=No TimeSetMode=Partial WhiteMessages=No ThrottleSyncAll=No GraduatedVisibility=No LowerVisAltitude=0 UpperVisAltitude=25000 UpperVisibility=6000 GenerateCirrus=Yes WindShearSharp=No UpperWindGusts=No ExtendMetarMaxVis=Yes CorrectVSsign=Yes MouseWheelTrim=No MouseWheelTrimSpeed=1 BrakeReleaseThreshold=75 AxisInterceptIfDirect=No DontResetAxes=No DisconnTrimForAP=No ZeroElevForAPAlt=No AutoClearWeather=Yes ExtendTopWind=Yes WindSmoothness=5 SmoothPressure=No PressureSmoothness=5 SmoothVisibility=No VisibilitySmoothness=2 MaxSurfaceWind=0 WindLimitLevel=200 WindDiscardLevel=400 WindAjustAltitude=No WindAjustAltitudeBy=2000 MinimumVisibility=0 MaximumVisibilityFewClouds=0 MaximumVisibility=0 MaximumVisibilityOvercast=0 MaximumVisibilityRainy=0 OneCloudLayer=No ThinClouds=No ThinThunderClouds=No CloudThinness=1000 ThunderCloudThinness=10000 CloudTurbulence=No CloudIcing=No WindTurbulence=No SuppressAllGusts=No ExternalOptionControl=Yes AutoTuneADF=No KeepFS98CloudCover=No ShowPMcontrols=No MagicBattery=No RudderSpikeRemoval=No ElevatorSpikeRemoval=No AileronSpikeRemoval=No ReversedElevatorTrim=No StopAutoFuel=No TrapUserInterrupt=Yes NavFreq50KHz=No ClockSync=No SmoothIAS=Yes SetVisUpperAlt=No VisUpperAltLimit=6000 MaxIce=3 MinIce=-1 WindSmoothingDelay=0 WindSmoothAirborneOnly=No LimitWindVariance=No VisSmoothingDelay=0 VisSmoothAirborneOnly=No TrafficControlDirect=Yes SuppressCloudTurbulence=No SuppressWindTurbulence=No SpoilerIncrement=512 JoystickTimeout=20 PollGFTQ6=Yes BlankDisplays=No ZapSound=firework ShortAircraftNameOk=Substring UseProfiles=Yes TCASid=Flight TCASrange=40 TrafficScanPerFrame=10 AxesWrongRange=No AxisCalibration=No CentredDialogue=Yes ShowMultilineWindow=Yes SuppressSingleline=No SuppressMultilineFS=No ClearWeatherDynamics=Yes OwnWeatherChanges=No FixWindows=No FixControlAccel=No WeatherReadInterval=4 MoveBGLvariables=Yes TimeForSelect=4 WeatherReadsFast=No LuaRerunDelay=66 MainMenu=&Modules SubMenu=&FSUIPC ... [JoystickCalibration] AllowSuppressForPFCquad=Yes ExcludeThrottleSet=Yes ExcludeMixtureSet=Yes ExcludePropPitchSet=Yes SepRevsJetsOnly=No ApplyHeloTrim=No UseAxisControlsForNRZ=No FlapsSetControl=0 FlapDetents=No ReverserControl=66292 Reverser1Control=66422 Reverser2Control=66425 Reverser3Control=66428 Reverser4Control=66431 MaxThrottleForReverser=256 AileronTrimControl=0 RudderTrimControl=0 CowlFlaps1Control=0 CowlFlaps2Control=0 CowlFlaps3Control=0 CowlFlaps4Control=0 MaxSteerSpeed=60 [sounds] Path=C:\Programmi\Microsoft Games\Flight Simulator 9\Sound\ Device1=Driver audio principale Device2=SoundMAX Digital Audio [buttons] Buttonrepeat=20,10 [Monitor] Display=2 Monitor0=0,0264,3,0 Monitor1=0,3364,1,0 Monitor2=0,3365,1,0 Monitor3=0,0840,3,0 ********* FSUIPC, Version 3.999z by Pete Dowson ********* Running on Windows Version 5.1 Build 2600 Service Pack 3 Verifying Certificate for "C:\Programmi\Microsoft Games\Flight Simulator 9\MODULES\FSUIPC.DLL" now ... SUCCESS! Signature verifies okay! Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL) User Name="marco fantino" User Addr="neta46@tin.it" FSUIPC Key is provided WIDEFS not user registered, or expired Module base=61000000 WeatherReadInterval=4 LogOptions=00000001 DebugStatus=15 103672 System time = 03/01/2002 20:35:22 103688 C:\Programmi\Microsoft Games\Flight Simulator 9\ 103703 System time = 03/01/2002 20:35:22, FS2004 time = 12:00:00 (00:00Z) 112891 FLIGHTS\OTHER\FLTSIM.flt 113016 AIRCRAFT\c172\Cessna172SP.air 113031 Aircraft="Cessna Skyhawk 172SP" 120891 ERROR: Can't change message filter: functions not available 125344 C:\Documents and Settings\marco\Documenti\File di Flight Simulator\Volo generato da UI.flt 125500 Clear All Weather requested: external weather discarded 148891 Advanced Weather Interface Enabled 337328 WeatherOptions set, now 40003605 (timer=0) 543547 System time = 03/01/2002 20:42:42, FS2004 time = 20:41:00 (04:41Z) 543547 *** FSUIPC log file being closed Memory managed: 0 Allocs, 4659 Freed ********* FSUIPC Log file closed *** ******* Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 11, 2013 Report Share Posted April 11, 2013 I only needed the run time log (FSUIPC.LOG). System time = 03/01/2002 20:42:42, FS2004 time = 20:41:00 (04:41Z) There's the problem. Your computer's date is 3rd January 2002, before FSUIPC3 was ever made and certainly before you purchased your registration, so it looks invalid. Regards Pete Link to comment Share on other sites More sharing options...
marcofa Posted April 11, 2013 Author Report Share Posted April 11, 2013 Thank you Pete. Its an old PC that I restart. I will change the battery. Anyway , data problem effect is wrong value in FSUIPC? Marco Link to comment Share on other sites More sharing options...
Pete Dowson Posted April 11, 2013 Report Share Posted April 11, 2013 Thank you Pete. Its an old PC that I restart. I will change the battery. Anyway , data problem effect is wrong value in FSUIPC? Marco A bad registration is treated as a pirated use of FSUIPC and causes deliberate bad data. If you remove the FSUIPC KEY file from the Modules folder then it will appear okay, unregistered, and the data will be good, but then you cannot use the User Facilities. The application interface continues to work without registration. Pete Link to comment Share on other sites More sharing options...
marcofa Posted April 11, 2013 Author Report Share Posted April 11, 2013 Thank you Pete after changing battery and updating time all work well!!! Regards Marco Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now