-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
LUA function as macro?
Pete Dowson replied to johnor999's topic in FSUIPC Support Pete Dowson Modules
Oh, you mean the use of otherwise unused FS control numbers for other things specific to different add-ons. Actually I was unaware that anything did that until recently when logging events on the PMDG 737NGX. Obviously, even if we knew what some of them did (and of course the 737NGX ones are now documented in their SDK), it wouldn't be possible to name all those correctly in assignment drop-downs, because they could be used differently by all the add-ons that possibly exist now and in the future. Well of course all of those listed in that document are already listed by those same names in the drop down, so I must assume you mean those not so listed, lke those in the PMDG NGX well outside the range of numbers used in FSX. If you don't actually mean that, then I still don't understand. Basically, you are asking for a short cut to avoid editing those numbers, the ones used by add-ons only, in the FSUIPC INI? I honestly hadn't realised anything other than the PMDG 737NGX used this method. I will certainly consider a way of doing what you ask in a future release. Meanwhile it can of course be done via INI editing. Regards Pete -
Sorry, but there is nothing simpler than assigning axes in the way you wish. It's merely a matter of moving them so they are detected and selecting the appropriate action. I really do not understand how you can possibly find it intimidating when you've never even tried it. Simply removing all the other option tabs is a bit pointless when you can simply ignore them. It's a bit like being frightened to use a Swiss Army Knife's bottle opener attachment because you are bemused by the amount of other attachments. Just ignore what you aren't interested in. Pete
-
FSX crashes when 'Free Flight' is selected
Pete Dowson replied to RobD's topic in FSUIPC Support Pete Dowson Modules
Okay. Three things of note. 1. You appear to be using an older version of FSX -- you haven't applied the SP2 update nor installed Acceleration. I will try to set up an install here with just FSX + SP1 here to see if I can see any problem, but I'm not sure when I can do this. Is there any reason you are not updating FSX? There were quite a few SimConnect bugs still before SP2. All my systems are at SP2 level at present. To get back to SP1 I think i'll need to reinstall Windows 7 because uninstalling FSX, espcially SimConnect, merely causes really bad problems. 2. The SimConnect log seems to show that the crash occurs when FSUIPC has received notification of lots of AI Traffic being added, with the last logged item being its very first request for data on an AI aircraft. So another possibility is that the traffic file is corrupted. 3. Is the flight being loaded starting Paused? One of the few last details sent by SimConnect was that the Sim was paused. This is not the same as being stuck loading. [LATER] Okay, I can reproduce the exact same crash in API.DLL when I run FSX with only the SP1 update installed, so there is some compatibility problem there. I'll investigate this tomorrow (getting late here now) Meanwhile I would still strongly advise updating with SP2. [LATER STILL] Okay, I can prevent the crash with SP1 if I set the InitDelay parameter in FSUIPC4.INI to a value which prevents it trying to connect ot SimConnect until FSX is ready to fly. I used InitDelay=30 -- it took less than this to press "Fly Now" and get into the sim, but if it takes longer it still crashes. It's weird, becaise there are no facilities used in SP1's SmConnect which aren't supported and working in SP1, and this is proven by the fact that it runs perfectly ones initialised correctly. So it is a bug in the SP1 SimConnect which causes a conflict when it is initialised whilst the rest of FSX is setting itself up. I've no idea what actions in FSUIPC might be causing this, so it will take some experimentation The actual crash is not in FSUIPC and in fact FSUIPC isn't even in the chain of events leading to the crash, so it is something FSUIPC has set in motion. As the SimConnect log seems to point to AI Traffic data, i'll see if I can delay anything involving that until FS is ready to fly. One of these days I may have to withdraw support for older versions of FSX, they are so buggy it is difficult to avoid these problems whilst still improving FSUIPC. Regards Pete -
FSX crashes when 'Free Flight' is selected
Pete Dowson replied to RobD's topic in FSUIPC Support Pete Dowson Modules
You can if you ZIP them, but best to ZIP them anyway (they compress very well indeed) and send to petedowson@btconnect.com. Pete -
FSX crashes when 'Free Flight' is selected
Pete Dowson replied to RobD's topic in FSUIPC Support Pete Dowson Modules
I honestly don't know any way possible for FSUIPC to be involved in that at all. At a last attempt at seeing what is going on, please get a SimConnect log. there are instructions for that in the FAQ subforum. I am suspecting now that your FSX installation is corrupt. Regards Pete -
Changing a Goflight Pushbutton's offset
Pete Dowson replied to spen25's topic in FSUIPC Support Pete Dowson Modules
Okay. I noticed several typos in my hastily written reply. i've corrected these now, so please review it in case something came over incorrectly. Pete -
FSX crashes when 'Free Flight' is selected
Pete Dowson replied to RobD's topic in FSUIPC Support Pete Dowson Modules
Yes, I would tend to agree. And that's at a point where FSUIPC is not actually doing anything. Okay, so it is looking like a corrupted aircraft. I think the difference with or without FSUIPC installed is misleading -- maybe causing a timing difference or changing the memory layout just sufficiently to make something crash which otherwise might only have created a graphics glitch. If it isn't the aircraft (which appears to be a default FSX one), then I would suspect something else in FSX's setup. As an experiment, just try renaming the FSX.CFG file so that it makes a new default one. Pete -
Changing a Goflight Pushbutton's offset
Pete Dowson replied to spen25's topic in FSUIPC Support Pete Dowson Modules
You are only changing one offset in any case, 9400. You are testing another offset, 66C0, but not changing it. I'll assume you really mean you want the value in the offset to swap between 026C and 026B. Do you know that offset 9400 contains one of those to start with? If so you can just toggle the changed bits -- bits 0,1 and 2 (hex C = 1 1 0 0 and B= 1 0 1 1), so an offset byte togglebits for offset 9400 with a parameter of 7 would do it (7 = 1 1 1) If you don't know the current value then you need to use a button flag, toggling the flag each time you press the button and testing that as the condition. e.g. using the flag for joystick 15 button 0 (which i assume is not a real button on your system): 104=P170,14,C1005,J15B0 ;Toggles flag J15,0 105=CP(+F15,0)170,14,Cx3009400,x0000026C 106=CP(-F15,0)170,14,Cx3009400,x0000026B [/CODE] Regards Pete -
Reregistering FSUIPC4 after each start of FSX
Pete Dowson replied to calspee's topic in FSUIPC Support Pete Dowson Modules
Sounds like a corrupted weather file. Please show me the FSUIPC4.LOG file, from the FSX Modules folder. No, sorry, nothing related to such an old version is of any use to me at all. Regards Pete -
Changing a Goflight Pushbutton's offset
Pete Dowson replied to spen25's topic in FSUIPC Support Pete Dowson Modules
Well, line 104 sets the DWORD at 9400 to 1 but that is then immediately overwritten by one of 0x26C or 0x26B depending on the value of the byte in 66C0. So you might as well delete line 104. What's changing offset 66C0? I'm not sure you understand what "toggle" means -- it means changing one or more bits from 0 to 1 or 1 to 0. It isn't usually applied to values, only bits, like switches. If you want just to toggle something when a button is pushed, why not use the facilities to assign buttons in FSUIPC's button assignments tab? Why are you messing with the INI lines? Toggling is done with commands like Offset byte togglebits and so on. Regards Pete -
Yes. That was what the release of version 4.82 was mainly about, last week. I did announce that earlier in this very thread! Regards Pete
-
FSX crashes when 'Free Flight' is selected
Pete Dowson replied to RobD's topic in FSUIPC Support Pete Dowson Modules
Okay. The point it crashes very stronly suggests a corrupted Weather file. One of the things FSUIPC will be doing once started and FSX is almost ready to fly, is getting the weather data regularly from SimConnect, so it can feed it to applications asking for it. There are a couple of binary files involved in the weather -- the WX file associated with the Flight being loaded, and the WXstationlist file in the same folder as your FSX.CFG file. SimConnect doesn't appear to check these at all and simply loads them up as if they are okay. It's only when something actually ewants access to the data that it crashes. The former can get corrupted if the saved flight file was interrupted or something else happened. The station list can get corrupted by bad data downloads form the FS real weather site. So first, try deleting or removing the WX file associated with the flight being loaded, i.e.YPJT 6L day.WX, identified by the line: If that doesn't fix it, try replacing the WXstationlist with the default one found in FSX's weather folder. Regards Pete -
FSUIPC Commercial-Use License, EULA?
Pete Dowson replied to ShelbyJ's topic in FSUIPC Support Pete Dowson Modules
There is no published EULA as such. It was free for all uses whilst I was still earning or regular salary from other work, and only became payware when that source dried up. Otherwise I couldn't have continued. Because the use of FSUIPC varies so enormously from one commercial user to another I found it best to discuss needs and do deals separately with each one. The use of FSUIPC to extract an aircraft position for display on a map in a shareware utility program, for example, is far less than that for a full blown commercial training cockpit. And there's a lot of difference between folks who are charging something for their shareware software in order to recoup costs and larger companies making a profit from selling goods or software using FSUIPC. From what you have said I'd not be unhappy for you to continue without any other agreement than my permission, which you have now, but if you do make yourself a tidy fortune please be sure to remember me! ;-) And thank you for being so considerate to ask -- many do not. Regards Pete -
IYP & PM Systems help
Pete Dowson replied to andrew 737's topic in FSUIPC Support Pete Dowson Modules
That's okay. Can you let Robert Cesar know you are okay-ish now please? He copied me because he's a bit lost in this area, and could do with reassurance i think! Regards Pete -
IYP & PM Systems help
Pete Dowson replied to andrew 737's topic in FSUIPC Support Pete Dowson Modules
What sort of voice commands? I've never used IYP to fly the 'plane, only Project Magenta. IYP will set the MCP values for you. I'm not sure how pmSystems comes into it. What voice commands are you using for that? I fly 737NG and of course the overhead, which is pmSystems' province, is all toggle switches, not buttons, so cannot be remote-controlled. I use IYP primarily to provide spoken checklists, and voice contact to Radar Contact. I do occasionally use it to set things like the transponder code, radio frequencies, and MCP / QNH settings when things get too busy for one pilot. Also I use it to get and speak the weather. But never anything which involves actual toggle switches because they'd get out of sync with the sim. Regards Pete -
FSX crashes when 'Free Flight' is selected
Pete Dowson replied to RobD's topic in FSUIPC Support Pete Dowson Modules
You posted your support request to the "User Contributions" subforum, for some reason. I've moved it to the Support Forum, or it won't get answered. FSUIPC knows nothing of that menu and isn't involved. What makes you think your problem is related to FSUIPC? If you still think it is, please show me the FSUIPC4.LOG file which you will find in the FSX Modules folder. Regards Pete -
FSUIPC 4.82 and LINDA/LUA
Pete Dowson replied to Delta14Sierra's topic in FSUIPC Support Pete Dowson Modules
Well, that's totally unhelpful. I've never seen one like that before -- not even knowing which module crashed! Are there no others with decent information? Good grief! 16 different plug-ins all trying to start at the same time? Okay, so now please get the log I requested a while ago, wqith all those other entries commented out and only the Linda one loading. First, though, UNCHECK the separate Lua logging option and CHECK the Lua trace option instead. The logging will go to the main FSUIPC log. Zip it up along with Linda.lua and send it as requested earlier. Regards Pete -
fout in installation path
Pete Dowson replied to Orion's topic in FSUIPC Support Pete Dowson Modules
I still believe you have that message incorrect as there isn't one like that. Why not show me the actual installer log as I asked? It would save a lot of time! If the FSUIPC installer cannot find FS then it will ask you to select the correct path. You select it in the explorer-type window which will appear -- just follow the instructions it gives you. If you cannot find the Install FSUIPC.exe program in the downloaded FSUIPC Zip file then you have downloaded the worng package! You MUST use the Installer. If you are not running the installer, what on Earth ARE you running which gives you these strange unknown messages? If FS9 won't start are you sure you've installed it? If you've not yet installed FS9 then you cannot uinstall FSUIPC into it in any case!!! Pete -
FSUIPC and Phidgets card etc. etc.
Pete Dowson replied to freddehboy's topic in FSUIPC Support Pete Dowson Modules
FSUIPC is not a hardware driver. It scans inputs from joystick type devices, as recognised by FS, and also from GoFlight, using their driver. No others directly. USB HID devices can be supported via Lua plug-ins, but otherwise you need to look to the card maker for a driver. Regards Pete -
FSUIPC 4.82 and LINDA/LUA
Pete Dowson replied to Delta14Sierra's topic in FSUIPC Support Pete Dowson Modules
Just click the Start button in Win7, and type "events", and Enter. The Event Viewer will appear. Select Windows Logs then Application. Scroll down the list of application events which will appear until you find an "Error" level one with "Application Error" listed as the Source. Look through those until you find the Faulting application identified as FSX.EXE. If you know the date and rough time of the last one you can find it quickly as that is displayed too. In the details there will be the faulting module name, offset and excepption code. Or just select al the displayed details and copy/paste into a message here. Pete -
Tried it here. Works fine with the default FSX 738. Here are extracts from a log using FSUIPC 4.82 with 0B54 monitored to the log and Lua tracing enabled before loading your Lua: This is the loading of the aircraft and starting the Lua, up until the cold/dark aircraft is ready to have the APU started: ********* FSUIPC4, Version 4.82 by Pete Dowson ********* ... 7969 E:\FSX\SimObjects\Airplanes\B737_800\Boeing737-800.AIR ... 119485 LUA.0: beginning "E:\FSX\Modules\apu.lua" 119485 LUA.0: E:\FSX\Modules\apu.lua:12 119500 LUA.0: Global: ipcPARAM = 0 119500 LUA.0: E:\FSX\Modules\apu.lua:2 119516 LUA.0: E:\FSX\Modules\apu.lua:14 119532 LUA.0: Waiting for an event in "E:\FSX\Modules\apu.lua" 119532 LUA.0: Offset Change event: calling "APU" in "E:\FSX\Modules\apu.lua" 119532 LUA.0: E:\FSX\Modules\apu.lua:3 119532 LUA.0: Local: offset = 2900 119547 LUA.0: Local: value = 0 119547 LUA.0: E:\FSX\Modules\apu.lua:4 119563 LUA.0: Global: model = 2 119563 LUA.0: E:\FSX\Modules\apu.lua:5 119578 LUA.0: Global: unit = 0 119578 LUA.0: E:\FSX\Modules\apu.lua:6 119594 LUA.0: Global: id = 1 119594 KEYUP: VK=9, Waiting=0 119610 LUA.0: E:\FSX\Modules\apu.lua:7 119610 LUA.0: E:\FSX\Modules\apu.lua:10 119625 LUA.0: E:\FSX\Modules\apu.lua:12 119641 LUA.0: Waiting for an event in "E:\FSX\Modules\apu.lua" [/CODE] [size=5][font=arial,helvetica,sans-serif]Now here is the APU spooling up (there's a lot of logging here as you can imagine, so I'll just show the beginning, and ending where the value finally goes over 99.0%:[/font][/size] [CODE] 145953 Monitor IPC:0B54 (FLT32) = 0.71267867 145953 SimRead: 0B54="APU PCT RPM" FLT64: 0.712678550207 145953 LUA.0: Offset Change event: calling "APU" in "E:\FSX\Modules\apu.lua" 145953 LUA.0: E:\FSX\Modules\apu.lua:3 145969 LUA.0: Local: value = 0.71267867088318 145969 LUA.0: E:\FSX\Modules\apu.lua:4 145969 Monitor IPC:0B54 (FLT32) = 1.37349093 145969 SimRead: 0B54="APU PCT RPM" FLT64: 1.37349057081 145985 LUA.0: E:\FSX\Modules\apu.lua:5 145985 LUA.0: E:\FSX\Modules\apu.lua:6 146000 Monitor IPC:0B54 (FLT32) = 2.60532713 146000 LUA.0: E:\FSX\Modules\apu.lua:7 146000 SimRead: 0B54="APU PCT RPM" FLT64: 2.60532617682 146016 LUA.0: E:\FSX\Modules\apu.lua:10 146032 LUA.0: E:\FSX\Modules\apu.lua:12 ... 182094 Monitor IPC:0B54 (FLT32) = 98.96405029 182094 SimRead: 0B54="APU PCT RPM" FLT64: 98.9640051778 182094 LUA.0: E:\FSX\Modules\apu.lua:5 182110 LUA.0: E:\FSX\Modules\apu.lua:6 182125 LUA.0: E:\FSX\Modules\apu.lua:7 182125 Monitor IPC:0B54 (FLT32) = 98.97804260 182125 SimRead: 0B54="APU PCT RPM" FLT64: 98.9780432637 182125 LUA.0: E:\FSX\Modules\apu.lua:10 182141 LUA.0: E:\FSX\Modules\apu.lua:12 182157 LUA.0: Offset Change event: calling "APU" in "E:\FSX\Modules\apu.lua" 182157 LUA.0: E:\FSX\Modules\apu.lua:3 182157 Monitor IPC:0B54 (FLT32) = 98.99060822 182157 SimRead: 0B54="APU PCT RPM" FLT64: 98.9906165059 182157 LUA.0: Local: value = 98.978042602539 182172 LUA.0: E:\FSX\Modules\apu.lua:4 182172 LUA.0: E:\FSX\Modules\apu.lua:5 182188 LUA.0: E:\FSX\Modules\apu.lua:6 182203 LUA.0: E:\FSX\Modules\apu.lua:7 182203 Monitor IPC:0B54 (FLT32) = 99.00544739 182203 SimRead: 0B54="APU PCT RPM" FLT64: 99.0054480489 182203 LUA.0: E:\FSX\Modules\apu.lua:10 182219 LUA.0: E:\FSX\Modules\apu.lua:12 182235 LUA.0: Offset Change event: calling "APU" in "E:\FSX\Modules\apu.lua" 182235 LUA.0: E:\FSX\Modules\apu.lua:3 182235 Monitor IPC:0B54 (FLT32) = 99.02178955 182235 SimRead: 0B54="APU PCT RPM" FLT64: 99.0218054708 182235 LUA.0: Local: value = 99.005447387695 182250 LUA.0: E:\FSX\Modules\apu.lua:4 182250 LUA.0: E:\FSX\Modules\apu.lua:5 182266 LUA.0: E:\FSX\Modules\apu.lua:6 182266 Monitor IPC:0B54 (FLT32) = 99.03430939 182266 SimRead: 0B54="APU PCT RPM" FLT64: 99.0343176779 182282 LUA.0: E:\FSX\Modules\apu.lua:7 182282 LUA.0: E:\FSX\Modules\apu.lua:8 182297 Monitor IPC:0B54 (FLT32) = 99.04635620 182297 LUA.0: E:\FSX\Modules\apu.lua:12[/CODE] Note that the timing of the Monitor and the calling to the Lua thread is a little skewed so it isn't exactly the same value or time -- okay within a few hundred millisecs though. Perhaps you should do the same sort of thing, monitor the value and trace your Lua code. You'll see, above, that once the value is seen, in the Lua, as being over 99%, your line 8 is executed as shown by [CODE] 182282 LUA.0: E:\FSX\Modules\apu.lua:8[/CODE] I did this without a GF unit attached, but what would worry me about your code is this: The value you are acting on is changing all the time whilst the APU is starting, and even afterwards. Your function is being called at a rate of about 15-20 times per second all that time. So you are sending "SetBright" and either "SetLight" or "ClearLight" to the GoFlight driver that often. Maybe that doesn't cope? Anyway, it is very ineffiicent. Try a slim line version only sending changes when changes are needed. That's good practice in ALL coding. e.g.: [CODE] -- monitor APU status and turn LED on if ON gfd.SetBright(GFP8, 0, 1) apuon = false function APU(offset, value) if value > 99 and not apuon then apuon = true gfd.SetLight(GFP8, 0, 1) else if value <= 99 and apuon then apuon = false gfd.ClearLight(GFP8, 0, 1) end end event.offset("0B54", "FLT", "APU") [/CODE] Regards Pete
-
fout in installation path
Pete Dowson replied to Orion's topic in FSUIPC Support Pete Dowson Modules
Sorry, I still don't understand! What, exactly, says "cannot find the given path"? That isn't a message in the FSUIPC installer. If it cannot find FS9 by itself it asks you to with a folder selection display saying: "FS2004 not found! Please locate and 'open' FS9.EXE:" So, I think you must be running some other program entirely. Who or what is giving which program a path? You should be running "Install FSUIPC.EXE", in Administrator mode, as described in the Instructions provided. If you run this you will see a Windows with all of the progress information scrolling as it finds everything and installs it. That is the Log. That tells me everything I need to know. If it is not being placed in your FS Modules folder, then you can use the "file" menu item to save the log wherever you like. Pete -
Make a Goflight LED Blink or Flash
Pete Dowson replied to spen25's topic in FSUIPC Support Pete Dowson Modules
That was quick! Your test crossed with some other improvements I added, editing the last message again and the original code. Please re-check. Regards Pete -
Make a Goflight LED Blink or Flash
Pete Dowson replied to spen25's topic in FSUIPC Support Pete Dowson Modules
Sorry, I didn't finish it properly in my haste. In the FLASH function you will need to set "light = true" when you turn it on and "light=false" when you turn it off. Obviously without the condition it is testing there changing it is not doing anything different on each timer event. If you want the LED to come on immediaely, that needs doing in the original function, along with "light = true". Additionally the "SetBright" line only needs executing once, so you can put that right at the beginning, outside of the functions. I've edited the original. Pete -
Reregistering FSUIPC4 after each start of FSX
Pete Dowson replied to calspee's topic in FSUIPC Support Pete Dowson Modules
Much better and easier to tell me the version number -- 4.82 is the latest version. What is yours? I think you must be misinterpreting the symptoms somehow. All registration does is create a KEY file in your FSX Modules folder. Once that is created it never needs to be created again uness you delete it. There is absolutely nothing else involved in registration with any recent version of FSUIPC4. Additionally I do not know of any radar gauge which needs a registered version of FSUIPC4, which makes me even more convinced that registration is nothing to do with it -- unless, that is, there is actualy something wrong with the registration, or something that makes it look wrong. One thing which will do that is forgetting to set the correct date on your PC -- any date set before your purchase date will make the registration look invalid. You can also check whether it is a bad registration by removing the KEY file so that FSUIPC runs unregistered. Re-installing FSUIPC4 merely replaces the FSUIPC4.DLL itself, and instals the documentation again, so that too cannot affect this -- re-installation never touches any of your settings in the INI file and any macro or Lua files you may have. So again, it cannot be that which is making any difference. I think you have something else going on. Maybe it's an FS9 gauge you are using in FSX? That is known to be troublesome. If you need more help on this I will need to see the FSUIPC4 logs -- one from an "ok" session and one from a failed session. Make sure FSX is closed down first for each. You can paste the files in a message here. Regards Pete