Yeah it's got me stumped mate, not really bothered though to be honest lol.
Support Help For Heroes!
Thank-you for the response. I had tried either lighter, or darker alphas, 32-bit 888 .dds sheets. Neither one will yield respective textures, and I find within the .mdl that there is no reflective scale set for the wings/fuselage, nor an environment map. So, basically the diffuse alpha isn't doing anything. With a tool like MDLMatxx, I could theoretically add the reflective scale, and adjust it, however, without a reflection texture assigned to that diffuse, It will still not work. I Had tried modelconverterx to test this theory, and it does work, however the export back to .mdl with an aircraft causes anomalies, seeing as they have not advanced that tool to be able to handle flying aircraft exports.
This is as far as I have gotten thus far.
Support the C-170B Project; send a private message.
Ahhh, got you, no it's shiny, not reflective.
Regarding the throttle issue, I compared the throttle animation in the vc with several other aircraft and the Sea Fury throttle animation is jerky compared to others. I know nothing of the design parameters in constructing animated parts but it is as if there were not enough measurement points along the throttle axis.
The throttle animation is perfectly smooth on both my test machines and all the beta testers so I'm confident the issue doesn't lie there.
The only person who had an unusable throttle had his throttle controls set up for engines 1 and 2 rather than just throttle, this has been fixed by updating the gauge to look for the Throttle or Throttle1 values. While it wasn't working he was getting occasional jerky animation of the throttle as the gauge fought his inputs.
The people who're getting jerky animation can you confirm what control axis you have set up for throttle control? i.e. could there be two inputs that are causing the gauge to fight itself?
I'm using a Thrustmaster T16000M using the single default throttle.
hoping to give my little contribution here is what I found out after buying today the Sea Fury and testing her with some different control inputs, here is what I found out: I have FSX with controls (Sidewinder FF2+CH pedals & PRO THROTTLE) mapped via FSUIPC and I downloaded the latest centurion.dll from Flying Station site.
with all the possible configurations if I put the throttle to idle position, it just jumps back to full power out of control and sometimes it ends up like this:
the only way I found for using the centurion.dll controlling the supercharger and the BOOST\RPM has been mapping the throttle control to "throttle engine 1" not "general throttle" via the FS axis assignment and not via FSUIPC, this gives me full contol of the engine with the prop on auto and\or full forward position while at low altitude if I "slam" the throttle forward the BOOST goes immedidiately to 20psi, then the autoboost control intervenes and brings it back to normal; can this throttle problem this be fixed manipulating the "centurion.dll" because if I cut out the throttle control via joystick and use the keyboard, there is no problem at all ?
Thanks in advance
Yeah that's what I'm finding too, te throttle open fully and throttle cut keys work fine, but the increase throttle incrementally I think it's called which my throttle is mapped too gets this jerky response!
Support Help For Heroes!
I don't know for sure what happens if you use FSUIPC but I'd guess there's a conflict between it and the gauge as both are trying to take control of passing throttle position to FSX, if FSUIPC 'wins' then Centaurus.dll won't get the actual throttle position and so just passes 0 to FSX.
I'm not sure how you're getting to 20" of boost, it sounds like for some reason Centaurus.dll thinks the throttle position is greater than 100% for some reason. I'll see if there's an easy way to add a sanity check to the code.
Roger, what is your joystick's throttle actually assigned to in FSX?
There's a new Centaurus.dll on our forums, this may stop the over boost problem although I can't be 100% sure as I haven't found a way to replicate the problem in the first place!
Last edited by peter12213; May 28th, 2012 at 12:12.
Support Help For Heroes!
1st, Thanks for the help with the new dll file, I tried it, but the throttle keeps jumping to the full\idle position when I have the control mapped via FSUIPC, the only way I found for it to work is to bypass FSUIPC completely (like aerosoft huey) and assign the controls using FSX joystick "default axis\mapping control".
Using the above solution and keeping the original dll I've been able to assign the throttle control to "generic throttle\all engines axis" (not engine 1 throttle axis) so that now I don't have to re-map the throttle axis when flying twin engines.
Again, when FSUIPC is bypassed everything works fine...at least for me
I couldn't resist and just had to purchase this beauty.....
Firefighters walk where the devil dances.
There are currently 1 users browsing this thread. (0 members and 1 guests)