Jump to content
The simFlight Network Forums

Andydigital

Members
  • Posts

    1,227
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Andydigital

  1. The way I understand it is that it disables the AXIS on your trim wheel when you have the Auto Pilot engaged. i.e. you can move the axis as much as you want while the AP is engaged but it won't alter the planes elevator trim. It won't stop it getting out of sync though and that is one of the reasons why I didn't bother buying one of those nice looking Saitek Trim wheels, I could foresee this sync problem arising so I'm glad I didn't waste my money for a change, lol. Profiles are assigned to the aircraft by you in the FSUIPC GUI, if you want to remove an aircraft from a specific profile then you have to remove it manually by editing the relevant profile section of the FSUIPC.ini by deleting the aircraft from the list. See the example below of the aircraft that are included in my Profile called "GA". To remove an aircraft I have to completely delete one of the numbered lines. I also make sure the numbered lines are in sequence after I have deleted one, whether this is needed or not I am not sure. [Profile.GA] 1=C Skylane 182Q6 2=C Skylane II RG R182 3=American Champion Scout FSX Red with Black 4=American Champion Citabria FSX Red and White 5=Beech Baron 58 6=Cessna Skyhawk 7=jfarcher_FR3 8=C337 Skymaster[/CODE] I think Pete did mention at one point that he was thinking of adding a way of removing an aircraft from an existing profile (via the GUI), although I'm not sure if this has already been implemented or not, (sorry if it has Pete) its been a while since I used FS never mind assigned a new aircraft to a profile.
  2. For the iFly you need to go to the official support forum and register your product to get support. Once thats done visit the hardware support forum section and you will be able to download a tool that will let you use practically every single switch, button, LED and gauge output through FSUIPC and link it to your hardware if its compatible.
  3. He is using 4.587 look at the error log above ;) Edit: Ninja'd by Dan
  4. The door animations go crazy too if you try to open a door when in the refuelling box, the door starts to open then immediately slams shut and the sound of a door closing plays over and over again every second or two until you reload the aircraft.
  5. The trigger for refuelling is to be within the bounding box, which can sometimes encroach on to stands either side of the fuelling stand and the aircraft has to come to a complete stop. As far as I remember it doesn't matter if the parking brake is on or not and it will still refuel if the engines are running. Yet more illogical logic from MS.
  6. If you have any anti virus software installed check the security logs in it, maybe for some strange reason it thinks makerwys.exe malicious and its quarantining/deleting it.
  7. I just thought it was strange that neither yourself or Leo said anything at all in reply to my post, because doing what I suggested takes no time at all to confirm. Basically it seems the lua interpreter doesn't really read any further than .lua when seeing a file name and ignores whatever comes after it. Either that or it's something strange in Artems implementation of LINDA.
  8. Did you miss my earlier post or are you both just ignoring me, lol. It could just be a simple bug.
  9. Make sure you don't have two files with the same name but a different extension, I noticed something odd like this with LINDA last week, I was having problems with Linda loading and Artem informed me from the log I sent him it appeared as if a script was being loaded twice. For example I had a couple of files named similar to the below in the same folder; Fallback.lua Fallback.lua.org When updating files I always leave the original file in place and simply rename it .org until I'm sure the new one works properly. When I did this recently with one of Linda's lua's it caused an error with an almost identical error in the log to yours Leo. Try moving any duplicate back up files like mentioned above to a completely different place and see if that helps.
  10. Click on the link below which takes you to the post Pete mentioned above, then read the contents of the post so you may follow the instructions contained within it which will hopefully fix your problem.
  11. There is a bug in FSX where doors can open and close constantly after executing the door command when you are near a fuel trigger point, simply move away from the refuelling stand and the bug goes away.
  12. You have to set up new profiles and new macros for every single variant, so that's like it's seven different aircraft in total.
  13. Unfortunately iFly do use separate gauges for each variant of the 737 so you will have to build macros for each one.
  14. The should just give you the full licence and have done with it, you provide a service they couldn't hope to match in a decade of development. I got an academic licence as I am using it in an educational manner.
  15. Release notes are here; http://www.prepar3d.com/wp-content/uploads/2012/08/Release_Notes_for_Prepar3D_1.4.pdf
  16. I don't think a lot has changed to be honest, they do mention a g3d fix though, the logs are below. Install; Installer for FSUIPC4.DLL version 4.85 Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... Looking in registry for ESP install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0 Parameter"SetupPath" Not there, so looking in: HKEY_CURRENT_USER\ESP Parameter"AppPath" ... NOT found! ... Looking in registry for Prepar3D install path: HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D Parameter"SetupPath" ... >>> OK! FOUND Prepar3D! <<< ... =========================================================== INSTALLATION FOR FSX: SetupPath="E:\Microsoft Games\Microsoft Flight Simulator X" Checking version of FSX.EXE: ... Version 10.0.61637.0 (Need at least 10.0.60905.0) Checking compatibility with installed SimConnect: Found SimConnect build 60905 (Original) Found SimConnect build 61242 (SP1 May07) Found SimConnect build 61259 (Acc/SP2 Oct07) Checking if there's already a version of FSUIPC4 installed in: E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL ... Version 4.850 found. FSX Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Andy\AppData\Roaming" Now finding \Microsoft\FSX\FSX.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Andy\AppData\Roaming" Found FSX.CFG in "C:\Users\Andy\AppData\Roaming\Microsoft\FSX\FSX.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Default\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No FSX.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No FSX.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX 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 "Offset Mapping for PMDG 737NGX.pdf" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== INSTALLATION FOR Prepar3D: SetupPath="E:\Prepar3D\" Checking version of Prepar3D.EXE: ... Version 1.4.4747.0 (Need at least 1.0.677.0) !! WARNING !! This version of Prepar3D is later than any known by this FSUIPC4. There may be problems. Please check for a later version of FSUIPC4! Checking if there's already a version of FSUIPC4 installed in: E:\Prepar3D\Modules\FSUIPC4.DLL ... Version 4.850 found. Prepar3D Modules folder already exists. Okay -- installed FSUIPC4 into "E:\Prepar3D\Modules\FSUIPC4.DLL" Looking for the current user's Application Data path: ... found as "C:\Users\Andy\AppData\Roaming" Now finding \Lockheed Martin\Prepar3D\Prepar3D.CFG for all users, including this one Looking in "C:\Users\All Users\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Andy\AppData\Roaming" Found Prepar3D.CFG in "C:\Users\Andy\AppData\Roaming\Lockheed Martin\Prepar3D\Prepar3D.CFG" Now checking DLL.XML ... ... There is a previous DLL.XML, checking for FSUIPC4 section. ... FSUIPC4 section already exists but will be replaced. (for FSUIPC4, without Loader) ... FSUIPC4 section of DLL.XML written okay Now checking for a SimConnect.XML file ... ... No SimConnect.XML file found. This is okay. Looking in "C:\Users\Default\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Default User\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\Public\AppData\Roaming" ... No Prepar3D.CFG there Looking in "C:\Users\UpdatusUser\AppData\Roaming" ... No Prepar3D.CFG there "Modules\FSUIPC Documents" folder already exists. Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder: Installed "SimConnectP3D.dll" okay Now installing additional files into the "Modules\FSUIPC Documents" folder: Installed "FSUIPC4 User Guide.pdf" okay Installed "FSUIPC4 for Advanced Users.pdf" okay Installed "FSUIPC4 History.pdf" okay Installed "List of FSX 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 "Offset Mapping for PMDG 737NGX.pdf" okay FSUIPC4.DLL installed and signature checked out okay! Deleted GlobalSign Root fix program ... no longer relevant =========================================================== All installer tasks completed. Registration for FSUIPC4 was successful! (result code 00) *************** End of Install Log ***************[/CODE] fsuipc.log [CODE] ********* FSUIPC4, Version 4.85 by Pete Dowson ********* Running inside Prepar3D on Windows 7 Module base=54A20000 User Name="xxx" User Addr="xxx" FSUIPC4 Key is provided WideFS7 Key is provided 624 System time = 24/08/2012 17:17:05 624 FLT UNC path = "\\ANDY-PC\Users\Andy\Documents\Prepar3D Files\" 640 Trying E:\Prepar3D\Modules\SimConnectP3D.dll 640 Found it: trying to connect 718 FS UNC path = "E:\Prepar3D\" 1373 LogOptions=00000000 00000011 1373 Wind smoothing fix is only partially installed 1373 SimConnect_Open succeeded: waiting to check version okay 1373 Trying to use SimConnect Prepar3D 1404 VRI port 1 "com4" opened 2371 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 2387 Running in "Lockheed Martin® Prepar3D®", Version: 1.4.4747.0 (SimConnect: 1.4.0.0) 2387 Initialising SimConnect data requests now 2387 FSUIPC Menu entry added 2403 Ready Flags: Ready-To-Fly=N, In Menu=Y, In Dlg=Y 2403 \\ANDY-PC\Users\Andy\Documents\Prepar3D Files\Previous Flight.flt 2403 C:\Users\Andy\Documents\Prepar3D Files\\VFR Barton to Woodford.PLN 2403 E:\Prepar3D\SimObjects\Airplanes\Carenado Skymaster 337\C337.AIR 2403 C:\Users\Andy\Documents\Prepar3D Files\\VFR Barton to Woodford.PLN 3120 VRI MCP2B ("MCP2 Boeing") detected on port com4 30717 Ready Flags: Ready-To-Fly=N, In Menu=N, In Dlg=N 31497 System time = 24/08/2012 17:17:36, Simulator time = 17:17:08 (16:17Z) 31746 Starting everything now ... 31762 LUA.0: beginning "E:\Prepar3D\Modules\ipcReady.lua" 31762 LUA.0: ended "E:\Prepar3D\Modules\ipcReady.lua" 31778 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 31778 LUA.1: 31778 LUA.1: [INIT]LINDA:: Loading... 31871 LUA.1: LINDA:: Aircraft: C337 Skymaster RED 31871 LUA.1: LINDA:: Aircraft module detected: Carenado Skymaster 337 31902 LUA.0: LINDA:: AivlaSoft library loaded... 31918 LUA.0: LINDA:: FSX standard library loaded... 31918 LUA.0: LINDA:: IAO library loaded... 31918 LUA.0: LINDA:: RealityXP library loaded... 31934 LUA.0: LINDA:: A2A MAP library loaded... 32854 Advanced Weather Interface Enabled 36458 LUA.0: LINDA:: Loading a fallback joysticks config... 36473 LUA.0: LINDA:: Loading Carenado Skymaster 337 joysticks config... 36473 LUA.0: LINDA:: Module: Carenado Skymaster 337 Started... 36473 LUA.0: LINDA:: Ready to go, Captain! 36473 LUA.0: LINDA:: 133085 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 133085 Sim stopped: average frame rate for last 102 secs = 39.6 fps 135253 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 138825 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 193707 Ready Flags: Ready-To-Fly=Y, In Menu=N, In Dlg=N 199915 Ready Flags: Ready-To-Fly=Y, In Menu=Y, In Dlg=Y 212349 System time = 24/08/2012 17:20:37, Simulator time = 17:19:00 (16:19Z) 212349 *** FSUIPC log file being closed Average frame rate for running time of 112 secs = 39.6 fps Memory managed: 80 Allocs, 80 Freed ********* FSUIPC Log file closed *********** [/CODE] The FSControls list in the drop down menus appear to be fully populated too, although I can't be 100% certain of this. No idea on Macros as I don't have anything installed that is amenable to them anyway, its a very fresh install, I only got P3D two days ago. Wind smoothing does mention only a partial install. g3d.dll isn't mentioned at all in the log as far as I can see. Apart from the profiles bug I've not noticed anything else amiss so far.
  17. Yes 1.4 works, I got a warning from FSUIPC saying that it didn't know about version 1.4 of P3D but it loaded ok once I accepted the warning. 1.4 was released on the 20th. I'm slowly but surely going to move across to P3D and once RealityXP get their arse in gear and get there GNS product working in P3D I'll probably not use FSX anymore.
  18. LINDA doesn't recognise the MCP-A (FCU/Airbus) panel, the only VRi devices LINDA will work with is the original MCP and the MCP2B. So yes the VSPE, FSUIPC and the VRi software are your only options at this time.
  19. Turn off your anti virus software or put the FSX folder structure in an exclusion. Also search the FSUIPC forum for terms like NGX, FREEZE or PAUSE during Autosave and you will find more details of the issue, it's been covered a few times here and at the AVSIM forum.
  20. Yes profiles are busted at the moment, the easiest way to get it working again at the start of a new session is to open the FSUIPC GUI and select the buttons and switches tab or Axes tab and click on the "reload all buttons" err..... button, lol.
  21. You need to use something like key2mouse. You will find it here. http://www.wideview.it/
  22. Please don't ask the same question more than once in the same forum (cross post), it is not good form and will not get your question answered any quicker.
  23. FSUIPC 4.484 is very old are you sure you mean that version? If you really are using that version then you need to update first. Pete is away for a few more days yet so don't expect a reply until later in the week. You should also see this post below in the FAQ section of the FSUIPC forum.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.