All Activity

Well to be honest, we have no idea how far are they in development, and what state of the module is even planned for EA.

I initially thought it was like the P-51 ASI that has a non-linear gauge face, but looking at it, and the gauge script, it IS linear: -- Tachometer TachometerGauge = CreateGauge() TachometerGauge.arg_number = 37 TachometerGauge.input = {0.0, 5000.0} TachometerGauge.output = {0.0, 0.5} TachometerGauge.controller = controllers.TachometerGauge This is how the gauge model reacts to the input number. On the Spitfire gauge above, there is only a start and stop, meaning the whole travel is linear. It SHOULD be 0-65535 is the full travel of the gauge. One thing I did see, though - Remove this, and all the other serial lines: Serial.begin(115200); // Starter seriel monitor It can disrupt the USB communications with DCS. If you want to output data while running a game for testing, use an I2C-connected character LCD or other display that doesn't use the USB connection.

I found this https://www.mil-airfields.de/approach-charts/de-germany/aerodromes.html which contains quite a bit of info not already posted. I've had a go with photoshop to clean up some of the previous scans into kneeboard format. If someone can remind me how to upload to the user files I'll zip them up and post in the original format

Greetings to the thieves.

Have you tried any of the Thrustmaster supplied scripts?

Don't Listen to haters! Keep up the excellent work, mate!

Awesome! Yeah that makes sense; with no M151 loaded before, there's indeed no profile for it, and the "P" error code says exactly that. But I also forgot that this was going to be a necessary step.

I was not implying that the BSOD was DCS related .. just that it was something i was able to correct on my own .

The only people that were surprised this was happening are those who never got into FSX. That blows my mind that nobody here really got into it, but at the same time I kinda get it; FSX was pretty bad in a lot of ways, and a lot of FSX devs wanted to come to DCS when ED opened up their 3rd party SDK program and not many stayed. They figured out that they couldnt get away with some of the stuff they did in FSX that they couldnt in with DCS when it came down to actually engineering their work. I applaud Razbam for sticking around for as long as they have, but we're only surprised that it took this long.

First of all, many thanks to Magnitude 3 LLC for this great module! Aileron control rod moves as you move the joystick.

Mission 10: First of all, this isn't how it's done. I had to pause the flight and use the Mi-24 instructions for the first time. It was hilarious. Now, seriously. Maybe I missed something, but the Orel 1 was left hovering (frozen) next to the cargo hold. I completed all the mission instructions, landed at the designated location, got an F10 message, a report, and the mission was completed. When I returned to the campaign menu, I saw I had the same mission to complete. I could skip, but I don't think that's the point. I wonder if I might have missed something? I took two soldiers and 800kg of cargo. Does this have any bearing on the fact that the mission was not 100% completed?

My experience after testing the new Pimax Play 1.41.1 QuadViews is now integrated, including settings options as in Companion. To avoid conflicts, I first uninstalled mbucchia QuadViews. Result: terrible ground stutter, which I didn't have before. I looked for a solution and made a few more attempts, but nothing worked. So I turned off QuadViews in Pimax Play and reinstalled mbucchia QV. Result: crashes. Like Calvin said, the new Pimax OpenXR is not compatible with mbucchia's QV. So rollback. Not so easy, since Pimax doesn't have a repository with old versions, not even decent patch notes. With luck, you can get a link from a Pimax employee. But what's the point of having a trash can? The last version was still in there. Then I put mbucchia QV back on and it ran like butter again. Conclusion: Half a day wasted. Stay away from the update for now.

Eigentlich sind A10 II und Hornet meine Lieblinge. Trotzdem C-130 bestellt ! Warum ? Futter für die grauen Zellen.

That looks like a Reshade effect on the HUD.

Cool idea, how does it work? As a DX button? If so, as I understand it, one press sends 3 signals to the system?

Yes, I find it a bit frustrating too... But one is a third-party provider, the other is ED. One does it this way, the other does it that way. We have to stick to ED's standard motto: be patient...

Fair enough.

Can you (since we already have the helmet) also add a sun visor (on/off) for the player's seat in the C-130J? Of course, this may depend on the type of helmet, but simply putting on or taking off the sunvisor (with a darker screen effect) is also a good option. Some modules have this, such as the F-15E and MiG-29A FF, and other DCS modules will soon have this option. The model: Example of animation from MiG-29: Btw. Of course, it must be VR-compatible, as with other modules. Some also have animation (hand movement). The logic here might be quite simple: - NVG present on helmet - no sun visor (but glasses are possible on/off) - NVG removed from helmet - sun visor present on/off

That video answers it I've seen it and it looks like big old boom, no new effects. They said "brakes arm, all 4"? Maybe that was it?

So see this: They wear them, they wear them. This is evident in most videos related to night flying (due to the NVGs), but not only that, they are also used during the day because of the sun visor as well. For example, Hercules pilots wore helmets in both Afghanistan and Iraq. Of course, I'm not saying that 100% or most flights can be conducted without a helmet, especially in fully controlled and relatively safe conditions, but it's always a protection in the event of a hit and a forced landing. Therefore, it's not a mistake that the ASC designed the crew to wear helmets, although, as I wrote, it would have been nice to have the option of having the crew in the cockpit without them.

Hey, it If it works it works. The 50% jump shouldn't happen in the first place, though, so something's fishy. MFG crosswinds here, set to full linear without curves, deadzones or anything. They modulate smoothly from 0% as they should so I'm puzzled why your Saiteks are acting up.

Just tried M01 of the Apache Outpost campaign and it wasn't a pleasant experience. First off, the voice overs, especially of the pilot, are bad. The pilot's is in fact terrible. But that didn't bother me as much as the glaring mistake in the briefing about the loadout. While the briefing states that you have 2 Laser and 2 Radar Hellfires, in the mission you get 4 Radar Hellfires something that I discovered only after I had engaged the target and being frustrated at George for refusing to change the missile type. In the end, it annoyed me enough to quit. Sure, overall, it doesn't matter much, and I should have checked the loadout beforehand, but one of the reasons I pay for third party campaigns is exactly to avoid immersion breaking issues such as this one.

I think I am looking at the bottom of your plane from this perspective. So, I would say you notched. The first missile is guiding onto you with its onboard radar.

This happens to me as well, and I do not use VAICOM. I noticed this bug as I'm editing a training mission for the Mirage 2000, where you need to have the kneeboard open to reference the starting position when preparing the INS alignment ... everytime the user presses Spacebar to advance on the training, the open Kneeboard will page forward one page ... really annoying