Nu-NRG

And it happens just past the runway threshold. That I was able to determine in the times that I experienced it. Which is as you say, completely random. Me and some of our members spent some time analyzing tacview recordings as we landed in 4 ship trail. All of us experienced it as sudden jolt up, some to severe (go around) and some really subtle. Tacview recordings showed a steady descent slope (little breaks, flaps, gear, on speed) and just on the threshold, that perfect line of descent goes in to curve. ACFT gains altitude, while still maintaining speed with no AoA change :D:joystick::joystick: Happened on LSV and INS.

Actually he did. In detail, HOF aka Height of Function will tell a SFW or CBU when to open up. Along with RPM you will effectively control dispersion / footprint. And if it was typo on your end and you meant CBU's, then that is done in DSMS INV pages (see manual).

When jammer switch on CMSP is switched on, power is applied to jammer. Jammer still needs to be activated with CMS switch depressed. Unless CMSP is in AUTO mode.

Last I checked you are suppose to drive piper on to target, not push it. So anything below 1g could end up in lets say, lucky situations :D

A: Change waypoint elevation B: Start looking, when way out of target area C: Maneuver ACFT to get TGP HUD symbology over target and GS I'd go for option A any day, but all are viable depending on situation.

As Z changes, I would not rely to much on it. Instead creating waypoint or another markpoint over target area is a wise thing :D Think of it as a good, safe way of doing it. And I'm not negating Bunyap, nearly expanding.

Yes true You assume correctly :D Will do and report back. Thanks!

Perfect!!! Not so well. Just yesterday, our pilots going in to the air (me being one of them - A) encountered a rather nasty thing that in my opinion (but I can stand corrected) should not happen. I believe that image will serve best: A had clear comms with B C had clear comms with B A and C had no comms until C was approaching taxiway golf (out of LOLA on charlie)

People that do have access to info like that, stated above, are banned.

There actually is more to radio frequencies than just power and range. Things like atmospheric conditions Adjacent frequencies Actual frequency (imagine 100mHz vs 2000mHz) Wiring length / installation (losses) And some other considerations :D But as there is not enough material to work on regarding that, I can only imagine how hard / impossible would be to code that in.

Hey Ciribob! Found a bug in 1.1.8.0. Tested with three pilots and diagnosing on the fly. What is working: We were able to confirm PTT is not and issue We were able to confirm that we were broadcasting/receiving on the correct (specified) radios via overlay panel Sound channel output is not working correctly: Radio 1 will not set anything (no effect) Radio 2 will set radio 1 output Radio 3 will set radio 2 and 3 output Example in A-10C: FWD radio on LEFT ear = no effect MID radio on BOTH ears = FWD radio BOTH ears AFT radio RIGHT ear = MID and AFT radio on RIGHT ear Timeline: This bug was not present in 1.1.6.0 (we skipped 1.1.7.0)

Hey Ciribob. I have a question for you there, or one could say a request for feature. I don't know if this was already asked or maybe already in the works, but would it be hard to make it work with some command line parameters. In particular I fancy connecting on start up without clicking connect :D

Once you start logging and graphing the HW utilization by DCS, you waive your head in dismay.

Did some experimenting with the springs. Interesting results! When I inverted the 4 small springs the stick holds "back" position and does not free fall. It does not return from "back" position either. Front, left and right it does return. But did that beforehand as well. :) The question now remains, would I replace the four springs at all..

With material and bending work .. cca. 35 EUR. And that is DIY price. I still have to see how much the springs will cost me. On Monday.

Does it work now? Was just editing the post as originally pics did not show up.

So here is another warthog extender. My idea, my design. Idea behind it was to bring the stick closer to my body with any offset. Design, well it was free flow. It turned out nicer than expected. Materials used: 1x M36x2 ÜWM-L nut 1x M36x2 GV-L cupling connector (male) 1x 1m 20x1.5 inox pipe (Actual used cca 22cm) 1x 15cm 25x2 inox pipe (Actual used 20mm) 1x Round profile with inner Ø25 / outer Ø34, cut out from 10mm steel/inox plate 1x PS/2 extender 1x Expertiese or services to bend, cut, smooth, assemble and weld everything together Pros: Interesting stick throw Any offset at both points Sturdy, no "wobbling" feeling from extender it self Cons: Stick falls back on it's own with no return (to be remedied) To do: PS/2 extender Default coil spring replacement (A. main coil spring or B. smaller four + invert) Pictures: I'll post up dimensions and instructions if anyone is interested. Feel free to ask away if you have questions!

1. Create a mark point with laser trough TGP. 2. Drop GBU38/31 at markpoint as SPI. 3. GTFO. :D

:joystick::pain: This already went south ... Only a matter of time till it gets locked down.

In light of trying to better one self, keep in mind, you have multiple sensors that can act as SPI. TGP is only one of them. And if you get masked / gimball limited much, you are way to close. TGP has some range. Also, my way of how to keep lock on target is simple Mk1 eyeball.

Some stuff: 1. You NEVER ever select a station on DSMS. You ALWAYS employ weapons trough weapon profile. 2. GBU-10/12 should be lased in between 13-15 seconds. Now on to the lasing it's self: You can set AUTOLASE to ON in weapon profile along with desired lase time. The alternative is that you manually lase your self with pinky button - with latch on or latch off. SPI has no effect on lasing, laser will always light up a target that is in the TGP's cross-hair. Also, keep in mind, laser in the TGP will burn out after X minutes (I tested it but I forgot the exact number) off TOTAL time used (does not need to be continuous)

No. This is how it looks:

TARS, TacView and Helios :P Basically modified export.lua :D

Well if it is in the area it should be there. Maybe you just need to look "better". It's an informative call that he/she/it killed armor at ###/###.

Were there any actual warnings on caution panel? Any battle damage is repaired on the ground.