-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
FSUIPC & Saitek Rudder Problems
Pete Dowson replied to Yowie's topic in FSUIPC Support Pete Dowson Modules
First off, you are still only assigning in FSUIPC "direct to calibration". If you assign "direct to calibration" you MUST calibrate, or else the controls are not active. I see no Profiled calibration in your INI! Second, since all your axis assignments are identical for all but 1 profile, why are you making profiles for axis assignment? The odd one out is: [Axes.Flaps Down] 0=0X,256,D,7,0,0,0 1=0Y,256,D,8,0,0,0 2=0R,256,D,3,0,0,0 3=1Y,256,F,2,0,0,0 4=2Z,256,D,10,0,0,0 5=2R,256,D,9,0,0,0 where you seem to have omitted to assign 1X, the aileron. Doesn't the "Flaps Down" aircraft need aileron control? Additionally this line: 3=1Y,256,F,2,0,0,0 is weird. The "F" means "FS control", but "2" is the direct to calibration value for elevator! I don't think sending that to FS will do anything, or certainly not elevator in any case. So this profile actually has no elevator nor aileron assigned. I would strongly recommend you delete all the [Axes ....] sections EXCEPT the generic [Axes] one which will do your assignments for all aircraft. Finally, if you look back, I did actually ask you to try assigning to the FS control, "Axis Rudder Set" instead of Direct to Calibration. You've either not yet tried this, or not reported on it. Please do. I am NOT talking about assigning IN FS. Also, please DISABLE controllers altogether in FS when assigning axes in FSUIPC just in case they are interfering. Regards Pete -
Problem with 4859J and SIM1.dll
Pete Dowson replied to vgbaron's topic in FSUIPC Support Pete Dowson Modules
Okay, but please, if it is something we should be aware of, please tell us whatever details that might help in case it does afflict others, Best regards Pete -
Hmm. I'll consider that. I'll chat with my expert pilot guy first. With a linear climb to, what, 10% at 30knots? So still only 5% at 20 knots? I don't think that would be right for airliners on landing rollout. I'd have to reduce the change to 20 I think, giving: 0% at 0-10 0% rising to 10% from 10 to 20 knots 10 rising to 100% from 20 to 60 knots. The last would give about 19% at 30% instead of the 10% you have now. It's starting to sound as if you need a different gradient for each range of 10 knots befow 30 ...? Sorry, you've lost me there. Regards Pete
-
Problem with 4859J and SIM1.dll
Pete Dowson replied to vgbaron's topic in FSUIPC Support Pete Dowson Modules
What, without these entries in the log? 16 Hook Error: can't find .37 in SIM1.dll 16 Hook Error: can't find .37 in VISUALFX.dll I ask, because the recent changes for the SIM1 friction are not only unrelated to those, but occur much later in the initialisation sequence. Thanks. Pete -
Hmm. I've done exactly the same here and I get this: ********* FSUIPC4, Version 4.859k by Pete Dowson ********* ... 168372 System time = 07/12/2012 16:07:06, Simulator time = 16:04:32 (16:04Z) 171461 Aircraft="Beech Baron 58 Paint1" ... 207029 Monitor IPC:281C (U32) = 0 282564 WRITE0 281C, 4 bytes: 01 00 00 00 .... 282580 Monitor IPC:281C (U32) = 1 282580 SimRead: 281C="ELECTRICAL MASTER BATTERY" INT32: 1 (0x00000001) 283064 READ0 281C, 4 bytes: 01 00 00 00 .... [/CODE] The master battery switch is one of the SimConnect variables which can be written to (many things can only be changed by sending controls or events). As you see, when I write 1 to 281C, Smconnect actions it and I read back 1. Evidently in your case something is stopping SimConnect from switching. Just to make sure we are noth using the same software, try updating to FSUIPC 4.859k. I'm not sure what to suggest next. It'll be a process of elimination. You say you can switch it on from the gauge? What does the log show then? Do you have any add-ons which might be interfering? What if you switch it on in FS and try switching it off from your program. Does that work? What about getting a SimConnect log? That'd show other programs doing things, maybe? See the FAQ subforum for instructions. It is such a simple little thing. I dont know how it could be so mystifyingly wrong.
-
Problem with 4859J and SIM1.dll
Pete Dowson replied to vgbaron's topic in FSUIPC Support Pete Dowson Modules
Please try 4.859k, now in the Download Links subforum. I changed the way FSUIPC derives the address of the tables in Process Memory, just in case. I'm also now logging the computed address and initial successes or failures. Regards Pete -
You always need to state the actual version number please. "Latest version" is next to meanngless as it depends where you are looking to decide it is "latest". The real "latest" is 3.999y2. Please see the Download Links subforum. Sorry, they are nothing to do with FSUIPC. The FSUIPC log is a single file which you'll find next to the FSUIPC DLL in the FS Modules folder. Nowhere else, and only one of them. Sorry, no. Nothing I know of for certain. Can't you look inside them, might give you some clues? Regards Pete
-
Yes, so please monitor it to the Log so we can see what happens. If you also lg Events" (on checkbox on the left side of Logging) it will show if extra commands are doing it. The whole point of the FSUIPC logging is to help track things down. Merely seeing it on the title bar is no good to me (I am not there), and it doesn't show any other details. Regards Pete
-
FSUIPC & Saitek Rudder Problems
Pete Dowson replied to Yowie's topic in FSUIPC Support Pete Dowson Modules
Those are the relevant parts. Seem okay. Please check with a default aircraft. I note that the two you mention are the only ones subject to FSUIPC Profiles, which may or may not be relevant. Also i note that you have the "slope" set quite extreme for the rudder. Just in case, please retest with it level (straight line, value 0). Finally, try assigning the rudder axis to the FS control "Axis rudder set" control instead. It might be that those add-ons don't do their animation otherwise. But possibly it is still actually operating? It might just be the visuals, in which case it would be add-on aircraft specific. Try steering with the rudder whilst taxiing. Regards Pete -
FSUIPC & Saitek Rudder Problems
Pete Dowson replied to Yowie's topic in FSUIPC Support Pete Dowson Modules
Is this with a default aircraft? Show me your FSUIPC4.INI file, from the FS Modules folder. You can pate it here. What IS the "latest version"? I asked for the Version Number, please. There have been many many versions over the last few weeks. I ALWAYS need the version number. It isn't hard to find -- it is displayed in the main FSUIPC options, it is shown in the Log, it is available in the DLL properties (right-clcik, properties). Please check the version number and tell me that. I asked how you are assigning in FSUIPC -- which assignment option and which control. Did you miss that? In the axis assignments there is assignment to FS control or direct to FSUIPC calibration. The two methods are very different. Furthermore, each has a different set of controls in the drop-down from which you select one. Which one did you select? These are not difficult questions, really, but answers are essential if I am to understand what troubles you and why. Regards Pete -
FSUIPC & Saitek Rudder Problems
Pete Dowson replied to Yowie's topic in FSUIPC Support Pete Dowson Modules
Sorry, what do you mean? What signifies their presence to you? Do you mean they do nothing in FS when pressed, that you cannot see the rudder move or steer whilst taxiing? Please explain. Also please state the actual version number of FSUIPC which you have installed, and how you are assigning in FSUIPC -- which assignment option and which control. Regards Pete -
FSUIPC & Saitek Rudder Problems
Pete Dowson replied to Yowie's topic in FSUIPC Support Pete Dowson Modules
You can always calibrate in FSUIPC no matter where you assign. If you need to assign it in FSUIPC, can you tell me what you see in the Axes tab when you move the pedals? If FSUIPC cannot see the axis then it cannot assign it, so that's the first thing to check. If some other axis is jittering and appearing there all the time, preventing you seeing others, just use the "ignore" button to temporarily ignore that one and then click "rescan". The only other thing I can think of is if you are running some other driver, maybe a Saitek one, which is already sending rudder controls. To check that, see if you can calibrate in FSUIPC even if you don't actually assign in FSX or FSUIPC. Regards Pete -
I don't know C# so I'm not commenting on the code. You say "when I turn it of it gets 0. But as soon as it reads the value it goes back to one", but do you really mean that? i.e. Do you mean it stays off for as long as you don't read it? And are you talking about the actual switch (as seen in a gauge, for instance), or only about the offset value? Do they always correspond? Have you tried using FSUIPC's logging facilities? Use the Monitoring option to monitor the offset. Maybe you have something else running which is setting the switch as well. Have you tested on a default aircraft to make sure it isn't related to the specific model? Regards Pete
-
Problem with 4859J and SIM1.dll
Pete Dowson replied to vgbaron's topic in FSUIPC Support Pete Dowson Modules
Thanks for re-posting here. Makes it easier to keep track of rather than in the middle of a mixed thread in the FSX forum. Your crash is very strange. I'm checking things through now, but I suspect I shall have to add some extra logging entries to obtain more info on what is happening, and why your FSX/Acceleration install is behaving so differently to any of mine. Can you confirm that it still occurs when you re-run FSX with the Trust established? (I never get the repeated trust question on each update because SimFlight is already down in my system as a trusted publisher). The more particularly odd thing is this, occurring before the crash itself: Those are relating to hooks placed in FSX, for calls from WEATHER.DLL, for weather smoothing and the like and the related code has been there for years. Can you tell me if you also see those entries with the previous working version you had installed? (If you've not got it still, please reinstall 4.853 to check. If so it definitely implies there's something very different in your installation. I can take steps to report the crash problem and carry on normally, with just a log entry, just like those hook failures, but it would mean that the SIM1 friction patching wouldn't then be available in any case. Those are the same as mine. I'll upload 4.859k with protection included and logging of success or otherwise, but I don't know what else I can log to find out why your system is behaving differently. The addresses needed are obtained after explicitly loading the modules and using the base address thus obtained with an offset. If the module could not be loaded the base address returned would be zero and then FS avoids patching. To actually crash would mean it returned success for the loading, so I don't understand. [EDIT] Are you using Windows 8 BTW? Because I'm wondering if the library handles are no longer memory addresses in that system. That could explain it. I'd have to find a different way of getting a modules base address in process memory. Regards Pete -
Have to assign/create profile every time I fly.
Pete Dowson replied to Barbs's topic in FSUIPC Support Pete Dowson Modules
Ah, yes, sorry. That was intended and it seems not done. It will change in the next major release of FSUIPC. Pete -
No, there's no way to do that. But you can use the Lua com library HID functions to read the buttons states. Check the com.gethidbuttons function. This decodes button data from a packet read previously by the com.read function on a device opened by com.openhid. Basically by using this you are using the raw USB interface to interrogate the device. It bypasses the DirectInput mechanism used by FSUIPC and FS for button detection and reads the current state. Once you have the button states you simply process each one calling the appropriate action (ipc.control function for controls, and ipc.write... or ipc.togglebits... functions to affect offsets. Unless you have switches which can be electronically changed over from the PC (a VERY VERY expensive option involving magnetic or solenoid switch operations. Very bulky too), there is obviously NO WAY you can set your real hardware switches to match whatever flight you load. You can only do it the other way around -- i.e. change the FS settings to match the switches. But that could result in disaster, or at least difficulties, if you reload a flight in mid air and switch things around like fuel or iginition! I always make sure I either shut down in a standard state (for me, cold and dark), and only load flights which are saved in that state, or, if I'm am trying to continue from a failed or time-limited earlier flight, just leave the cockpit the way it was when I saved. Regards Pete
-
I looked up "string.find" and it seems to me you have the parameters the wrong way round? The pattern you are searching should be second, the thing in which you are searching should be first. Also the pattern matching is not a simple string operation, it is for patterns defined using quite a complex character-based system.In particular the '-' in the pattern has a special meaning, being one of the "magic characters" (which are ^$()%.[]*+-?). You can make string.find operate with plain strings -- the 4th parameter controls that. I suspect that's what you need. I'm not an expert, but I can look things up! Luckily I purchased the reference manual in print, which makes it slightly easier perhaps than referring to the Lua website. Regards Pete
-
Have to assign/create profile every time I fly.
Pete Dowson replied to Barbs's topic in FSUIPC Support Pete Dowson Modules
No, I've never seen that before. Can you please confirm you ARE using a supported version of FSUIPC? You don't even say if it is FS9 or FSX or some other simulator. If you are not using version 3.999w or 4.853 or later please update first, then apply the very latest version (3.999y2 or 4.859i, or even 4.859j by the time you look) from the Download Links subforum. Test again, and if it still occurring let me see the INI file and the LOG file for that session. BTW, provided you have "ShortAircraftNameOK=substring" set (and it is defaulted like this these days) you could edit the [Profile.B737] entrries to simply: 1=737 and then that profile would be used for every 737 you have or will have, provided there's a "737" someplace in the name. But please let's work out why the original problem occurs first so that, if it is still prevalent in the current versions, I can fix it. Regards Pete -
Without any real information I can't really help much. there are logs produced by both WirdServer and Wideclient, and these will probably show why. The most usual problem is that those two operating systems default to using different Workgrops, so broadcasts don't get through. If you please refer to the section in the WideFS user guide there is help there to sort it out. Read the section on configuring your network, especially the part with the bold red heading telling you to read it. Regards Pete
-
New computer for a registered version FSUIPC
Pete Dowson replied to georgefitz's topic in FSUIPC Support Pete Dowson Modules
Well, whilst downloading a new copy would make sure you were up to date, if your existing copy is up to date, why not just copy it over? Yes, you'd need to register it, so you'd need to run the Installer to do this in any case. Email? Can't you just copy it over, or via a disk or memory stick? If you use Joy Letters to identify your joystick devices then you should have no trouble. If not you'll probably find all the joystick numbers are different, so your axis and button assignments, if you have any, may be all jumbled up and assigned to the wrong devices. Regards Pete -
No, I can't figure out what you are doing I'm afraid. What does "ipairs" do?I don't think i've ever used that. I don't actually program Lua much, I add Lua support functions to FSUIPC and WideFS. Please use the logging faciklities. The Lua Debug option will not only trace your code but show you the variable vales. Pete
-
FSUIPC vanishes from Addon menu mid flight
Pete Dowson replied to mccaba's topic in FSUIPC Support Pete Dowson Modules
Actually it would be better to track the cause down. See if you can stop that secion of McAfee. There should be no reason to have that activity going on. It might be periodically checking loads of stuff -- any files which have been changed. It should only be necessary to have virus checking on downloads, internet access and so on, when you actually do them. Pete -
FSUIPC vanishes from Addon menu mid flight
Pete Dowson replied to mccaba's topic in FSUIPC Support Pete Dowson Modules
Yes. did you change the stall time parameter? The disconnections don't start till the 1,332nd second (22 minutes in), but then seem to occur almost regularly: In fact it's either every 12 seconds, or sometimes a multiple of 12 seconds, like 24, 36 or 48: 1332639 **** No SimConnect events or states being received! Re-connecting now ... **** 36s 1690661 **** No SimConnect events or states being received! Re-connecting now ... **** 1810189 **** No SimConnect events or states being received! Re-connecting now ... **** 1929810 **** No SimConnect events or states being received! Re-connecting now ... **** 2049260 **** No SimConnect events or states being received! Re-connecting now ... **** 2168664 **** No SimConnect events or states being received! Re-connecting now ... **** 36s 2527481 **** No SimConnect events or states being received! Re-connecting now ... **** 2647087 **** No SimConnect events or states being received! Re-connecting now ... **** 24s 2886175 **** No SimConnect events or states being received! Re-connecting now ... **** 3005703 **** No SimConnect events or states being received! Re-connecting now ... **** 3124981 **** No SimConnect events or states being received! Re-connecting now ... **** 3244571 **** No SimConnect events or states being received! Re-connecting now ... **** 3364396 **** No SimConnect events or states being received! Re-connecting now ... **** 36s 3723104 **** No SimConnect events or states being received! Re-connecting now ... **** 3842601 **** No SimConnect events or states being received! Re-connecting now ... **** 48s 4320807 **** No SimConnect events or states being received! Re-connecting now ... **** etc [/CODE] That strongly suggests it's related to some other regular activity on your system. do you have background defragging, antivirus checking, anything like that going on? Is your weather program inserting new weather every 12 seconds, or at least dowbnloading it? There are none at 2 mins. The base interval is definitely 12s. That's the main clue. No! Every single SimConnect stall requires FSUIPC to reconnect to SimConnect and regenerate theMenu. All of them show the Menu being re-added. Why do you only see the last one? FSUIPC itslef doesn't stop and restart, only its ability to deal with FS via SimConnect, and the Menu is made by Simconnect.. Regards Pete