Tekkx

This is an outcome of my second try without any assistance. How many Tail-Wheels do you count? (It's not a Photoshop-Trick!)

I wrote bullshit there! The mirrors were absent cause the canopy was open. :music_whistling: While testing GPU-Tweeks I started always a mission "Hot on RWY", just one time a used another one ColdAndDark. But I detected this way, while toggle mirrors in Spitfire makes a difference from 60 w/o Mirror to 15 FPS with Mirror, it looks like mirror ON or OFF affects FPS in the A-10 (close to) none. This tells me, there is still some development to do inside Spit's code. Remarkable is, A-10 has three big Mirrors, Spitty has just one very small one (???) How to reach 60 FPS in the Spitfire? First I added one of my old GTX580s outside the SLI to feed the third display. Maybe this an over shoot, but it makes no difference if this collects dust on storage or inside the rig. Second I spend a lot of time with "nvidia profile inspector" and "nvidia inspector" in tweeking Overclocking and SLI-profiles. Now my GTX970s run at 1400 MHz if DCS is running. They are used by close to 100% (Power Level up to 110%) with mirror OFF (just 30% with mirror ON) This gives further questions to ask to the devolopment. GTX580 runs just idle under each condition. I attached a screenshot of nvidia Monitor where GPU's behavior is good to beseen. I toggled mirror a few times. You'll see. The other one is from inside the A-10 with mirrors ON. Best results brings the "War Thunder"-Profile where I added dcs.exe as application. All my attempts to further tune this profile broke the SLI and just one of the GTX970s spooled up after starting DCS. (I have no idea from that what I did there, every manual regarding this - no matter if a Forum or NVIDIA.com - looks very chinese to me) :)

I havn't check out if there is a difference, but it seemed consequential to me. While Rudder, Ails and Elevator are moving from Zero to both sides, brakes have just one direction. And: If you set a curve, "no slider" gives a strange behavior to a "One-Direction-Axe". Meanwhile I checked out the triple-set of axes to the brakes: Using a good reachable (by thumb) rotary for the brakes - in combination with toes - makes taxi quiet "easy". I know, it's a kind of cheat. But the only way (for me) to reach the runway in one piece :) Now, on the RWY, the next problem occured: Take Off. Well-behaved - as I am - I pull the Elevators full back and ... (very busy with keeping the Spitty straight on the line) ... release them too late. This causes a lift off prior to enough speed. Outcome is clear to everyone: The plane is completely uncontrollable. Best result is a belly with a surviving pilot. So I ask myself: How did those brave men train this. There is no place for a trainer. How much planes have they wrecked before they became a serious fighter pilot...

It took me a moment to dig this out: Use (in Control Settings) (out of my brain - I'm not in the Cockpit - pretending to work - so sth is maybe some incorrect) - Axis Commands - highlight Wheelbrakes (column of the referring controller) - Click ADD - move desired controller's axis from one edge to the other :joystick: Bling! New axis is added there where the other axe already has been :) (separated by semicolon) - Tune axis as you need - you have to tune both axes separate. I set one axis to my thoughts and copied values to the other. I think, I'll never find a suitable curve. I set it as Slider with a some flattened behavior for soft response. Not too flat and even (maybe) no deadzone. And I stuck the pedal on the floor with double-sided adhesive tape (If I have to move someday, I have to take the deal boards with me) The renter: Hey! What about my deal boards? I: Keep calm, man. I flew a Spitfire right here. You're lucky, that anything else is still OK with this house. Right now (I am at work again) I had a flash: I'll add the "trick" with the Rotary to the brakes, so I can use it as a parking brake AND can test if I can improve my taxi-skills with that. Jeeeeh Ha!

That's a valuable idea. Only problem: Rotary aren't self resetting. Will definitely try that. Before, I have to swap Throttle and RPM axes. Throttle is now on left lever and well used while taxi. So I can't reach any of the rotarys.

I put the brakes to the Toes of my pedal (both axes). This works sufferable as the curves are tuned wise. I'm still on it... It took me several crashes until I realised, that brakes work differential in relation to the rudder. The manual keeps this secret. Though I know this it's still heavy to taxi without leaving the taxi way. It's not easy to give the brakes the right rate without the sensation of acceleration or deceleration (ass-meter). Yesterday I found out, best taxi behavior is with a flat rear tyre :) I performed a near-headstand (cause of heavy braking) and as the plane's rear fall back to the concrete, jumped a few times, the tyre was flat and the tail-wheels' support bearing was fixed. The ground chief ranted ... but now it was very easy to taxi straight ahead :)

