Aces High Bulletin Board
General Forums => Hardware and Software => Topic started by: FLS on May 20, 2010, 03:12:55 PM
-
Do not update the Logitech G940 firmware. You will ruin the FFB. The firmware update does not fix anything, it just ruins the one thing that worked correctly.
-
Logicrap... why am I not surprised.
Sorry to hear this.
-
Oh crap. Thanks for the heads up.
-
Do not update the Logitech G940 firmware. You will ruin the FFB. The firmware update does not fix anything, it just ruins the one thing that worked correctly.
Wow I mentioned this several hours ago HERE (http://bbs.hitechcreations.com/smf/index.php/topic,289489.msg3677234.html#msg3677234)
I also explained why this is.
I've heard the 5.09 software is good, but don't update the G940 firmware, until there is a way to revert it back if need be.
-
Yea I found it out the hard way. Does anyone know how to get rid of the firmware update?
-
You'll have to wait for Logitech to release a fix. There's enough people complaining that I expect they'll have to do something. The worst part of it is that they ruined the trim forces in order to try and fix an issue that they know is caused by the FFB API.
-
I love how someone ask a question in here and then someone comes in and gives opinions of something they have no interest in. If you don't like the equipment then go play with yours and let the person get the answer he wants without having to listen to garbage.
-
I love how someone ask a question in here and then someone comes in and gives opinions of something they have no interest in. If you don't like the equipment then go play with yours and let the person get the answer he wants without having to listen to garbage.
Out of curiosity...
what part of
You'll have to wait for Logitech to release a fix.
didn't you understand?
-
It was in reply to the Logicrap comment. I think they have a great product with the G940. Like everything else it will have growing pains but I believe it will eventually get there. In fact I love my G940. Both of them.
-
Enabling features is one thing...making the devices function as necessary for longer than 1-4 months is something else entirely!
I got a similar reply from someone else in a similar thread to this I started.
It's a shame because a lot of times all it does is divert the thread from it's originally intended topic to a "lets talk about how much logitech sucks" thread.
-
It was in reply to the Logicrap comment. I think they have a great product with the G940. Like everything else it will have growing pains but I believe it will eventually get there. In fact I love my G940. Both of them.
Sadly the G940 is total garbage. I bought mine the day they came out and won't ever even spit on another logicrap product. Is a complete bust...
-
What problems have you been having with it Humble. I have had pretty good luck with mine so far.
-
What problems have you been having with it Humble. I have had pretty good luck with mine so far.
Wagger are you running Win 7?
-
My stick repeatedly loses connection, same issue many have reported. It also loses FFB and goes floppy...
-
On both of the different FFB sticks I have had in the past, I'd experience something similar when the "deadman's switch" would engage - which would happen at times when I simply shifted my hand position. On both the Logitech Wingman Force (not the POS 3D, but the original stick with the 20 lb motors) and the MSFF I ended up defeating the sensor because the stick would go dead and I'd slam it to the stops when the resistence suddenly disappeared.
(Made for some interesting flying when that would happen)
You might try something similar and see if it eliminates the issue. I found that on one, I needed to tape a reflective material over the sensor emitter pair, and on the other, I used black electrical tape to "permanently" interrupt the beam.
I'm mentioning this because while I don't have a G940, in both instances with the sticks I had, it wasn't immediately apparent the problem with loss of FF was simply because the stick "thought" I'd let go.
<S>
-
I'm on my 3rd G940 (1st two replaced due to spiking on rudder axis). I have updated the software to 5.09 and applied firmware update, still have spiking on rudder which makes pedals unusable. I've tried maxing the hysteresis on the rudder axis to 255 and it doesn't help.
Running Win 7 and since all my G940s have had this problem, still wondering if its a driver issue.
-
Oboe: yes I am running Win 7.
Humble: I have not run into that problem since I first got my G940. Had that problem for about 2 weeks when I first got it. I have not had that problem since then. I did have that problem a lot when I used my X52, but I just kept a copy of my settings in a separate folder so i could replace them when it happened.
As far as spiking on the rudder pedals I think I had my first problem with it a few days ago. I went into the options, controls and selected the rudder then used the calibrate axis. After that the problem seems to have gone away.
The one reoccurring problem I seem to have is that lately I have is that my rudder either quits working all together, especially in the special events arena's, and occasionally will work for left rudder but not right rudder. Again I recalibrate and then calibrate the axis and it goes away. More annoying that anything but would love to have the problem fixed.
-
Wagger - sorry - I should've been more specific - Win 7 64-bit?
How about your toe brakes? The last two G940s I've had, the right toe brake has no scaling to the input - it's either fully off or fully on. Left brake works as one would expect though, with a full range of input corresponding to depression of the left pedal.
-
Oboe I am running Window 7 64bit.
My toe brakes work fine. I had some problem with them being reversed, brakes on and had to apply brake to unlock them. Just checked the inverted box on advanced settings. When you have your pedals selected up click on right brake and left brake and use the calibrate axis. I found this to be helpful in solving some of the problems you have mentioned.
-
Oboe I am running Window 7 64bit.
My toe brakes work fine. I had some problem with them being reversed, brakes on and had to apply brake to unlock them. Just checked the inverted box on advanced settings. When you have your pedals selected up click on right brake and left brake and use the calibrate axis. I found this to be helpful in solving some of the problems you have mentioned.
Can anyone describe exactly where to go to calibrate the rudder and toe bake axis? I cannot find the calbrate function within the Logitech Profiler software. I have the Pedals selected (they are pictured in the Profiler's window). For each axis, when I click ion it, I have a choice to "Select Axis Assignment", "Select Zone Assignment", or "Axis Properties..." I wouldthink it should be in Axis Properties, but al I can do here is Adjust Sensitivity, Dead Zone, Range and Mapping. I can also reverse polarity here. But no Calibration function.
If I chose Device/Game Controllers, and select the pedals and then click the Properties button, I can test the axes, but not calibrate (this is the window where the constant spiking of 20-30% in the rudder axis can be seen. If I click the Settings button here, I can change the Hysteresis values, but still no calibration function. (btw - Hysteresis settings have no effect on the spiking).
Where do I go to calibrate the axis?
-
The rudder and brakes calibrate when you move them to their limits after rebooting.
-
Hi FLS,
Do you mean reboot the PC, and after the reboot is complete, simply move the rudder and toe brakes through their full range of motion, without running any particular software related to the device? Does that also work for joystick and throttle?
-
I wouldn't reboot just to calibrate the rudder but in effect it's recalibrated every time you reboot and move the pedals to the limits. You'll notice the difference between the first time you move the pedals, when the indicator jumps to the end, and the second time when it moves smoothly along with the pedal.
I think Wagger is referring to calibrating in Aces High.
-
It's worth a try, both rebooting and trying in AH, though I'm sure I've done the AH one on previous units. AFAIK calibration just matches the limits of the device's travel to the game's expected limits of input for that axis (could easily be in error here) so not sure it would have much affect on a device that sits and spikes 20% of its range with no input whatsoever.
-
*DISCLAIMER*
I do not own or nor have I had a chance to use the G940 controllers
but in regards to installing any programs/software/firmware/devices/controllers/ on a Windows 7 OS...
may I make a suggestion:
I highly recommend going back to the old way of when installing any software, always install it to it's own folder in your root directory
example: make a new folder in the C:\ root directory....... and forgo trying to install anything or letting anything default to your C\program files(x86) or C:\program files(X64) folders........
and always make sure you are installing your stuff while signed on as an administrator......
also if you have more than one user using the PC< make sure you right click on the software and click run as administrator, or make sure this is checked as being so
just a suggestion
( another note - on ym Windows 7 installation, I only have it setup to be just me ( 1 User ) and I also have disabled the UAC to where it never pops up those stupid warning messages, so I can avoid any possible conflicts ......... however do this last part only if you are completely comfortable with the ins and outs of windows 7 )
hope this is of some help
good luck
-
I wouldn't reboot just to calibrate the rudder but in effect it's recalibrated every time you reboot and move the pedals to the limits. You'll notice the difference between the first time you move the pedals, when the indicator jumps to the end, and the second time when it moves smoothly along with the pedal.
I think Wagger is referring to calibrating in Aces High.
I just finished rebooting, then moved both the pedals and toe braks through their full range of travel. Then I started the Logitech Profile and took a look at the axis behavior in the device/game controllers. Althought the random spikng with no input is gone, it still spikes in either direction if you try to hold partial input. Also, the right toe brake still has no scaling - it is either fully on or fully off. Left toe brake works fine.
Then I started AH and recalibrated the axies their. Same result as above regarding spiking on the rudder axis with partial input and no scaling on the right toe brake.
I always install as an administrator but use the default directory preferred by the installation package.
-
Humble I had the same problems you are describing . The firmware and software update fixed mine . If you guys are talking about the update messing up the trim forces . I also moved my usb to a port on the pc instead of an externally powered usb . What worked for ms sw ffb don't work for the g940 . Also there are some issues with FFB in this game . I have some conflicting info from htc about this .I am awaiting clarification on it .
http://bbs.hitechcreations.com/smf/index.php/topic,241749.msg2941721.html#msg2941721 (http://bbs.hitechcreations.com/smf/index.php/topic,241749.msg2941721.html#msg2941721)
http://bbs.hitechcreations.com/smf/index.php/topic,247921.msg3042019.html#msg3042019 (http://bbs.hitechcreations.com/smf/index.php/topic,247921.msg3042019.html#msg3042019)
Humble every problem you have stated here has been reported at one time or another in this game . Some time in version 2 things went wrong and the only thing I can find in BBS is reference to a temp. fix for a return to center problem . .The buffet fx is disabled . Stall gives buffet effect . I think before you blame logitech for the problems we need a properly working FFB system in game . BTW I have a reduced return to center effect on the ground . I don't get it in flight . The stick rttc force should be linked to stall , as the stall horn gets louder the stick should get sloppier . Less air pressure over the flight control surfaces the looser it gets . With the stall instead giving a buffet effect , you can't really tell if the G940 is the problem . With FX porked here it is entirely possible the stick is just doing what the game is telling it .
-
The rudder and brakes calibrate when you move them to their limits after rebooting.
Is the G940 similar to the X52 in that it constantly calibrates throughout your usage? I may be incorrect, yet that's the best description I can come up with for my X52. A few times I've entered games and upon moving the stick slightly left or right, the input was detected as motion fully left and fully right. I simply moved the stick to its maximum left and right positions and the stick was recalibrated. Absolute smooth input after I moved the stick to its full left and right positions.
So, is the G940 similar to the X52 in that it's "constantly" recalibrating?
-
Denholm I don't know about constantly but the G940 only has a few axis that need calibrating in the profiler. The stick itself and the pedals don't.
Hlbly I know you have an issue with FFB in AH but this isn't the place for it. The firmware upgrade porked the FFB trim forces. If you find that an improvement that's wonderful for you but it's not so great for the rest of us.
-
Denholm I don't know about constantly but the G940 only has a few axis that need calibrating in the profiler. The stick itself and the pedals don't.
Hlbly I know you have an issue with FFB in AH but this isn't the place for it. The firmware upgrade porked the FFB trim forces. If you find that an improvement that's wonderful for you but it's not so great for the rest of us.
The firmware didn't pork trim forces for me , fixed it on the ground for me . So how is this not the place ? You calibrate nothing in profiler . Calibration is of the throttles and all rotary wheels , in game controllers in windows . If you don't even have the right answer to a question how would you even know if I am on topic ? My G940 was unusable until the updates . maybe someone else has the same issue as me this time Since you imply this is your first "issue" with AH2 and ffb. What should it matter to you to what degree your FFB is porked ? Broke is broke . But never mind that I know how to change what you feel now back to what you felt before firmware update . That it is something that is neither intuitive , nor makes a bit of sense . That it is a weird combination to stumble on . I hope you have good luck figuring it out .Because the only way I will tell anyone is if they can give me something to fix my issue . Shouldn't take more then 3 or 4 hours so at least you got a shot .Yes return to center difference was gone in flight , was not there on the ground for me . Now I have it both places ,after trying a few hundred different combinations . Humble I had those same issues you describe . Mine had nothing to do with overheating , though that was what I was told was probable cause for it at logitech forums . You need a really clean install of new software . If you want pm me I will send you the instructions I got from the same guy who made my throttle panel lights work . Work like they do for indicator lights on your instrument panel in game . My auto pilot, landing gear indicator lights trim and dive brake lights etc all work with the same timing they do in game pretty cool imho .
-
But never mind that I know how to change what you feel now back to what you felt before firmware update . That it is something that is neither intuitive , nor makes a bit of sense . That it is a weird combination to stumble on . I hope you have good luck figuring it out .Because the only way I will tell anyone is if they can give me something to fix my issue .
That's nice that you think you have a fix but you won't share it. It sort of reminds me of your request for an AH profile for your G940. I remember I sent you one so I guess it's not really that similar.
With the stall instead giving a buffet effect , you can't really tell if the G940 is the problem . With FX porked here it is entirely possible the stick is just doing what the game is telling it .
That's BS. You have your axe to grind so you post nonsense. The G940 firmware update porked the FFB for many people in many sims.
-
I'm on my 3rd G940 (1st two replaced due to spiking on rudder axis). I have updated the software to 5.09 and applied firmware update, still have spiking on rudder which makes pedals unusable. I've tried maxing the hysteresis on the rudder axis to 255 and it doesn't help.
Running Win 7 and since all my G940s have had this problem, still wondering if its a driver issue.
Oboe this is a weird one bro . On my new rig tildeath built for me . Any seperate rudders I used spiked , only the ones on my twisty stick didn't . I dampened scaled and did everything I could to minimise what I couldn't fix . With the G940 I dont have spikes at all . I only found one thing that stopped my rudder spikes . When i used a program from logitech from their SDK . I had the spikes on my saitek peds my ch and some ch prop eds that were borrowed . The utilty stopped spiking on the 2 that I could try . I will find the link or put it on the muppet ftp server if you like . It is called poswdm.exe . Stop the polling see if spikes go away .
-
That's nice that you think you have a fix but you won't share it. It sort of reminds me of your request for an AH profile for your G940. I remember I sent you one so I guess it's not really that similar.
That's BS. You have your axe to grind so you post nonsense. The G940 firmware update porked the FFB for many people in many sims.
Do a complete uninstall of software including clean the registry . Install firmware without software installed . Reboot install 5.09 . In game controllers in windows uncheck enable centering forces . then in profiler under axis properties start reducing sensitivities until you get what you want . The reducing sensitivity of axis is when it started varying the return to center strength on mine . Worked for my buddy in IL2 as well . FLS the difference was that I was never rude to you when you helped me . Since you helped me ,what I believe in allows me no other action than this . Good luck .Also the ffb issue I have with Aces High you have too . I really hope this works for you , maybe then you might actually try the test I have suggested . And see it gives the result I know will happen . Maybe read the bottom post on the links i posted where the bug is acknowledged by htc staff . I think if you understood the most important aspect of FFB as far as information given to you , is not right you would be interested in it being changed as well .A friend of mine has a degree in programming . Two friends have used stick shakers in fighters , and I have used 4 different ffb sticks in several flight sims over the years .the programmer flies here I would need his permission to post his name . The name of the pilots are Former USMC Captain Justin Rempe pilot of FA-18s and former squaddy in AW . Col. Tim Parker USAF Academy graduate and child hood friend from Misawa AFB Japan where our dads worked together . Look them up . I have looked at this from every possible angle got questions answered from people who know . I also suggest looking at immersion corp they answer alot of questions MS can't or wont . Note you are still being rude . My ax to grind eh ? Why don't you try disabling stall in game leave buffet enabled go for a spin tell me what you feel . If my solution doesn't work I am sure you won't bother . If it does a few minutes of your time is not too much to expect is it ?
-
I know we're talking a different product, but at the time that I was beta-testing WB's III, I was using (first) a Logitech Wingman Force (not the POS 3D they sell today, but it's 20 lb predecessor) and then a MS FF2. And the sticks both were "flawed" in terms of how the sim supported them, albeit in different ways.
I spoke several times with the programmer, and found that at least at that time, they almost had to program for each individual stick they were going to support, because each stick would implement different portions of the API - and at times, even if they implemented the same API functionity, they would do so enough differently that it would "feel" completely wrong on one stick when
exactly right for another.
Which is a round about way of saying that if it doesn't work in AH, it might not be (entirely) the developers fault, as I don't believe that it's quite as cut and dried as it would seem it should be to implement FF.
All IMHO, YMMV - It's been 8 years or so of water under the bridge since those conversations.
<S>
-
http://cogadget.com/2009/06/02/logitech-launches-force-feedback-flight-stimulation-controller-g490/
(http://i270.photobucket.com/albums/jj110/GrnEagle43DHBG/logitech_flight_system_g940_1.jpg)
-
I know we're talking a different product, but at the time that I was beta-testing WB's III, I was using (first) a Logitech Wingman Force (not the POS 3D they sell today, but it's 20 lb predecessor) and then a MS FF2. And the sticks both were "flawed" in terms of how the sim supported them, albeit in different ways.
I spoke several times with the programmer, and found that at least at that time, they almost had to program for each individual stick they were going to support, because each stick would implement different portions of the API - and at times, even if they implemented the same API functionity, they would do so enough differently that it would "feel" completely wrong on one stick when
exactly right for another.
Which is a round about way of saying that if it doesn't work in AH, it might not be (entirely) the developers fault, as I don't believe that it's quite as cut and dried as it would seem it should be to implement FF.
All IMHO, YMMV - It's been 8 years or so of water under the bridge since those conversations.
<S>
Ghastly the issue here is that the firmware update changed the stick performance by adding a permanent centering force that cannot be turned off and it lost the linear greater G load = firmer stick effect. It's not an AH issue. It worked just fine in AH prior to the update. My gripe with Logitech is that they stated from day one that the lack of FFB in the center was not a driver or firmware issue. Then they porked the FFB in order to "fix" the problem in firmware. Some people aren't seeing a problem. I don't know if it's their preferences, perceptions or actual stick behavior that's different but the fact is that a lot of people have a problem with the update and no amount of tweaking or adjusting settings is making any difference. I'd be surprised if anybody at Logitech tested the new firmware with Aces High before releasing it.
-
Sorry, I wasn't meaning to confuse the issue with the G940 porked firmware - I was posting in response to hilbly's assertion that FF is "broke in AH in general".
<S>
-
Oboe this is a weird one bro . On my new rig tildeath built for me . Any seperate rudders I used spiked , only the ones on my twisty stick didn't . I dampened scaled and did everything I could to minimise what I couldn't fix . With the G940 I dont have spikes at all . I only found one thing that stopped my rudder spikes . When i used a program from logitech from their SDK . I had the spikes on my saitek peds my ch and some ch prop eds that were borrowed . The utilty stopped spiking on the 2 that I could try . I will find the link or put it on the muppet ftp server if you like . It is called poswdm.exe . Stop the polling see if spikes go away .
Link (http://www.wingmanteam.com/latest_software/gadgets.htm)
ack-ack
-
Sorry, I wasn't meaning to confuse the issue with the G940 porked firmware - I was posting in response to hilbly's assertion that FF is "broke in AH in general".
<S>
Sigh does anyone read what was linked . I will cut and paste .
from skuzzy august 8 2007 "The 'buffet' feature in the force feedback is not working at the moment."
from sudz sept 24th 2008 "We are aware of this and one other FF bug. Unfortunately, an in-house hardware hiccup caused a delay in addressing either issue. We were, however, able to confirm both as bugs and are on the list to be fixed."
Both seem to support my "assertion" that ffb is broke in ah2 and "confirm" that the "issue" effects everyone that uses ffb in AH2 . Easy to reproduce it so anyone can be aware of it turn off stall give it a whirl . See what effects you feel . I guess it didn't work for you FLS . I also guess you didn't try my test for ffb in ah2 . Well we both got something from the other we could not use .Once again the difference is I said thank you anyway . I really wish that people would actually test it out before they tried to say that the problem is my personal ax to grind or that I am asserting something not true .That I have not made myself aware of all things it might possibly be . I personally tried the test on 3 different sticks using 2 seperate PC's . I had the problem in all 6 different configurations .I did this before i posted word one . I am not the one making assumptions in this thread . Anything I assert to be a problem in AH2 no matter what it is . I will give a simple test that will reproduce the problem for any/every user . Which leads me back to my question for FLS . Why does this FFB problem bother you ? You don't notice/care about the single most important aspect of ffb . Does not "broke is broke" apply ? I can sense your frustration . Logitech has not been very fast about addressing customer issues have they ? Look on the bright side . Look at the date of the post from htc acknowledging there is a problem . Then look at todays date . Thanks for the link ack ack .
-
Sorry again -
Hlbly, I didn't mean to imply that you're somehow wrong in your assertion that FF is broke in AH in general. I was simply trying to pass on (admittedly old) information from a developer of a similar product that FF is/was far more difficult to code than would seem reasonable because each stick type would behave very differently to the same API calls, and that there is/was at least 2 "incompatible" API's in use.
Having now offended everybody equally, I'll bow out... ;)
<S>
-
My apoligies ghastly . I guess I have become a little sensitive about this . FLS is not even close to the first person who has said it is my problem . That I am on some crusade to harm htc's reputation . That I am someone looking to glorify AirWarrior . I'm not any of them true . I remember it as a community I loved that played a deeply flawed game . A series of band aid on missing limbs and sucking chest wounds . Where everything was "on your end" . When it comes to the point of the matter they won't respond . This is the point it goes to insult , ridicule or implication . Take a look at the thread for example . My"personal ax to grind" is my statement that AH2 has FFB that is not working correctly . The first response to my statement that it is possible that the stick is just doing what the game is telling it to do . I did not say that IS whats happening . Then a reply by fls that it is an "issue" that I have with ah2 and this wasn't the place for it . My post was on topic . I did not expand on the topic by detailing anything about the error . My links were to support my claim that AH2 has a ffb bug . Now before he even reads <assumption> my links . It becomes my "issue" . Does he defend his position that it is my issue and not a game wide thing . No he just ignores it ,and my test so he could duplicate the problem for himself . My experience has shown they will simply ignore the points I make . If any reply is made it will be ridicule insult or simple statement that I was wrong . No reference to posts from HTC's acknowledging its a bug , or reply about the test i suggest . So I am sorry , I am defensive . I am that way because of discussions like this before . That is no excuse though for me , looking for the same treatment from you I get from others .Mia Culpa . BTW was the 2 api's you are talking about direct input and IFORCE2 ?
-
Ghastly I'm just trying to keep this thread focused on the firmware issue since it seems that everybody in AH that updated the firmware is unhappy with it. The exception of course being hlbly.
Hlbly I don't see how your "fix" could help anybody with the firmware issue since the firmware updater won't run when you already have the current firmware.
-
I really don't notice any negative specific to the incremental feel of the FFB...it is what it was so to speak. My issues are basic and center around the stick constantly dropping USB and having constant calibration issues and other "hiccups". There are numerous reports of this on the Logitech bbs forum. As for all the complaints the simple reality is that the profiler should allow you to enhance "feel" but the stick should work reasonably in a full featured way at the default setting.
-
Sorry again -
Hlbly, I didn't mean to imply that you're somehow wrong in your assertion that FF is broke in AH in general. I was simply trying to pass on (admittedly old) information from a developer of a similar product that FF is/was far more difficult to code than would seem reasonable because each stick type would behave very differently to the same API calls, and that there is/was at least 2 "incompatible" API's in use.
Having now offended everybody equally, I'll bow out... ;)
<S>
Back at the time you described, the reason why the programmer was having troubles with coding the force feedback was due to the 2 different APIs that were being used at the time. Logitech was using the standard I-Force API while Microsoft was using their proprietary Force Factory API (which MS was at the time trying to force as the new API standard) and any software using both had to be coded to use both APIs added on top of that was that the I-Force API supported different effects than the Force Factory API and vice versa and also the effects themselves felt differently between APIs. I do not eny that programmer that had to code for both, it must have been a nightmare.
ack-ack
-
That sounds almost exactly right Ack Ack.
<S>!
-
My first force feedback stick was the CH FX . Best one ever it could use either API . IFORCE2 worked best imho .
FLS I see your point I ran the firmware updater and it would not run . I remind you , you are the one that brought up the "issue" I was having . The "ax to grind" is your statement . I notice also you ignore any reply that disputed that . Merely you just continue to try to belittle me . Did you try the parts of my fix you can do ? Did you adjust axis sensitivity and uncheck centering force ?
-
Hlbly I tried everything posted at the Logitech forums. The centering force is on even when it's not checked and the slider is on 0. There is no combination of settings that matches my pre-patch feel of the stick.
-
I will screenshot every setting I have and post them for you tonight . See if maybe we can get it working .
-
I would like to see them myself. Over all I like the temp fix Logitech applied with the exception of the force required to move the stick during flight. I noticed on the ground and when I go into a stall it goes limp as it should. When the airflow over the surfaces increases I found a lot less play near center as with the old firmware. What I am finding thought is that it does take more force once the airflow over the wings builds it does not increase proportionally with the increase of airflow. If I go into a hard turn it is a steady force the whole time. In a dive the pressure does not change at the airflow builds over the surfaces. It takes the same effort at 250mph as it does at 450mph. This is what I am hoping is fixed in the next software version.
-
I think we have pretty much the same response with our sticks a 3 month old baby is stopping me from learning how to do screen shots in windows . Teething 9 months or so early is rough . I also wanted to share my last pm from pyro . "Ok, I got a FFB hooked up and now I understand what you mean. I'll put it on the list and try to get it done for the next version. Is there anything else in the FFB system that bugs you?" I also made the suggestion that , trim should be done away with entirely . FFB in games is linked to sound . What sound does trim make ? I suggested that a force called airspeed replace trim . Link it to wind sound . Make the force be rtc effect . I can't for the life of me figure how trim should effect return to center ,unless it is return to off center .
-
Just use ALT Print Screen for a screenshot of the active window.