Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Hmm. No idea why you had to do that. Must be something odd to do with the specific aircraft implementation? Pete
  2. Did you change the Workgroup name in one of those so that they are the same? XP and Win7 default to different workgroups. Please read the WideFS documentation, check the section about configuring your network. It isn't there. The log is simply informing you that since no Initial.lua was provided, none was executed! It is information, like most entries! Looking at your log: 4256 Trying TCP/IP host "HP-Bureau" port 8002 ... 4256 ... Okay, IP Address = 192.168.0.220 25206 Error on client pre-Connection Select() [Error=10060] Connection timed out [/CODE] Is that the correct IP address for your FSX PC? Was FSX actually running? The Client log only shows half of the story. For a full diagnosis the WideServer log file from the FS Modules folder is also needed. Pete
  3. The only WideClient configuration file is WideClient.INI, and all the parameter settings you can make are described in the WideFS documentation. Please take a look. Pete
  4. I think you will need to post in a forum dealing with aircraft gauges and so on, or email the gauge author. I'm afraid I have no idea how that gauge works. Pete
  5. Water runways are omitted. No one has ever asked for those. They weould have to be an option if needed, as pretty much all uses of the files prodcued uses them for land aircraft only. Similarly heliports are omitted. As documented, runways of 1500 feet or less are also omitted. You can override that -- see the read me. Pete
  6. The sound facilities are working fine here with P3D 1.4. Something is wrong in your P3D installation or Lua files. Paste a sound-playing Lua in a reply, and paste in your FSUIPC4 install log, and I'll check. Pete
  7. Sorry, please explain what you mean. "GLOBAL" is not meaningful without context. Which version of FS is this with? I don't believe that's possible with FSX or P3D, though it may be with FS9 and before. That's really only related to the old Adventure Programing Language (APL) weather. You should use 0F8C, and it is statute miles times 100. Sorry, that looks nothing like Intel Assembly code to me. What is it? You cannot access FSUIPC offsets directly, only via the FSUIPC interface, as documented. The offset numbers are tokens representing the documented values, they are not addresses. If you are using FS9 or before then certain BGL variables can be used via FSUIPC offsets 0DD6-0DDE. Please check the documentation supplied. Pete
  8. Sorry, then. I don't understand at all. I always thought SB3 --> FSUIPC --> FD9, and SB4 --> SimConnect --> FSX. I'm afraid you'll need to refer to the SB forums, if they exist. From now till November 5th I am on holiday. Sorry. If this is still unresolved then I will again try to help, but currently I simply don't understand. Regards Pete
  9. The problem I have in helping you is simply that I do not understand the concept of assigning an axis to "these arrow keyboard". What IS an "arrow keyboard", and how would any keyboard type of control even act as an axis? An "axis" is something which provides variable values according to position, i.e. a joystick or lever. I do not see how "arrows" or "keyboards" come into that. When you use the keyboard to control a value which is more commonly or more conveniently controlled by an axis input, you do it by assigning INCREMENTS and DECREMENTS. For every axis type control in FS there are increment and decrement controls which you can assign. indeed, most are already assigned on the "normal keyboard" for use by folks without a joystick. FSUIPC can also assign such controls to keyboard inputs. Is this what you really mean and need to use, perhaps? Regards Pete
  10. It isn't "4.something" but 4. then two or three decimal digits! Version 4 is the one for FSX and has been so for over six years. The version number is easy to find, so why not quote it? There were four releases in September. And you don't "buy the latest version" you buy FSUIPC3 (for FS9 and before) or you buy FSUIPC4 (for FSX or later). Your purchase covers all versions FSUIPC 4.xxx, so there's no way I can know what actual version you are using unless you tell me!. The actual latest version 4, as you will see from the Download Links subforum, is 4.858. So "TDC Radar" isn't some FS function peculiar to a cockpit, as it came across to me, but a mode of use of your joystick? Anyway, the crucial part of the above is "Nowhere in the FSUIPC programming tool do I find any microstick response" in which case it evidently is not looking like a normal joystick device, at least in the "TDC Radar" mode, therefore you can't program it as a joystick device in FSUIPC -- unless perhaps you can get USB innterface programming details for it and write your own Lua plug-in to handle it. If the "TDC Radar" means sending keystrokes then they won't be detected as assignable bttns or axes. You need to program the keystrokes instead. Sorry, I am totally confused now. I do not understand any of that at all. Where does "VRS" come into it, and what is "emulation on mode"? This must all be related to other programs I assume? If FSUIPC can see device buttons and axes as device buttons and axes, you can assign them in FSUIPC. If it cannot then you cannot. It is really that simple. If you can make this strange device send the right signals to the PC then I'm sure you can do something with it. I'm really sorry I can't be more help than this. Regards Pete
  11. Andy's given you the correct answer for that one. The disconnection is to stop your trim axis messing up what the AP is trying to do. You can't stop the AP using trim else it won't work. As Andy says, just remove the line in the list for the old Profile in the INI file. Why would you want to do such a thing -- did you make a mistake in assigning the profile? If you want to fly the same aircraft with different profiles for different circumstances, it would be better to edit that aircraft's AIRCRAFT.CFG file and add another instance of it with a different name. the name could even include some Profile ID. After today I am away on holiday till november 5th, so please forgive any delays. Regards Pete
  12. See previous answers. There were several versions released in September. -- 4 of FSUIPC4 and at least one of FSUIPC3. They have version numbers, which are really really easy to find -- in the log, on the screen in options, in the DLL right-click Properties-Version, even amazingly in the documents supplied in the Zip. Please always give version numbers. If this "microstick" is visible via DirectInput as a normal joystick type device, it will be visible and assignable in FSUIPC when you move it. If it isn't then it presumably is not a normal Windows joystick device. You'll need to consult its documentation to see how to use it. I've no idea what a TDC radar is nor how you could use a joystick as one. Sorry. So it IS visible as a joystick! Then you can assign it to any of the FS controls listed, or to any additional FSUIPC controls listed -- see the drop down in the assignments tab. You can even assign it to do things with FSUIPC offsets. I'm afraid I don't know what you mean by "using it as a TDC radar". That makes no sense to me I'm afraid. After today I am away on holiday till november 5th, so please forgive any delays. You might be better off posting a question in a new thread with the title saying something about "TDC Radar", as evidently your question is certainly not about getting your microstick working, which is what this thread was about. By using the proper titles in threads you are more likely to get help from folks who know. Regards Pete
  13. Er ... SB4 is for FSX and doesn't use WideFS. In fact it surely doesn't work with FS9 anyway as it needs SimConnect? All this time I thought you were talking about SB3! Pete
  14. Why do folks so insist on posting screenshots? I could barely make that one out! Seems that something is broken either on your SB3 installation, or in the WideFS link. You could enable logging in the WideClient to ensure the message gets through. Try Log=Keys in the [user] section of the WideClient.INI file. BTW did you check your SB3 version? Maybe it is out of date? Does it work otherwise? Does it link via WideFS? Is it running at the same priority level. Oh, one other thing I thought of. The facility uses message broadcasting. Is it possible that you have the facilities for this turned off on the Client? Or are you perhaps using a very old version of Windows on that PC? Pete
  15. Not sure why you posted that Ps. I was referring to your "proof", i.e the picture you posted, which didn't show the single throttle axis at all. I've finished for now. i'll have a little time tomorrow and I'll check back, but I don't think there's anything else I can do from here. Maybe the Dodo people can get in touch with me after I get back if there's some conflict with their product. Or maybe other users know the answers. Pete
  16. Also try removing that throttle Lu's file, temporarily Pete Sorry about typos -- horrible keyed on phone
  17. Briefly: Try leaving the logging as you have it, and load a different aircraft -- maybe that other help you have. If you then don't get those 6 hz repeating batch of 5axis controls, you know it MUST be the Dodo. The try their support. Sent on my phone PS i try not to inject any tone into my replies, they are purely technical. I'm sorry you read them otherwise and even accuse me of accusing you of things which,if you read more carefully you'll find is not so. Bye, and good luck! Regards Pete (no Ph.D I'm afraid
  18. When they are turned on, they stay on for all further sessions until you turn them off. You had them on in the first log you posted. Then you posted a log with them off. Not sure where "new log" comes into it. I actually explicitly told you not to press it in the message asking you to enable the axis logging. FSUIPC is simply doing what you ask of it. It isn't doing the other stuff which is what is messing things up. You cannot say "FSUIPC isn't working". It's a tool, it does what you tell it to do. The "tone"? I am absolutely trying my best, under pressure as I am trying to get ready to leave on Friday for three weeks. I am honestly frustrated by the lack of success, but I am doing my damnest. It's just that each time I suggest something the response comes back with something done differently to my suggestion. If only you'd take just a little more care. I quite understand if you are completely unfamiliar with computers, but you must realise they don't really understand anything, they just do what they are told. if you scan throughg this Forum you will see I try to, and normally achieve, the best and fastest support you are likely to see anywhere, and I am deeply hurt by your accusations. I am afraid we have reached an impasse with virtually no time now for me to help further until after 5th November. I respectfully suggest there is something very odd about that "Dodo" and perhaps you will get more help from other users? Sad Regards Pete
  19. Further to my previous reply, there is one important thing I just noticed. when you had Axis logging enabled, as in the ealrier logs, the main 5 "generic" control axes were being set at rregualr intervals: Here's a section without the confusion of your own throttle movements: 1683204 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1683204 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -205 (0xffffff33) AXIS_ELEVATOR_SET 1683204 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1683204 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1683204 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1683375 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1683375 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -215 (0xffffff29) AXIS_ELEVATOR_SET 1683375 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1683375 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1683375 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1683547 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1683547 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -225 (0xffffff1f) AXIS_ELEVATOR_SET 1683547 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1683547 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1683547 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1683703 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1683703 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -235 (0xffffff15) AXIS_ELEVATOR_SET 1683703 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1683703 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1683703 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1683875 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1683875 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -245 (0xffffff0b) AXIS_ELEVATOR_SET 1683875 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1683875 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1683875 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET 1684031 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1684031 *** AXIS: Cntrl= 65762 (0x000100e2), Param= -255 (0xffffff01) AXIS_ELEVATOR_SET 1684031 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1684031 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1684031 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET The fact is that these are NOT sent by FSUIPC. But it perhaps isn't actually FSX either, because it doesn't appear that the all values are changing -- only the Elevator (which oddly is decreasing by exactly 10 each time!?). The interval of 160-170 mSecs (the number on the left is time in mSecs) is suspiciously like FSX though -- it scans devices at 6Hz (much less frequently, in fact, than the default in FSUIPC4, which is 100 Hz!). So I am unclear on this. See if the logging is the same with that other helicopter -- maybe it is that aircraft you have loaded which is doing this. I'm sorry, but I have reached the limit of my ability to help you. All I can say is that the problem is NOT to do with FSUIPC, It is either something set in FSX or the aircraft or some other add-on you are using. Now it is time for you to do some elimination. You have the tools -- the logging with Axis events logged will show you, as i have explained. One experiment you CAN try in FSUIPC4 is to set the [JoystickCalibration] option UseAxisControlsForNRZ=No in the INI file to Yes. Maybe this add-on expects the "AXIS_ ..." controls only and if it doesn't see them does this crazy reset action. Being a helicopter with only one "throttle" (actually treated as collective I think), it may not even like the separate throttle 1 and 2 controls in any case. I suspect you may have to start using Profiles properly so that different things apply to different aircraft according to their needs. Regards Pete
  20. Well, take care. Sometimes just a USB glitch or a slower than normal initilalisation of a USB device can make it happen. Just check when you get problems. No. Just disable the controllers and re-test. That will prove it to you. I am running out of time here. You really do need to test this yourself. There is nothing in FSUIPC which is doing this to you! You haven't got any log options selected this time, that's why! I don't know why you turned them off. Anyway, it won't tell me anything else now. Those "AXIS_ ..." controls it logged last time were certainly all from FSX -- unless the FSUIPC4.INI file you showed me isn't the one you are actually using. Pete
  21. The logging "tab" is the tab selecting the Logging options, like Axis tab and Buttons tab, etc. In Windows tabbed dialogues the tabs are the selection bits at the top, as in a filing system with tabs. Those are the two separate throttle axes, which, yes, are unassigned in FSX (as I could see from the log)! But you've not bothered to scroll down to the single throttle axis,That's the one which is doing the damage! "AXIS_THROTTLE_SET" is the single throttle axis which is obviously assigned in your FSX -- as I can see in the Log along with those other axes I listed. If it isn't assigned on this controller, it most certainly is on another. Provided that you don't have conflicts, which you do, that is true. But be aware, as I already stated, that FSX will automatically reassign axes if it ever sees your device as "newly connected". So whenever you get something odd happening, as you have, always check. On the whole it is best to do all or none at all. Keeps things clean and tidy. To check assignments on a device you need to scroll through the entire list, not just stop at the start! I understand that, but I am asking you to do things and you are not, or you are doing different things. And you certainly aren't ensuring that you have no conflicting assignments in FSX! Pete
  22. [Continuation log requested by user] First off, you pressed the "New Log" button. I expressly asked you not to do that. It means that some of the initialisation information is missing! Second, you did not need to send a complete log. Each part is much like the other. That is why I just asked for an extract, a "relevant section" -- ie. one place where you got the problem Third, it certainly looks like toy have all your axes alsp defined in FSX, not only in FSUIPC: 1681363 *** AXIS: Cntrl= 65763 (0x000100e3), Param= 0 (0x00000000) AXIS_AILERONS_SET 1681363 *** AXIS: Cntrl= 65762 (0x000100e2), Param= 0 (0x00000000) AXIS_ELEVATOR_SET 1681363 *** AXIS: Cntrl= 65765 (0x000100e5), Param= -16383 (0xffffc001) AXIS_THROTTLE_SET 1681363 *** AXIS: Cntrl= 66291 (0x000102f3), Param= 16383 (0x00003fff) AXIS_PROPELLER_SET 1681363 *** AXIS: Cntrl= 65764 (0x000100e4), Param= 0 (0x00000000) AXIS_RUDDER_SET All those events are from FSX assignments! In particular the AXIS THROTTLE SET controls will conflict with your two separate throttle assignments in FSUIPC! Disable controllers in FSX! You must NEVER have dual assignments for the same axis to the same action. It is asking for trouble! The documentation tells you this, and I note even the instructions for using that Throttle Lua add-on tells you to at least unassign them. You can do this, but be aware that FSX does re-assign automatically if it ever sees the controls as newly connected. Best therefore to only use FSX or FSUIPC for assignments, not both. Pete
  23. It is definitely behaving strangely, though. There's no way FSUIPC can do that. It judst gets the named axes from DirectInput. Your INI looks innocent enough. Hardly much use of FSUIPC at all at present, and certainly nothing which will produce the symptoms you describe -- unless it is something in the Lua files executed by these lines 1=P2,14,CL2:T,2 2=P2,12,CL2:T,1 and one or other of those buttons is getting pressed or acting flakily. I see they are on the throttle quadrant. Try placing a ';' in front of both lines to stop them doing anything, just as a test. I see it is called "ThrottleManager" and it is certainly the most likely candidate. Just one other observation. This line in [JoystickCalibration] SyncSlopeThrottle2=20/21,41/41,63/63,71/71,92/91,101/100,117/115 is very unlikely to have anything to do with it, but it might be worth eliminating that too (; in front of the line). If neither of these changes makes any difference then the logging details are needed, bt it would then point strongly at a faulty device or driver. Regards Pete
  24. SUIPC most certainly won't be doing such things of its own volition! That's fine. You buy FSUIPC4. The purchase covers all versions 4.xxx. Well, it doesn't appear to be related to the assignment you've shown. Why not show me the INI file where all the settings are stored? That would be far for informative and definitive than a set of pictures! Yes, it means there's jitter on those other axes and this is being detected. You'd need to press the "rescan" button to clear it and make FSUIPC look for another. If the same one keeps cropping up you'd need to use the "ignore axis" button to tell it to (temporarily) not scan that axis. (All this is covered in the documentation). Either you are confusing yourself about which is X and which is Y, or your device is subject to interference between the assorted axes (I've seen this happen), and probably one or more has a tendency to jitter. It is not "weird", and you can deal with it using the ignore and rescan buttons as documented and mentioned above. Show me your FSUIPC4.INI file, from the FS Modules folder. You can also use FSUIPC's axis and event logging to see what is hhappening. Check the Logging tab -- you'll see the options there. If you (temporarily) run FSX in Windowed mode you can enable FSUIPC's Console Log too, and see what is happening in real time on screen. Don't mess with any other options there, though. Don't press "new log". If you want help understanding what the log is showing, paste a relevant section into a message here. Note that after tomorrow (Thursday) I am away on holiday for over three weeks (back November 5th). Regards Pete
  25. You have two assignments to these functions, both on your Saitek X52 Flight Controller: 6=R0,32,C1001,0 7=U0,32,C1002,0 and 8=P0,6,C1001,0 9=U0,6,C1002,0 The first pair is actually to a hat position and is set to "repeat whilst held". Why do you have this? Are you sure that's not the reason for your problem? If you still have a problem with this corrected (i.e. just delete those lines) then I really don't know. I've never used Squawkbox myself and can't really support it at all, but maybe others using it and this facility can help. Is there still a Support Forum or some place where users congregate? BTW, I assume you do know that you have to keep the button pressed whilst talking? Otherwise you'd need to use a toggle switch or two separate buttons. Regards Pete
×
×
  • 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.