Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Everything on the TQ6 acts like a normal Joystick, so its axes are assigned like normal joystick axes and its buttons like normal joystick buttons. There are facilities in FSUIPC for it, but they are minimal (what can they do that normal assignments cannot?), and they are inhibited by default because otherwise the buttons register twice in FSUIPC's button assignments -- once as joystick buttons and once as GF buttons. This makes assignment difficult and confusing. If you really want to enable it in FSUIPC you have to add the documented PollGFTQ6=Yes parameter for it in the INI file. But I've no idea why you'd want to do that. Pete
  2. There's never anything whatsoever of FSUIPC outside of the FS Modules folder -- certainly nothing that can be used by it or FS -- so you must have simply not actually deleted the right file the first two or three times! Regards Pete
  3. That's a first! It has never actually been found "impossible" before, despite all the obstacles Microsoft throw at it with more and more security traps in Windows! Logs are simple text files. Just read it with notepad and paste it into a message here. There may be two logs -- an Install log, and another log, the run-time log. If the latter exists then FSUIPC was actually installed okay, so you may be misunderstanding your problem. Please always state the VERSION number of the FSUIPC4 you are trying to install. Note that I am away on holiday from Saturday 20th to Saturday 27th inclusive, so if I don't see any useful information before then it may get delayed over a week unless someone else can help. Regards Pete
  4. No, I remember this much from Commodore Pet Basic days (1978-80): The Basic "chr" function takes an ascii byte and turns it into a Basic character. That code is exactly what I said you might need to convert C strings, read from FS, into VBasic strings. It is concatenating each ASCII byte to build up a Basic string. Yes, you read that from my previous reply! I don't like Basic at all, but then I'm a programmer. It is intended for non-programmers., but I think that only applies if you don't want to use it for anything real, where it has to talk to other things. Then it gets more complicated that C, in my opinion. Why not look at Paul Henty's DLL? Most folks seem to find it much easier. Pete
  5. Not sure why you've replied with only a quote of my message to you? Pete
  6. I've no idea. It depends how it is implemented. Some hardware units make themselves look like several joysticks in order to overcome the limit on the number of axes and buttons imposed by the Windows default joystick drivers. Many hardware developers do not want to do specific USB drivers which have no such limits because it means they have to provide specific interfaces for each possible simulator or game, and pay Microsoft a fee if they want them approved for 64-bit Windows. It should be easy enough to find out, though. In windows "Game controllers" do they look like one device or several? Also check your FSUIPC INI file -- look for the [JoyNames[ sectrion. That lists each joystick type device which Windows identifies, with the Windows identity number (0 upwards), as long as this doesn't exceed 16 devices (0-15). FS itself should also be listing all of your joystick type devices, so you can make assignments there. If they've implemented them in such a fashion, yes. I've no idea why FS doesn't see the rudder. Are you sure it isn't listed in its device drop-down? (A lot of folks don't seem to realise that FS lists devices in its own drop-down list. you only see assignments for one at a time). Note that if you update Windows (a major update only), or simply plug USB devices in differently, it is likely that those joystick numbers will change. This is why FSUIPC offers the facility to assign letters to the devices instead, and then it tracks them by name and GUID (a unique device id). Regards Pete
  7. Please try downloading and installing the current interim update, from the Download Links subforum. There have been some recent changes in Windows which seem to have changed security settings and prevented proper Registry updates. I programmed around those when I found out. It doesn't seem to affect everyone, though. The other thing to try s to re-run the Installer, but do it "as administrator" (i.e. right-click on it and select "run as ..."). If it still doesn't work please show me the Log files -- there should be one for the Installer and one for FSUIPC itself. Paste them into a reply. Regards Pete Regards Pete
  8. Ah, that sounds like a pirated key -- most of which are detected by FSUIPC automatically (but still they try!) Where did you download from? There are most certainly no pirated key files in any of the places where I supply FSUIPC. You wouldn't have had to delete all the files. The only one dealing with the registration is the KEY file. Thanks for the feedback. I hope that this download you did is not used by many. The official site, as linked by the SimMarket purchase page, is the only official one for full installation FSUIPC packages. Regards Pete
  9. Ah, just looking back it hadn't actually clicked in my head that you referred to "RunReady", a WideClient parameter. I was thinking of the Run parameters in the [Programs] section in FSUIPC's INI file! That makes a bit of a mockery of all my talk about Profiles and [Auto] sections. Sorry! I must have been confusing you a bit with all that! I think I started off wrong after your intro saying "as I cannot add features to fsuipc ...". This actually makes it even more important to do it via the Lua system. I really wouldn't want to try doing it using extensions to the "RunReady" part! Would you mind if I changed the title of this topic (if I can, that is)? It isn't really applicable to the true subject and I'd like to be able to find it more easily on my return. Regards Pete
  10. Oh, yes. I have hundreds in mine! FS recomputes that hash number for every small change, so as I'm testing and debugging I get one added each minor change! If you know what to change them to -- which probably means disassembling both versions of the DLL or GAU file with something like the IDA disassembler and working out where each entry point has moved to. It's the sort of thing i had to do for my FS hooks in FS9 and before, each time MS updated FS. Somehow I think it is easier to rebuild them, letting FSUIPC do all this sort of work! Yes. Others have noted that it might be better to wait until things settle. Regards Pete
  11. I'm still here so I see it, but I don't understand why it is posted within a thread entitled "Multiple keyboard support for FSUIPC". Two things: 1. The parameter must be written BEFORE the 0D70 write, as it is the latter which triggers the action. 2. The parameter is a NUMBER, not a STRING! The number is probably derived from the first 4 ASCII character values: "myst" would give 0x7473796D. Well, certainly not via an integer parameter. You could use the user offsets 66C0 - 66FF if your string isn't too long (max 63 characters + 0 terminator there). What's the application? Could the string be anything, or only one of a known set of strings? If the latter it would be better to make a table in the Lua of all the strings which can be used and then just pass the index as the ipcPARAM. Regards Pete
  12. Yes, I noticed that the PMDG code seemed to intercept some keypresses before FSUIPC can get to them. Most odd -- it only seems to apply to a few. Mouse macros work by determining the address (inside the aircraft DLL or GAU code) of the routine to be called when you press the button -- the same code it determined was called by the mouse click. In the macro encoding, like "RX4df00*X8bcc" the number X4df00 is the offset address of the code to be called from the start of the named DLL or GAU file. Obviously, if a different version with the same name is loaded, the code being called could have moved. FSUIPC tries to prevent FS crashing as a result of things moving by checking that the bytes at the address are correct. That's the purpose of the check value X8bcc. If the check fails, the macro does nothing. If you update an aircraft for which you have made mouse macros, you have to remake them all to update these addresses. There's no easy way I'm afraid. You cannot actually have two copies of the same file with the same name in the same folder. Windows won't allow it and renames the second with "Copy" or similar. I don't think any of this is anything to do with FSX.CFG Regards Pete
  13. I don't know Basic enough to help very much I'm afraid, but the most likely problem is the way VB handles strings. I see you declared the reception area for the 256 bytes just as a "string", but how does VB know how much memory to provide? The Process call will write 256 bytes to whatever place in memory you specify, but if that isn't already obtained and sized it will almost certainly cause an Access Violation (crash). I suspect you have to declare the input area as a byte array of 256 elements, then, after the Process call, build your string byte-by-byte using concatenation. I also have the suspicion that VB uses unicode or some other 16-bit character format, not the ASCII single byte characters used in C, FS, and Windows. Have you thought of using Paul Henty's interface for VB instead? I think he sorted all this stuff out quite neatly. See "FSUIPC Client DLL for .NET - Version 2.0" in the Download Links subforum. Regards Pete
  14. Yes, I think so. And it avoids messing in very old code and risk introducing new bugs. Lua is easily expandable by adding new library functions. The Lua interpreter never "stops", only the individual threads. However, I can see the need for the facility to start a program running, via a simple Lua statement, without that Lua thread continuing to run. After all if it hasn't anything else to do there's no point in hanging around. So maybe there needs to be three library functions: 1. Start a program which runs independently of the thread 2. Start a program which is terminated (kindly or by process killing) when the thread terminastes (tidily or forcibly) 3. Kill a program tidily or by process killing Of course 1 and 2 would probably be the same function with different options (much like the Run parameters in the [Programs] section). You might also need auxiliary functions: 4. Test if a process was running 5. Bring a process Window to the foreground (gives it keyboard and mouse focus) 6. Put a process window to the background 7. Minimize, maximize, restore a process window. In fact, overall it might be quite extensive, so I would probably collect all such functions into a separate new library. Have to think of a library name: maybe "run" or "ext" (for "external process functions"). BTW are you using FS9, or do you have a really very powerful PC, because the thought of having up to 64 or 128 processes running alongside FSX in the same PC is pretty horrible. What performance can you expect? On the better side, having such facilities in a Lua library means I can easily add the same facilities to WideClient, so these things can all be done on networked PCs too (where, in my opinion, they all belong! ;-) ). The [Auto] facilities in FSUIPC are explicitly designed to start and stop macros and Lua programs based on aircraft name -- or Profile name, which may be more convenient. This would be a far more efficient way of doing such things, though of course with Lua you could do it your way if you wished. It is interesting in any case, and I'd enjoy implementing such a library. Remind me in September. Regards Pete
  15. Could you or your friend tell us what the problem was and how it was solved, please? I'm sure others would like to know, and I certainly would too so I can help more directly in future. You see there has been at least three such questions in this thread, but no real answers from anyone about what they did to proceed. Things improve for everyone with feedback. Thank you, Regards Pete
  16. No! Why are you using such an out of date copy of the documentation? The 4.70 version was included in the FSUIPC SDK version released in April, at the same time as FSUIPC 4.70 itself. This applies to both the SDK in the main Schiratti "Dowson" page and the one in the Download Links subforum! The 4.40 version is not available anywhere that I know of. There was a 4.60 version, last year, well after the 4.40 and 4.50 versions. It is always updated at every major release. The only changes in offsets since the 4.70 edition will be listed in the Notes on the subsequent updates, also in the Download Links subforum. THat's only 0334 to 0340, listed in item 24 there. Regards Pete
  17. Why an offset? How would that get set? If you wanted Aircraft or Profile-dependent program loading, why not have it implemented in the same way of all the other Profile or Aircraft-specific facilities, like the Keys, Axes, Buttons,, JoystickCalibrations and Auto macro running facilities. Possibly the best way for me to provide an equivalent facility would be to add program running facilities to the Lua ipc library, alongside the "ipc.runlua" and "ipc.macro" facilities already provided. Again, I'd rather implement it in a more flexible way, such as additional Lua facilities. Wouldn't that meet the needs more flexibly? The conditions under which programs are run could be as simple or as complex as you liked, that way, and the Auto section method of running Lua programs in Profiles or Aircraft-Specific circumstances would be an easy way to relate them to aircraft being loaded. The only thing i'm not clear about is terminating such programs. Is this also a requirement? Automatically or again by Lua library function? What happens if the Lua program is terminated -- should that terminate the programs it spawned, or not? It needs some thought. I'm not really in favour of messing with the current [Programs] facilities -- they are unwieldy, not suitable for expansion, and certainly not as flexible as I like new facilities to be these days. I'm on holiday from this coming Saturday for a week or os, so I can't really do anything till September now. But think about my suggestions and let me know. I will too. I'm sure something worthwhile could be done on those lines. Regards Pete
  18. Not sure what you mean by that. Sorry. What sort of reaction? One that merely asks you to read the thread which you knew was relevant and which had answers to your questions? I don't understand why this is a "sort of reaction" to object to? Can you explain what the problem with it is? Okay, and what was the result? Please do tell me. Ah. So, can you please show me the Log file from the attempt with the updated version? I.m very sorry, but you surely understand I cannot help without information. Regards Pete
  19. Sorry, no. Where and when did you post it? I've not seen any such thing here in the Support Forum. How long ago was this? Oh, only two days you say? I've certainly not seen anything that hasn't been answered for two days. That tends to only happen when I go on holiday (as I do this Saturday, by the way). If you posted in one of the Sub-Forums by mistake, other than the "User Contributions" subforum (and in relation to a contribution you were making for others to use), then it may have simply been tidied up as being not relevant, if it also looked old and not followed up. If it is something you you want help with, or are asking about, please try posting here in the Support Forum. It must come here if you are looking for answers to questions as otherwise they might not even get noticed. The other sub-forums contain more permanent information and files rather than support questions. I am out for a few hours this evening but will deal with anything here before I go to bed tonight. Regards Pete
  20. you should really try to keep up to date with FSUIPC in any case. There's no change to how it checks registrations during entry. You are making a mistake. All three parts must be identically correct to those originally used -- name, email, and key. Use cut and paste if you are not sure what any of the characters are. Regards Pete
  21. That looks okay. You have the offset, the size, the description, the read status and write status, each on separate lines. To convert that to CSV you'd need to remove the new lines and replace them by commas. I couldn't do anything better from Word. Whatever way you try, there's going to be a lot of work involved editing into a CSV format. I'm not sure what that message was about? Ah, so the FSInterrogate method came in useful? Note that it's FSI files haven't been updated for quite some time. It won't have many of the more recent offsets listed, and still has errors which I try to correct now and then. Regards Pete
  22. Ah, at last! ;-) I'll upload it to the Download Links subforum, along with the same FSUIPC3 fix (3.997n). Thanks, Pete
  23. Please try FSUIPC 4.726. This has to be my last attempt before September I'm afraid. I've tested as best I can and "dry run" it with assorted near-boundary conditions. Regards Pete
  24. Please please please DO read the other replies I've already made in this thread! You haven't shown me the FSUIPC log as I've mentioned in at least two replies here, and I assume you also haven't tried the latest interim update as I've also suggested in this thread twice already, the updated version which should fix this? Sorry if I have to reply like this, but I really don't see the point of repeating myself all the time, especially not in the same thread which just needs reading before adding to. The idea of a Forum is that everyone can learn together, not get individual answers to exactly the same questions. I had all that work to do when I did email support. Forums should be better, don't you think? If you do try the suggestions and they work, well and good, please do come back and say so (others don't seem to always bother). If it doesn't then please at least show the files I ask for, in this case specifically the FSUIPC log file, not the Installer's log. Thank you! Regards Pete
  25. You posted a question as a new thread in the Download Links subforum, not the place for support. I moved it here for you. No. It is a Word document. The nearest you'd get is to use FSInterrogate. I don't know what format the fsi files are, but i think there's an export facility. you could try that. What sort of strange results? What pdf viewer are you using? Some allow you to save an unprotected PDF as a text file -- Foxit PDF Reader has such a facility, for instance. 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.