All Activity

Mine doesn’t. Quite the opposite actually. Maybe, I missed something. Care to elaborate your “various reasons”?

Very quick test for the CH-47. No colors / No special font

Ooh, lovely Splitty

Yeah, also works for me. Looks like user error with your procedure. I would suggest following the procedure described in our manual step by step and if it doesnt work still, you can provide a track file or video or just write down a list of your steps so others can check what you might be missing

You would need to properly put out the fire. I am not aware of a way to trigger this magically. Fire goes out when you repair the aircraft (maybe this can be triggered?) or fly fast enough for some time (practice testing: around 10-15s at 0.8 - 1.0 mach). Depends on a lot of conditions of course. Shutting the engine down will not help a lot because once there is a fire it will burn through the engine and set other parts on fire as well. It does not need the fuel to continue burning. It can help in the early stages of some fires when you only got an OVERHEAT but no FIRE lamp and potentially also only see smoke instead of fire coming out of the engines.

I was listening to something the other day and learnt that on the flight Dimbleby flew and reported on, his Pilot was Gibbo. I’ll have to read Enemy Coast Ahead again for a refresher. He should never have been asked to even begin forming 617 when he was asked to. He’d done more than enough already and was pretty battered. Amazing what some of those fellas went through. Looking through the thread a bit, just reposting this one (with gunners ). Best regards team

Once I was over the target (on time and altitude) and realised that I couldn't do a thing. Called it a rage quit

Not only for the Viper. The Phantom as a weasel, F18 and F14 from the carriers, theoretically the Strike Eagle (damn it!) and of course the Warthogs, Apaches and even some redfor stuff. There is so much potential!

After summer vacation, i returned to my rig only to find that problem is back...but for now i can't fix problem of DCS showing on wrong screen no matter what i try..

Продано, прошу закрыть тему.

BUMP Related to this… I’ve created a mission whereby the user experiences an engine fire on takeoff. I’d like to make it so that, if the user completes the correct actions, the fire is contained . By using a “trigger” I can time the start of the fire perfectly. I can also trigger additional problems if the user “flips the wrong switch”. However, I can’t find a way, through triggers or otherwise, to stop the fire from “spreading”. Right now it just keeps burning, even after shutting down the related engine and it will eventually end up resulting in a catastrophic event. Is there a way to “stop” or “undo” an active failure? Can it be done by scripting and if so, how would one go about that?

Did you skip it completely? Than you miss something big! Without spoiling, the focus of this particular mission is NOT the mission task, but the events surrounding it and their impact on the tory. Maybe you should give it a try.

Tomcat and Strike Eagle

I think you need to elaborate a bit, since neither of the claimed "even the slightest hover makes it collapse and crash" nor "it is impossible for the helicopter's behavior to drop during a base approach" make any sense.

Мэтт, как уже сам говорил в одном из интервью, не является экспертом по МиГ-29. Если посмотреть почти все его видео по холодному старту, они сильно отличаются от РЛЭ в сторону упрощения. Будь то МиГ / Хорнет или Вайпер. Чтобы среднестатистический Джо / Иван / Жак могли бы посмотреть и запустится без лишней головной боли. По 9-12 куча информации находится в публичном доступе и каждый может запускать как хочет. Может @Fighter29 покажет как надо

How about “search”? Man .... https://github.com/jonsky752/DCSTheWay .

No problem, just that you made it work

Even though I have FC3 since years, I just began using the MIG-29. From the first Landing, every other Landing was a success. If you have a feeling how to propper land a F-16, you can land Mig-29. The only difference is the Metric system. But since I am European, this was never a Problem for me to adapt. The MIG even does some good landings with one broken engine (And you cannot say, the F-16 does ).

In fact, this is how a kneeboard could be displayed, the one that is on the knees of many 3D pilots in DCS. But I also think that there should be an option to turn it on and off in 3D, because sometimes the maps don't look very good on the pilots' laps - they are either too big or too small, so it doesn't always look good). In most cases, you can add your own pages there, and the airport diagrams themselves are displayed correctly, which is good. We have also something like this: https://dcskneeboardbuilder.com/ what could be interesting for Hercules DCS pilots.

This little guy is outperforming almost 90% of the ground units in range. It's 76mm is ranging out to 2.68nm. While the Abrams and other 120mm MBTs are only hitting 1.87nm. A DCS comparison would be the Tk M4 Sherman 75mm which goes to 1.60nm

Changelog in the SDK says only: "Bug Fixes & Stability Improvements". So yeah, we shouldn't see much of a difference.

Want to bump this topic. I’m experiencing same. With any gunner or loadmaster positions if I press the binding 4,5 or 6 on keyboard I cannot move from that view again. Eg Pressing 1 will not return to pilot view. Pressing the same key again also does nothing. Have to restart a mission when this happens.

Ah i see, that's another type of latency on top. Called motion-to-photon. Your headset has to collect and process your movements, send it to your PC - process and apply it to the game - render it - compress it - send it back over Wifi or USB - decompress it and render it on your display panels again.

That's why I said "noticable". I was comparing my experience with the Rift S and Quest Pro. With VD there is a lag when moving your head quickly. I don't see this with quest link cable.

Sorry man, but there is no tech magic possible to reduce the latency of the odyssey a rendered frame has to take through the route of streaming over wifi or usb cable. With a direct Displayport connection it will take a rendered frame only 1-3 ms to reach the display panels, while going through all the hoops and loops of processing needed for streaming over USB or Wifi you'll always end up with 40 - 80 ms. It's all the encoding and decoding, hacking everything into little transferable packets vs. just flushing it through a big pipe. Even with "Oculus Link" you'll end up with 20 to 40 times the latency the sim is actually meant to be played. You will "see" it, once you have the chance to compare it directly. I had two years of built up muscle memory with a standalone headset and was a bit shocked about the difference. When i changed my setup, i also did a DCS session with standalone HMD before and after the change to PSVR2 (which was roughly within 20 minutes). You can go into details here: https://pimax.com/de/blogs/highlights/technical-comparison-displayport-direct-connection-vs-quest-3-streaming-solutions-for-pcvr