Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. As far as I am aware, you can trial PM modules without WideFS. Just use them on the FS PC. Otherwise, this is a question for PM support or sales. They used to do time-limited trials, but this is up to them. Pete
  2. Please answer the questions first. I don't want a file yet! Pete
  3. Please ask again on Monday or later, after I've caught up! ;-0 Pete
  4. You are using an out-of-date PFC driver, then. Maybe FSUIPC as well. I've got no such instructions or program which installs both FSUIPC and PFC. It sounds like you are getting your files from elsewhere. Try the official Pete Dowson downloads! If you download from the PFC site, use THEIR support, not mine. I am not in control of their files. Pete
  5. You must have downloaded an old version from a French website. The standard issues made by me are all in English. Sorry, no American, only English. I'm sure you'll muddle through though. ;-) There's no version 9.0. I think you must be talking about a different program altogether! Pete
  6. More than a problem, almost an impossibility. Though perhaps i can figure out some logging that would help me. remind me on or after May 9th, when I'm back. Regards Pete
  7. You don't need 3.65. It is unsupported. The current version is 3.90. Each version is a compatible superset of the previous one and is better is all respects. Pete
  8. Search the LOG for the actual words Rudder and/or Trim, as I said. I'm afraid I won't be able to help now till after May 9th as I'm off in a few hours and not back till then. Regards Pete
  9. Really? I've found almost no switches at all that respond. Which ones are you talking about? Hmm. Not sure why it would work with "tab" but not subsequently, because they do the same thing really. Of those aircraft I've only got the 747, so perhaps you can list those functions which don't work there, and show me the Macro parameter lines from the file corresponding to them, and i'll check here. But that will be after May 9th as I'm away in a few hours now and won't be back till then. Please find examples for the PMDG 747 so I can try here. Regards Pete
  10. The FSX offsets are, on the whole, just a superset of those for FS9, which in turn was a superset of those for FS2002, and so on back to FS98 and CFS1. The whole point of FSUIPC (the "U" standing for "Universal") in the first place was to maintain ongoing compatibility, so you could use programs designed for one version of FS on the next rather than having to wait for re-writes. Regards Pete
  11. I don't know why you are looking in the INI file. Who mentioned that? Try searching fro the English words "Rudder" or "Trim"! It is the rudder trim you said was going awry, wasn't it? So why not look to see if such events are actually occurring as a first step? Paste the log here if you still do not understand, or English is not your language, and I'll have a look. But if it is not today, I'll not get to it now till May 9th as I'm away for the week. Best list all the add-ons you are running in FS too -- I've never heard of a runaway rudder trim problerm as virtually nothing uses the rudder trim in FS at all. Pete
  12. AdvDisplay is obsolete and unsupported. I replaced that long ago with superior facilities built into FSUIPC. Please check the early parts of the FSUIPC user guide. Regards Pete
  13. Yes -- because your AV package has a specific bit pattern listed as that virus, and it thinks it finds it in the DLL. But the DLL is not only compressed, which makes it look mostly like a random jumble of bits, but it is also SIGNED with a very secure signature which prevents undetected tampering with an extremely high degree of confidence, underwritten by GlobalSign. If you ever have any doubt just right-click on the module, select Properties-Version-Signature, highlight the signature listed and select Details. If it says it is "ok", then the module has not been tampered with, guaranteed. You should always report false positive virus indications to your virus package support -- they will then add more data to their checking to avoid it happening again. Each version is obviously different (else why would i release it?), so the bits making up the compressed version are also different. Obviously. As I said, there's a later version in this Forum in any case. I can't update the Schiratti site very often -- Mr. Schiratti seems unresponsive at present in any case, so most of my packages are becoming outdated there. Regards Pete
  14. But that list is specific for 12 bits. The very first list I gave you is completely general for ANY size - 4, 8, 12, 16 .... 64 bit values, anything! Decimal Hex Binary 0 0 0000 1 1 0001 2 2 0010 3 3 0011 4 4 0100 5 5 0101 6 6 0110 7 7 0111 8 8 1000 9 9 1001 10 A 1010 11 B 1011 Just look up each group of 4 bits. It's so easy! I don't understand why you are still making it more complicated! Anyway, I'm not answering any more here. I've run out of ways of trying to convince you to take the easiest ways. Regards Pete
  15. The Schiratti site belongs to Mr. Schiratti. I have no more access to it than you, but it certainly downloads fine. I suspect you have an anti-virus program which is falsely detecting a virus. There have been a couple of other reports. You need to sort your AV out. There is a later version in the Updates Announcement here, by the way. There usually is. Regards Pete
  16. But why not just split the 100000 into groups of 4 bits: 0010 0000 which (as you can see from the first table I gave you) is 20. That's the whole point! Each hex digit represents 4 binary bits, that's all!! Pete
  17. Powers of 2 apply to individual bits, according to their position in the complete number, the same as powers of 10 applying to decimal digits in a decimal number. For some reason your table lists powers of two for hexadecimal digits 0 - F. Why? One hexadecimal digit represents no powers of anything -- it's just one digit of any hex number, the same as 0-9 are digits in a decimal number! You seem to be wanting to make something very complex and mystifying and completely wrong out of something basic and simple. Please take more time to consider how decimal numbers actually work. Then apply that to binary numbers, where you only have two digit values 0 and 1 instead of 10 (0-9). Once you've got that far, you can simply group 4 bits together to give you hexadecimal. Pete
  18. Because the value "9" is binary 1001 which is TWO bits -- bit 0 and bit 3, so switching both those buttons on. Button 9 is bit 2^9, or value 512 -- if you write 2 bytes to 3340. Or you could view it as bit 1 (9-1) in the next byte (3341) and write 2^1 = 2 to 3341 instead. Bear in mind that this only switches the button ON. To switch it off you'd need to write 0 to that bit. Also bear in mind that by writing a byte you affect 8 buttons (8 bits in a byte), by writing a word you affect 16 buttons. You should really read the byte, OR this bit in (to switch on), or AND the bit out (to switch it off) then write it back. If you are programming a button via FSUIPC options then just assign it to Offset Byte Setbits with offset 3341 and parameter 2 to set the button ON, and Offset Byte Clearbits with the same offset and parameters to switch it OFF. If you want to toggle it on and off alternately with one button you could use Offset Byte Togglebits. Regards Pete
  19. Well, that's not relevant at all to want you want to do in GFdisplay, but if you want that, then this: 2 6 E 9 0010 0110 1110 1001 4 64 16384 512 still makes absolutely no sense. The highest bit, the "2" is "26E9", is bit 13 so, as I so carefully explained, it represents 2^13, or 2 x 213 times. ie. 8192. There are then 2 bits in the next hex digit (the 6), so how do you get 64? Ditto how do you get 16384 for the 3 bits in the 3rd hex digit, "E"? And the last hex digit is 9, which, wonderfully simply, represents decimal 9 too. But you get 512 from somewhere? How? Even if you are reading right to left for some reason, your numbers make no sense. Can you explain them? Like decimal numbers, binary and hex read with the high values on the left, the low values on the right. why would you think everything was reversed in order just because we use a different base? I really cannot help any further sorry. I suggest you get a simple book on computers. Regards Pete
  20. What exactly is a "list of FSX addresses"? Do you mean offsets accessible via FSUIPC? If so it's all in the document of that name in the FSUIPC SDK. Pete
  21. Training movie? Sorry, I've no idea what you are talking about! If FSUIPC's installer cannot find where you've installed FSX or ESP then tyou've either not installed it, or the registry entry pointing to where it is is incorrect or missing. Maybe you moved it manually after installation. The FSUIPC installer provides a detailed log, which you can save using the facilities in its File menu. Please do that and show it to me. Pete
  22. How can you get lost here when all we are doing in numbering the bits. the same as numbering houses in a road or students in a line. Look, if I have a 4 bit number: 0 1 0 1 (which represents 5 in decimal), the LAST bit, the 1 at the end, is bit 0, the one to its left it bit 1, the next is bit 2 and the 4th from the right is bit 3. With a 16 bit number, the 16th bit from the right is bit 15 (it is always one less because we count from 0, not 1). What system of bit numbering are you using which gets up to 16384 bits in a 16 bit vaslue? And goes up and down? Can you explain what those values, 4, 64, 16384 and 512 are supposed to represent and how you arrived at them. you've got me completely lost. i've no idea how you are thinking, even! :-( What do you mean by "last" bit, exactly? It isn't a very precise term except in an ordered list. The last bit reading left to right is the right-most bit, the least significant bit, or bit 0. I've no idea how you are using your "English" words I'm afraid. Pete
  23. Sounds like there's some assignment not working as you would wish for in FS. If you have FSUIPC installed, you could use the Logging facilities to see what is happening. enable Button, Event and Axis logging. It will show all those types of commands getting to FS, easy to understand in the LOG file as the commands (controls) are named. Regards Pete
  24. Are the files you got for your VRinsight MCP suitable for the 3D VC? This is getting very confusing here, I really don't know what you are using or doing for what! 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.