Jump to content

rcbarend

Registered Users
  • Posts

    80
  • Joined

rcbarend's Achievements

Community Guru

Community Guru (4/7)

  • Conversation Starter Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done
  • One Month Later

Recent Badges

10

Reputation

  1. Hi Calvin, Glad you solved it. By the way: The Test gauge picture values show that everything worked as intended , EXCEPT the internal commanding of speed in FSX. Which would be a problem with install of FSUIPC, or any other gauge/module I use to command the long. speed in FSX. (this is depending on the Bounty version you use). But since it's working now ..... Best regards, Rob Barendregt
  2. At least you have proven (with the default 737 test) that it's not related to a specific aircraft, and has nothing to do with Afterburners. Other then a USB controller problem on your PC (not very likely) , the last thing I can think of: In the Setting-Controls menu, Tab ControlAxis, check that (for ALL controllers in the 'ControllerType' list) only ONE axis is assigned to Event 'Throttle Axis' or 'Engine 1 throttle axis'. Because if multiple controller axis (actually connected to the PC) are assigned to Throttle, they WILL influence eachother. Especially if one of those axis is jittering .... If that's not the case, I'm out of idea's ...sorry. Rob
  3. What was the result of testing this: 1. When the AB has kicked in (so at NO full throttle), press the key assigned to 'full throttle' (default: F4). WITHOUT touching your flightstick. 2. Load a flight with a default aircraft, like a 737 or 747. Shut down the engines, open the VC (or 2D panel window) that shows the Throttles animation). Now move the Throttle lever on your flightstick for idle to full a few times, and see if it visually 'jitters' at any point (especially in the nearly-full range). Rob
  4. Hi, This sounds like a Hardware problem with your flightstick (== dirt, accumulated at the end of resistance area of a potentiometer, or worn-out taper of the throttle potmeter of the flightstick ). Try this: When the AB has kicked in (so at NO full throttle), press the key assigned to 'full throttle' (default: F4). WITHOUT touching your flightstick. If that works OK: your flightstick throttle potmeter is the problem. Calibrating your flightstick won't help, since it's an intermittant problem. If it's dirt in the potmeter: the only thing that might help, is cleaning the potmeter with a contact-spray. But then you have to open-up the flightstick assembly. But if it's a worn-out potmeter, only remedy is to replace that part (or buy a new flightstick). Of course, my comment is based on you saying you have the same problem with other aircraft, and that re-callibration doesn't help. Another way of establishing IF it's a dirty, or worn-out, throttle potmeter of your stick: Load a flight with a default aircraft, like a 737 or 747. Shut down the engines, open the VC (or 2D panel window) that shows the Throttles animation). Now move the Throttle lever on your flightstick for idle to full a few times, and see if it visually 'jitters' at any point (especially in the nearly-full range). If it does, it's certainly a flightstick hardware problem. Rob
  5. Which FSX version are you using ?? (FSX-Acceleration, SteamEdition, ...)
  6. Willing to help, but I first need to understand what you mean by " I changed my throttle settings from prop to jet" . I really don't have a clue ... Rob
  7. You are right on both counts .... Both aircraft were made for FSX-Accell. Like using the default Accel HUD gauge and some new .air file tweaks, for the F14D. And using the TAILHOOK HANDLE Avar for control of the fandoors in the F35B Rob
  8. No clue why this happens with you, sorry. I'm using FSRecorder V2.01 (on FSX-Accell) for many years, and for hundreds of hours (recording flights upto 1 hour). But I never encountered any problem, other then the obvious things (like Lvar states not being recognised/recorded). But that's not a bug ..... One thing (if I recall correctly): if you remove the configured Temp folder, FS-Recorder will crash when you start using it. Another thing: where have you installed your FSX (standard location ? ) and therewith FS-Recorder ?? (folder/file protection issues in Windows) Rob
  9. Hi Chris, Euhhh ... long time ago we had contact .....LoL I think the problem MIGHT be (and has nothing to do with elevator sensitivity), is that you are trying to rotate too early in the takeoff run. I.e. that the Vspeeds (V1, Vr) you rely on, don't match the actual aircraft flightmodels. Best, Rob
  10. So do I ..... And trust me (as a designer, primairily for FSX-Accel), you still will if you keep using/exploring FSX. Even I (using/designing for FS9/10 almost every day, for some 18 years) learn new things every week. That's why I still stick to this "ancient", but very stable Flightsim platform. "Stable" meaning: it's limitations and bugs are mostly known and documented by now. Instead of chasing my own tail again and again as an alpha-tester, trying to keep up with an endless stream of bugs, (flawed) updates, even lacking features (compared to FSX), etc. etc., on the latest new "flightsim platform". Please ignore this remark (I just couldn't resist, sorry ...LoL). Whatever one prefers in being a flightsimmer. Just MHO; but wrong forum and off-topic. Cheers, Rob
  11. Yes, I received three PM's. And I replied to you via Email on the mail address you specified, some 6 hours ago. But maybe our PM's / Emails crossed eachother ..... Rob
  12. I DO understand your desire to code it yourself (because that's the best way of learning how to program in XML: by trial-and-error (that's how all designers learnt it) ). But there is no way to describe a "basic syntax" for such an XML gauge you are after. Because that would raise more questions then it answers..... There are many documents available that explain the basics of XML coding (see e.g. the PanelDesign forum here). And on other websites (like the WIKI section on FSDeveloper.com), a few examples on how to program a timer function. Rob
  13. In FSX/P3D there are many functions (events) that you cannot assign via the menu. Like TOGGLE_LOGO_LIGHTS. Moreover (that's is FSX, and I'm pretty sure in P3D too), you cannot assign a keystroke to a controller button via the menu; only an event. But since you allready know how to add/change stuff in the standard.xml file, the simplest solution is: - In P3D, assign the intended stick-button to e.g. "Lights -all (on/off)" - Close P3D, open standard.xml and find the entry that reflects this button assignment to event ALL_LIGHTS_TOGGLE. - Then replace ALL_LIGHTS_TOGGLE with TOGGLE_LOGO_LIGHTS. - Save the standard.xml, and start P3D Should work fine now .... Rob
  14. Willing to help, but I'm a bit puzzled as-to what you want: In other words: - The gauge starts a timer when some conditions, based on A:Vars, are all True. - When that timer elapses, a K:event should be issued. Correct ? If so: Should the timer be stopped (without issueing the K:Event) when any of the conditions become False before the timer elapses ?? If you PM me your Email address, I'm willing to make such a gauge for you. Just specify the A:vars and K:event, and the time. Rob
×
×
  • Create New...