Mapping brakes to a button? What a strange idea. On my bicycle I use a stick for braking: if I drive too fast I just put it into the spokes. That simple.

Is here some place for a dream? What about Export to a separate monitor? I ("some" others maybe also) have plenty of them here for the A-10C.

YOU started with that :) I stayed AND did something different. He. How about this? Encouraged I tried to make a record of my second flight in a Spitfire. The boring part ended with a non-recovering black out.... In Replay my mashine stuck in the meadow, thow I reached this time (in original) the RWY straight using the Taxiway. :smartass: Looks to me like the Recorder writes just the throttle and controls, not the trail.

I can't imagine they fought against Kraut and found their way back to the homebase. I am complete unable to just read simple heading from that thing (even from a still close up). Glamour Boys. :thumbup:

My problem at taxi, take off and landing is the quiet sensitive bird to the controls. Touching the wingtips to the ground is the merest problem I encounter :) I have a long way to go to find the right curvature of controls (rudder, brakes and aileron) and will need a lot (means really: a lot) of training for not oversteering to keep the AC "on track". Trying to compensate the torque impact of engine and screw are most challenging. Also handicap makes lack of direct feedback of controls. Pilot induced oscillations are my worst problem at the moment.

Funny :) The other question is: Is this a ED-issue or do we let the problems in with installing special Mods? BTW: I watched Ironhands (really boring :)) track on my rig: It ran beautyful. So the issues happen while recording. That's what I've learned from that.

Althow this is an Arduino matter (look here) here is a short answer: 20 mA per Output Pin 400 mA total (!!!) That means, you'll get with two LEDs per Pin close (to close) to the edge. I wouldn't recommend. Look for a solution with a Transistor inside of a special electronics forum. I made good experiences with MOSFETs (others too). Also I think you'll need for the cabin light some more power than a single 20mA-LED :)

Thank you, Art-J :) "Water" is a very helpful hint. Looks like, posting a shot of my settings has been my best idea today ;) 1024 inside the cockpit is really (really) important for meter-reading some instruments. But A-10C makes no problems. It's just the Spitfire. Problems occure first time as I installed that (long awaited) Airplane. Edit 30 minutes later: Found out wherefore the A10 makes no problems: There are no mirrors. I think I have deactivated them sometimes for some reason (while setting up MonitorExports somehow - maybe). I have inside that bird such a workload so I never realised the absence of mirrors. Setting Water down made about 5 to 10 FPS+. Will see - if I fly over the sea - if it's worth of that :)

Now I overclocked my GPUs to about 1300 MHz, reduced Gras/Clutter considerable and set Textures and Shadows to medium. On the ground with engine off my rig manages now 30 FPS (+/-) with mirror off. With mirror on my FPS melts down to about 15. It's impressive, how much power this small mirror consumes. I think I can fly now. Without mirror and a landscape looking like "good old" 90s (Strike Commander) - using two GPUs, I thought I'd be safe for 2 years at least :( Maybe here is some one with a useful hint, where I can do further tweeking without loosing too much immersion?

https://forums.eagle.ru/attachment.php?attachmentid=144782&d=1469212750 Forget this thing!!! I did a test last week (the case was low priority): NO function. So I reworked the complete clip, using some IR-LEDs SFH 4209. They have a half angle of 25 degs. Means: No grinding :) Three LEDs in series with a 16 Ohms Resistor at 5V. Works very well :) White shine of LEDs is just the reflection of my "flash"light :)

From what I understand of this matter (the language's barrier is also there) "Track Replay" is ATM an useless (because not working as intended) tool. I can imagine, fixing that is an in depth intervention into the system and recording is a complicated process. So I don't want (nor plan) to complain that. If I got a wish for free: I'd appreciate a button (or sth else) where I could stop recording (as recorded data are useless anyway). Maybe this would solve also my Low-FPS-Problem. (Low means < 10)

This is much better than what is to expect of a (notable) commercial software developer/seller :thumbup: More interesting: That looks like no one has connected two pots before... OffTopic: I'm still on the 3.5" mysterium. Approaching (keep your fingers crossed) a solution.

I am 100% with you. Not just at high speeds, also notably in ACs with baulky attitude (like the Spit). Spitfire is NOT to handle under this circumstances. Low FPS are also a good excuse for lousy skills :) (as I did right now) ;) Otherwise ATM I'd be glad to reach 30 FPS. I think (on actual ascertainments) in my case it's not just a question of drivers. There went something wrong with my whole system. But I'm still on it. Edit (one day later): All tweeking with drivers got me nowhere. Now I try a new clean install of DCS. Checked 2.0.x: Just Nevada Map :( Right now runs install of DCS 1.5.5. Now comes the worst thing: Recover all configs (keymapping, Stick curves, DCS-BIOS, Helios... and modules like A10C, FC3 and Spit) without recovering my old problem... Huh.

