-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
Can't register - bought in 2003
Pete Dowson replied to pylon101's topic in FSUIPC Support Pete Dowson Modules
The latest is actually 3.998r, but the latest installer in 3.998q. If you don't see the 'q' please download the smaller 3.998r Zip from Download Links subforum, unzip it and copy it into the FS Modules folder. Once is enough. Have you checked the date your computer is set to, as I asked? Is there an FSUIPC.KEY file in the FS Modules folder, and if so are the details inside it correct? (It is a text file, you can view it in notepad). Can you ZIP it up and email it to me so I can check it here? petedowson@btconnect.com Regards Pete -
Can't register - bought in 2003
Pete Dowson replied to pylon101's topic in FSUIPC Support Pete Dowson Modules
"Latest" doesn't really mean anything. What version number? What is the symptom? You need to explain more I'm afraid. The registration system has not changed, ever. It is only now performed by the installer instead of in FS because FS normally doesn't have enough privileges. The likes of Vista and Windows 7 forced changes on all of us. Your FSUIPC3 key is valid forever, for all versions of FSUIPC3 (but not FSUIPC4 of course). I would most certainly do so if I could, but at present I don't have enough information. Did you run the Installer 'as administrator', as instructed? What exact version number of FSUIPC? Is the date on your PC set correctly? What is the symtom of the problem -- it your key rejected, or is it just that FS still says you aren't registered? Are you using the exact same name and email as you did in 2003 as you must? Regards Pete -
It's assigned that way by default in FS, so I'm not sure why you'd bother to override it in FSUIPC in any case. Regards Pete
-
Actually, reading Andy's reply, it could be that the anti-virus checker is having more difficulties and causing the longer pause simply because of the difference in privilege levels. I don't have a virus checker continuously active on files local to the PC, only on those downloaded from the Internet. Regards Pete
-
FSUIPC Client DLL for .NET - Version 2.0
Pete Dowson replied to Paul Henty's topic in FSUIPC Client DLL for .NET
Not sure why this is in this thread -- you'd be better off posting (with a new title) in the Support Forum. Why not simply have it written to one of the offsets 3BA8-3BC6 (eg 3BBE is for elev trim)? Then FSUIPC will automatically scale it, and you can assign it and calibrate it in FSUIPC as for any other axis. If you did want to scale it yourself, and use it without any calibration options directly to the elevator trim control, then to get -16384 to +16383 from a range of 0-1024 you'd need to do newval = (oldval * 32) - 16384 and check for +16384 afterwards and change that to 16383. I don't know where you get a multiplier of 128 from!? Regards Pete -
Hmmm. Strange. I wonder why having it in Admin mode causes a delay? I can't think of a reason for that at all. If the NGX saves its panel state into a folder inside the FSX folders, and you have FSX installed into the Program Files folder, then you may need to change the permissions on that folder. To do this you'll need to run Windows Explorer "as administrator" in order to get enough privilege. If this is the problem it is very amiss of PMDG to do it like that and not automatically change the permissions -- after all they don't have the excuse that Vista and Windows 7 weren't around when they were developing the software. FSUIPC's installer makes the Modules folder user-writable when installing FSUIPC explicitly so that the FSUIPC logs and user plug-ins and INI changes can be saved there, else it would have been in the same boat. Generally, because there are so many FS add-ons which are not really Vista and Win7 compatible, it is better to install FS in its own folder, not allow it to install in its default place. However, once done it is too late and more damage can be done (mainly to SimConnect) in trying to uninstal it to move it -- FSX's uninstaller doesn't do a complete job and can leave the SimConnect part unusable. Regards Pete
-
Yes, using the Joystick Lettering facilities. That is why it is there. See the section in the user guide entitled "Keeping track of multiple control devices" -- it is actually listed in the contents on the second page so it isn't hard to find, and it has been available for quite a while now (since February 2009 in fact). Regards Pete
-
FSUIPC in COMBO II BOEING
Pete Dowson replied to sudqui's topic in FSUIPC Support Pete Dowson Modules
I don't know that. Is it working through VSPE okay? I do not have the new MCPs at all so I can not test. All I did was add the commands as listed by andy. I think you need to ask him. You said you had 3.998, but the latest is 3.998q. Perhaps you should do some logging. Andy can tell you how, though there is a document on that too. Regards Pete -
Script to read LVAR too slow
Pete Dowson replied to Tiago Thiengo Vieira's topic in FSUIPC Support Pete Dowson Modules
That's odd. with 90 values it was taking 2 seconds, but with 138 it takes only 1 second? If you are already only writing changes, then why did you ask me? If all you want to do is copy it all over then read all the LVars, then do one (r a few) wrteStructs. Your choice. You asked for advice and that was it. Sorry, I don't know what you mean. You can't handle L:Vars from a client. Sorry, I've no idea. I find out such things by experiment. Try 3.998r, http://fsuipc.simflight.com/beta/FSUIPC3998r.zip The LVars are read in the Lua thread in that version, instead of being queued. Regards Pete -
FSUIPC in COMBO II BOEING
Pete Dowson replied to sudqui's topic in FSUIPC Support Pete Dowson Modules
The latest is 3.998q. Please see the Download Links subforum as I stated. I don't think the new VRI combo devices aren't supported by 3.998. Anyway, you should use the latest if you want help. Okay. I see [VRinsight] 1=COM19, COM3 Are those correct? Are you using VSPE? What is your actual question? Are you using the VRInsight software as well? If so, then that should connect to it on COM3. Does it? If your device is on COM19 and VSPE is working, then FSUIPC will see it and pass things you don't program on to the VRI software. What is your problem? Pete -
In that case your '.' key is not assigned to the brakes. Maybe it is assigned to something else, or you unassigned it in FS for some reason? Or it is being used by another program? Sorry, i can't tell from here. Why not check in FS assignments as a start? Sounds like your button 0 is assigned to the same control that '.' should be assigned to. There never has been a "continuous brakes" facility, either you hold the key (so it repeats) or have a button set to repeatedly send the control. Braking with toe brake axes is different of course. What has FSUIPC got to do with what you've said so far? If you have a registration for FSUIPC you can do all sorts of assignments, as you wish. Regards, Pete
-
The autosaves shouldn't be perceptible, so something is wrong. Usually I would say it's to do with the disk access -- that your disk is nearly full or badly needs defragmenting. but there's something else fishy going on, as you say it only started doing that since you set it to run in Admin mode. Try changing it back to normal mode and see if the pauses stop. If so there's something strange going on with FS's access to its own "My Documents\Flight Simulator X Files" folder. (FSUIPC's autosave does not save the files itself, all it does is call FS's savew routines, the same ones you call yourself using the ';' key or the Flights-save menu entry). Another thought. Was there a particular reason you changed FSX to run in elevated admnistrator mode? Something to do with something else you installed perhaps? If so, maybe it is more related to that addition. For example, some add-on aircraft save a lot of stuff too when FS saves a flight. Maybe that is trying to save into a protected folder and the delay is being caused by such cross-checks and errors reported back to it? Or maybe it is simply inefficiently done? There really should never be a reason to run in elevated administrator mode -- that's needed for installers and when you are trying to update or repair things central to Windows' operation. There's no upper limit imposed on the number of seconds, only a lower one (10 i think). Same applies to the 'also Save' interval. Regards Pete
-
The cost of the assorted Bodnar boards is really good for what you get. The BU0836X is sort of "top of the range" at about £50 -- but you get 32 switch inputs, 16 encoders, 8 analogue (axis) inputs and a POV. See http://www.leobodnar...oducts/BU0836X/. I paid about £20 for a lesser card, the BU0836, which is missing the encoder inputs, but does a great job with both analogue and switch inputs. Just work out what you need -- count up switches, encoders and axes. No drivers needed for this method -- your device will look like a standard Windows HID device and you can assign things in FS directly or in a registered FSUIPC. For more advice I'd recommend you go over to http://www.mycockpit.org/forums/. There's a lot of folks there who know a lot more ways of doing this sort of thing than I. Regards Pete
-
Okay. The fact that you have an FSUIPC4.LOG file being produced means that FSUIPC is actually being loaded. So that's one step forward. I note you have 4.728b installed. That was a temporary interim release. Not sure how you got stuck on that, but it would be a good idea to change it -- 4.756 is available on the Download Links subforum. Well, SimConnect is connected okay, and the Menu entry is certainly being created initially, at least. However: Something is stalling SimConnect so much that FSUIPC4 is not getting any information back, so tries reconnecting: which again succeeds. for a little while: And so on, ad nauseam. So, whether you see an FSUIPC menu entry or not looks like it depends when you look! Something is serious degrading your SimConnect performance. I've never seen anything quite so bad -- FSUIPC does occasionally need to reconnect in heavily overloaded systems, but yours, judging by the configuration you posted earlier, most certainly should have no such problems. There is one clue. the intervals at which the problem occurs. Look at the lines for the errors: The number on the left is in milliseconds. so the timeouts are occurring regularly at intervals all around the 60 second mark. FSUIPC defaults to a timeout of 1 second in receiving SimConnect messages (which should arrive at your FS frame rate, as a minimum). Something in your system is stopping FS once every minute, approximately, for something over a second. Don't you notice any such pauses whilst flying? You can make FSUIPC more lenient, by editing the FSUIPC4.INI file -- the parameter is "SimConnectStallTime" and you'll see it is set to 1. You can set anything up to 9 (for 9 seconds). but really you should try to find out what is causing the >1 second pauses. Regards Pete
-
Encoders and keyboard hack
Pete Dowson replied to Basje's topic in FSUIPC Support Pete Dowson Modules
Aha! here's the reason your Lua is never running: That needs to be [Auto] 1=Lua AltitudeChange The [Auto] section is for automatically running Macros -- Lua plug-ins are one type, but equally you could run your macros directly there too. FSUIPC needs to see the Lua prefix, as it does in the assignments, so it knows your meaning. Regards Pete -
Starting LJ45 engines in FSX issues
Pete Dowson replied to Tomlin's topic in FSUIPC Support Pete Dowson Modules
Thanks for finishing the thread, albeit late! ;-) Regards Pete -
Encoders and keyboard hack
Pete Dowson replied to Basje's topic in FSUIPC Support Pete Dowson Modules
Ouch! Please please update your FSUIPC. The current version is 4.756. See the Download Links subforum. I didn't realise we might have been talking cross-purposes, as a lot has happened in the months since 4.703! Yes. Your Lua plug-in isn't loading, it isn't running. That's why it does nothing. How are you starting it? Try the current version of FSUIPC, then get back to me -- I'd need to see your FSUIPC4.INI file. Pete -
I assume you mean the transponder mode switch? You'd switch the mode when swtching to Tower before takeoff, or after switching to Ground after landing. Usually that should be before entering the runway and after leaving it. No harm in stopping whilst making such changes -- you needed to retune the Comms in any case. Unless you are flying on line this is only an added realism option, as it isn't realy doing anything. For on-line flying there are FSUIPC-added controls to talk to Squawkbox, and i believe FSInn has methods too. If the switch is amenable to mouse macro treatment, like much of the NGX cockpit, then you should be able to program a hardware switch for it. Have you tried? I don't know enough about LINDA, but it is designed specifically to make these things easier so it is worth you looking at too. Regards Pete
-
Oh, yes. In Bury. How are you? It isn't something I'd be interested in doing, but I think there is a program which does something like that already. EZscenery or something like that? I don't know if it does moving traffic though. Of course I remember Lago -- Mathijs Kok, now in Aerosoft, was part of that company. I think there was a bit of a bust-up. But I've not really been interested in doing scenery or AI myself. I have a full 737NG cockpit to deal with and my programming time is more spent on interfacing to such things. Best Regards Pete
-
Didn't think what? Sorry, you seem to be replying to my whole post in a confusing way. What is this an answer to, exactly? I am not asking you to log anything! I said that if an FSUIPC log file (a FILE -- something you see in Explorer! Files are objects on your disk) is being produced then FSUIPC is at least loading! That's the first thing to determine! If it IS loading then the log may show why the menu isn't being produced, so I'd need to se it. On the other hand, if it isn't loading, then ... oh dear, why do I have to repeat it all? Please re-read my original reply which you seem to have misinterpreted. If you don't want to resolve this problem, all very well, but in that case why post here? Pete
-
Has offset 0x3308 (FS version) been updated?
Pete Dowson replied to lordofwings's topic in FSUIPC Support Pete Dowson Modules
Which document are you looking at? It certainly cannot be any official offsets list released in the last 5 years! Both the "FSUIPC for Programmers" and the "FSUIPC4 Offsets Status" documents have included FSX since 2006. Maybe it is now time for you to update your copy? Both FSX and ESP. are listed, but not yet P3D -- that'll be in the next update, this Spring. Regards Pete -
Likely the easiest and maybe cheapest option is to effectively gut it and get one or more Leo Bodnar BU0836X boards or similar, and wire it all up to those. You'd then have a USB device easily programmed. The panel has no indicators or gauges, so doing it that way it would look like a joystick type device with lots of buttons in both FS and FSUIPC, so easily assigned. Check out this 3-year old thread too: http://www.flightsim.com/vbfs/showthread.php?181630-Making-an-old-Jeppesen-FS-200-Panel-usable-for-FS2004 Regards Pete
-
FSUIPC Client DLL for .NET - Version 2.0
Pete Dowson replied to Paul Henty's topic in FSUIPC Client DLL for .NET
Lua plug-ins are only for registered users. Pete -
You can't tell whether the aircraft is at a gate or runway without checking the latitude/longitude and working it out from full airport runway/gate/taxiway/apron data. But if you mean whether you are "ready to fly" or not, please check offsets 3364 and 3365. If you read 3364 as a "word" (2 bytes), you are 'ready to fly' when the result is all zero. Regards Pete
- 1 reply
-
- 1
-
-
Best way to find out if an engine is running
Pete Dowson replied to lordofwings's topic in FSUIPC Support Pete Dowson Modules
Good question. I'm pretty sure, in this context, that props and turboprops are both treated like props, whilst jets and turbojets (i.e. the original type of jet engine) are jets. I think the distinction is whether they have a prop or not. Regards Pete