Jump to content
The simFlight Network Forums

Pete Dowson

Moderators
  • Posts

    38,265
  • Joined

  • Days Won

    170

Everything posted by Pete Dowson

  1. Yes, but they must still support the Concorde! Try here: http://forums.flightsimlabs.com/index.php?/forum/3-concorde-x/ Pete
  2. Please see my edited reply above. Pete
  3. Yes, that's quite normal. Sound devices are programmed to repeat the last sound downloaded to them until it is changed. Pete
  4. The Google translater doesn't seem to do too well with this, but let's see: Hello, thank you for your track, I returned to the window on the left axis value spoiler on the right it is what my problem. After your documentation again Sev points are set, we have two windows on their right I have difficulty understanding this part. I assume "spoiler" is a mis-translation because nothing we have been discussing is anything to do with the spoiler (speed brake), right? Ignoring the above, for now: range to return the value in number, eg flaps incr = 117 F6 = 118 Flaps decr for F7, Flaps up = 119 119 = 116 Flaps down Should he enter the first order in the range of the upper or lower knowing that we start the procedure with the joystick down? For components can be divided into several ranges that correspond to crants (1,2 and 3)? Should we start with (down) Down, Inc, Inc, Dec, Inc, Flap1 or Down Flap1; Flap1, Flap2; Flap2, Flap3 I assume this is all about how to use the range setting options on the right-hand side of the Axis Assignments tab. Here I'm at a loss to know how to explain it differently from the way it is explained and illustrated in the Manual. Perhaps the French version of the User Guide would help? This is from the Documentation thread in Download Links: FSUIPC 4.60 documentation in FrenchFSUIPC460Francais --- Translation kindly donated by Mr. Philippe Hantzberg, 19th March 2011 With the assistance of concerned FSLABS I in my relationships Pierre CHASSANG (http://concordeperfo.../cps-cest-quoi/) who participated in the development of Concorde but slammed the door before its publication because he told me that the value has awarded buisness home before because the quality is plien Sharp bugs (PA and realism of flight), I found this myself but I hope it will fix soon. To return to the subject I have fear that the assistance is the author of their ambitions Sorry, I don't understand this bit either, other that it seems to imply you can't get any support from FSLabs, which seems rather strange. Regards Pete
  5. I have NEVER received keys by email when purchasing from SimMarket. As far as I knew you ALWAYS had to get your keys from your Account, which you can normally do directly you've had the purchase approved. Regards Pete
  6. There is only one very specific G3D.DLL crash for which FSUIPC patches a work-around in FSX. I'm sure it isn't related to anything you might experience in FS9. In all the years I was using FS9 I never had one G3D.DLL crash, and I've not heard of them happening before. I am therefore pretty sure that your crashes must be down to an add-on. You'll need to go through a process of elimination to ascertain which. No, not really. Sorry. No. I knew WHERE they were happening, and observed that it was the attempted use of a bad pointer which caused the crash. The routine in which it occurred was small and was merely going through a loop testing values before returning TRUE or FALSE. No other result was provided, so it was relatively easy to patch it to check the pointer for validity beforehand, and if invalid to simply do the FALSE return. I have no idea what the routine was doing nor what such a return might do, but since the end result displayed no adverse symptoms (or at least none that folks could detect), it was judged successful. There were several other crashes in G3D.DLL for which I knew the location, but which were in areas where there was no work-around possible without understanding what the code was doing. Regards Pete
  7. I'm afraid I don't understand any of this. Perhaps you could write in your natural language (French?) and maybe someone who understands French and English could translate it for me. Maybe even the Google translation would help. Regards Pete
  8. Well, I'll have a look, but I really do need to know which version of FSUIPC you are talking about! Are you using FS9 or some earlier sim, or FSX or later? i.e. FSUIPC3 or FSUIPC4? Have you made sure your version is bang up to date (3.999y5 for FS9 and earlier or 4.859r for FSX and later)? Pete
  9. The wel-known way to deal with that is use the NRZ (no reverse zone) calibration and set the "UseAxisControlsForNRZ" option. The only other way is to use the FSUIPC control to disconnect the throttles when the A/T is engaged. Not in FSUIPC. It sounds like the pausing is related to either a hardware driver (sound or joystick or video maybe), or possibly a virus checker in the background. Regular 3-8 second lockups when nothing responds are almost always down to low levels modules like that. Regards Pete
  10. In FS2004 and before the scenery complexity was readable, and may have been writeable (I don't know) via offset 0B60, but this isn't available at all in FSX. Similarly for texture quality at offset 0C92. Also in FSX only the cloud density and complexity values can be read and written at offsets 0254, 0255, but I don't know if these actually become effective without visiting the menus. In FSX the only performance-related adjustment you could certainly operate would be the AI traffic levels (assuming it is FSX traffic -- UT2 injected traffic is controlled via it's own shortcuts). See offsets 0250-0252. There are added FSUIPC controls to manipulate the main traffic levels too. Regards Pete
  11. Well, as far as I know, that system is automated, so I can only think that it is something to do with your ISP blocking emails from that source. Perhaps you should contact them? If it is only your FSUIPC key you wish to recover, and it is legitimate, give me your order number and I'll see if I can find it here. Regards Pete
  12. Numbers are numbers, not places for reading! if you are sending those numbers, then you know they are sent. That is ll that happens to them, they are a message, not a value or setting!!! They in themsleves tell you nothing, they are just commands to the sim. If you are operating the switches you know you are operating the switches. The messages tell the NGX you are operating the switches! The numbers merely tell it which switch you are operating. Pete
  13. I don't know which WAV it is. It is the sound produced by "MessageBeep(MB_ICONEXCLAMATION);" The sound is documented as "the sound specified as the Windows Exclamation sound." Pete
  14. Ah, my misunderstanding. Thanks for the clarification. Odd that they should have omitted these from the SDK. Pete
  15. Sorry, I have no suggestion. If the NGX does not provide this information, and doesn't even light its own indicators accordingly, then it is PMDG who must fix this. BTW, this: WARN_annunDOORS - $6510 is for all or ANY door open. It is the warning light on the right hand 6-pack, next to the MCP and should be lit for any door open. There doesn't appear to be any information at all abouty the overhead door indicators. Also, you seem to be thinking incorrectly here: Those numbers are Controls numbers, or Events. They are not offsets. You cannot read control numbers, they are simply numbers used in messages, not addresses of stored data values. Regards Pete
  16. Ah, but maybe their code only takes notice of the "FLAPS INCR" or "FLAPS DECR" controls, or even the old FLAPS 1/2/3 controls? If the documentation doesn't tell him then maybe some experimentation is needed. Nor I. I think he must go to FSLabs support for advice as I suggested earlier. Regards Pete
  17. Sorry, you mean you've lost or forgotten your account password? Please clarify. If that is all you mean, then you can get SimMarket to generate a new one and email it to you. Please just click on the "Forgot your password" option and you'll get to a screen which helps you. Pete
  18. Okay. Version 4.859r. The "log console on" control now actively makes the main FS window the active foreground window. Regards Pete
  19. Best always to use the same make of controls for both sides. What hand-made stuff is that? Well, it may be useful for a very small number of folks, and if it were easy to do I would certainly consider it. But it is not. It would be a major upheaval and too risky in terms of jeopardising FSUIPC reliability. Sorry. If your controls are really way different to each other, your best bet is to experiment using the axis multiplier/adder values to see if you can adjust each axis to suit its twin more closely. Regards Pete
  20. In FSX? Options-Settings-Controls: Uncheck "Enable Controllers". In FS9 I think there's a "disable joystick" entry in the settings menu. Pete
  21. Sorry, but that version is far far too old to support. You need to update to a supported version first, no earlier than 4.853. Regards Pete
  22. But the A321 has flaps, the Concorde does not. Why are you expecting a flaps control to work on an aircraft without any? You are not making sense I'm afraid. If you want to operate the visor, assign buttons or switches to the appropriate visor controls. don't try to treat it as flaps when it isn't! What is the "A + CA" by the way? What is it yuo want to send me? I do not want pictures, thank you. Pete
  23. They are simple controls, not axis assignments. If you want to use a lever to send normal FS controls you have to create regions of the lever position in which those controls are sent. That is on the right-hand side of the Axis assignments tab. Please read the User Manual! Regards Pete
  24. First, it would be best to read the axis assignment chapter in the User Guide. Pressing 'OK" will close the dialogue, no need to do that before assigning all - and calibrating too. As further clarificationThere are three ways of assigning them -- two of them "to FS control", which presents you with the same controls as FSX uses -- Axis throttleN set controls which would be just like assigning in fS9 or FSX, and ThrottleN set controls which are like assigning in FS95, FS98 or FS2000 -- and one via "direct to FSUIPC calibration", which is more efficient because it avoid messages going to and from FS each time you move the throttle. Different methods suit different add-on aircraft, depending upon how they were coded. No. I would have thought it obvious that throttles 3 and 4 are the 3rd and 4th throttles. There are 4 engined aircraft you know! FSUIPC provides separate reversers for each engine. You would have seen these listed if you'd read the User Guide. I shouldn't need to repeat it all here. Calibration. That's what it is for! The "somewhere" you should start is reading the documentation. It is all there Regards Pete
  25. Sorry, I do not know., except that the Concorde had no flaps in any case. But you would be better off asking in the FSLabs support forum. See also http://www.airliners.net/aviation-forums/general_aviation/read.main/240195/ 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.