It seems my Replays start running out of convergence if I drive the bird into the meadow (as I always do ;)). There I need much more RPM as on the concrete to bring it back to the lane. In replay I watch me (smooth) throtteling up, but the bird don't move until I reached (in real) the RWY and give full throttle (for take off in real at the RWY). In replay the bird stucks still in the grass till it starts rushing into the next obstacle. Maybe there is a context with my low 10 FPS inside the cockpit (F1 view) while my rig reaches close to 100 FPS in F2 ... F4 views. If someone's interested in: I append such a missfortune here :) 3 attempt Spit crash.trk

Hallo, javelina1. First I had version 373.06 -> bad Than I updated (suggested by GeForce Experience - uninstalled meanwhile) to the latest version -> no difference Than (after I read this Thread) I downdated to 355.98 -> also bad. 355.98 I elected randomly from a long list of downloaded drivers (I could go back to 266.58 from 2011 :) ) Now I'll try 368.81 - no, I can't. There is a gap in my list: Previous is 364.72. So I try this. Thank you. Will see. PS: Tried some different drivers. Meanwhile I get about 12 FPS in Cockpit... 100+ outside (F2 ... F4) :huh:

Last post is now one month old. I try to chime in anyway :) Someone wrote, 24 to 25 FPS are good. So far I'm with you. What about 7 to 12 FPS? I've been astonished about my brandnew Sopitfire is "nearly" unflyable - besides the natural problems of this bird. So I took a look at the Frames: 7 to 12 (sometimes 20 if I look in the sky). Outside the plane FPS jumps up to 30 ... 50 FPS. So I raised some money and spent it to a second GTX970. This one runs now with the other one in SLI-compound. Still the same! Interesting is, these low FPSs happen just inside of the Spit. Inside the A-10C (e.g.) everything looks good. Same bad performance if I screw all at "LOW" or even "OFF". I don't think, this is standard.

Poser! :) I flew just the A10C before. Long awaited Spitfire is something complete different. Meanwhile I start the Merlin at first attempt. Take Off and Landing isn't as difficult as taxiing (to me). I started to manage bringing her to the RWY, as I tuned my Toebrake-Axis. I set it to "Slider" with an ease curve (will look what value). In the A10 I didn't care about that. To put the brakes to the Stick (like in the real one) is maybe a good idea. Will check this althow at the Stick are just Triggers. Slightly and modest(!) use of brakes seems to trim the COG so she turns into the wanted direction. All in all successful steering is a mixture of Throttle-, Rudder- and Brakes-Play. Elevator pulled all the time. What a workload... (in the A10 I can have Breakfast in the Cockpit while taxi). I try it without assistance (read about this here in this Thread). I'm still on learning "to put her on". Right now I can't imagine to handle her in combat :joystick: PS: Meanwhile I found this:

I did some testing with my brandnew Spitfire :) After 2 crashed planes (total loss) I managed at my third attempt to (partly) successful taxi to the RWY, take off, fly a circle and land (second approach) with almost no damage (just broken legs due to unwanted touch-and-go). Pilot was still alive! Proud of this amazing progress I saved this track to delight myself in watching me later. ;) And maybe learn sth. of this. Long story short: While watching (replay) it ends everytime in a desaster: Plane crashes somewhere in the weeds. Why I write it here: The AC crashes everytime at another(!) place. Sometimes in the meadow, sometimes it hits a bunker frontal. It reaches never the RWY, nor it takes off. Annoying and disappointing. PS: I use F3-view to let the Plane pass me cause the bird looks and sounds really great while passing!!!

Ruahatu: Ian is right. Ripple Rejection is essential for stable function of most ICs. Also should you try other MAX487s - just for sure. Maxim Integrated write in the datashet, these Chips are very stable and reliable (robust) ... but I've seen tons of them gone by just little mistakes. They die fast and silent. Look at the photo: (a very close look shows burned holes on some chips) I started to collect them as a reminder as I killed about double or tripple of the collected ones (not to be seen: several complete PCBs with burned Chips on them) :music_whistling: