Spacehamster

Thanks.

How to set the weapon system camera to be locked to the calculated impact point? I once managed by accident to set it up. For example, when selecting unguided rockets or the gun, I want the camera to point at the calculated impact point.

I mean it just feels wrong that the KA50 gets thrown around by the wind so much on that server. Do you fly with rudder trim on or off? I fly with OFF, because the real helicopter does not have rudder trim I think.

So it is a matter of the F5 ADF not being able to tune into that frequency band. Is that different on the Nevada map? I do not have it.

I did not use rudder on purpose to see where it will rotate towards. On a regular cold start it will take of straight. It is the wind speed then? There is a windsock on the airfield that indicates a strong wind. However the KA50 should not be that susceptible to it. It has no engine torque that has to be countered with a tailrotor and it is a heavy helicopter.

That means I can not manually dial in an ADF?

I have added a replay track. On the VA server my copter gets blown off towards the left on take-off. And that does not happen on regular single player missions. I would like to know if wind is causing this or somethin broke on start-up. I can only control it with strong rudder input. And a helicopter with considerable weight and stabilizing systems should not be this hard fly straight even in wind. I can much more easily fly the Huey or Gazelle on the same server. Virtual Aerobatics public server v1.5.4u4k-20160921-184122.trk

How to use the ADF on the F5? Set the frequency to 335 and approached Kobuleti, no signal at all. The radio is set to ADF and MANUAL and the Antenna to AUTO. Is that feature not completed yet? Because TACAN works. 1. What if the NDB frequency is higher than 399? Because the UHF dials only have 3 as a setting for hundred. 2. What do the letters after NDB beacons mean? Like, Kobuleti, NEAR NDB 335 (BI)

I was taking off with my F5 and right after take-off, I noticed the plane trying to roll very hard to the left. I looked at my gauges and the left engine was completely shut down. Then after a minute of flying it suddenly kicked in, and the plane stabilized. However the exhaust temperature gauge of my left engine was stuck at 10, way past the marked 7-8. It was completely stuck there, it did not oscillate or move back when I lowered the throttle. The RPM gauges however did work. And they showed different values for both engines. 1. What happened? 2. What caused it?

The sound needs to be crisp and higher pitched up close. I can hear the doppler effect of it moving away from the recording source.

How do you check for the gyros being ready?

That roll is a bug. We just need to keep making noise so the developers will fix it

The new engine sound is terrible. You just took a a flyby recording and cut it so it loops and used that as the engine sound. However no plane engine sounds like that up close. https://www.youtube.com/watch?v=NS-O6_gH-XA Listen to it at 1:50. And then for 15 seconds until it takes off. At 1:57 (when it moves away from the camera) it starts to sound like a deep howl. Because the doppler effect will cause the pitch of the sound to lower as it moves away. The engine sound remains crisp and of higher frequency when the plane is close and stationary.

Getting very weird behaviour from my KA-50, but only on the Virtual Aerobatics server. After take-off it immediately tries to align itself in a certain direction. The server briefing shows a wind speed of 9 meters per second towards 276 degrees. 1. The degree number, does it tell the direction the wind is heading towards or from? 2. Could a 9 meter per second wind cause the KA-50 to refuse to fly straight, even with the appropriate autopilot systems on? For comparison it does exactly what I want it to do on a default cold start mission. 3. Could a preprogrammed flight plan cause the autopilot to rotate the helicopter in a certain direction?

No external loads, cold start. And it can not be a deadzone issue because the controls indicator shows dead center. If it is not a bug, what could cause it? Wind? Turbine torque?

Is it really this loud compared to all other planes in the game? I find it hard to believe that a relatively modern jet like that sounds like a hairdryer from hell, while the mig15 and mig21 are comfortably moderate in noise (all without the helmet option in audio).

So that is nice, but it still looks like December 2018. Actually this press release has even less tangible news than the others. It is a small clip of the landing looped over and over again and most of the 8 minutes in the video is filler. That whole f14 was supposed to be out "second half" 2016. cobra in september 2015

Not sure if this is a bug. Flying straight, no external payload, full afterburner. The plane very slowly rolls over to the right. Is that a bug or something causing it to roll?

Is the L39 really that noisy in real-life? I find myself having to lower the ingame sound volume because its engine is so high pitched and noisy.

It's a bug, not some highly sophisticatesd feature of the flightmodel. The bank input runs away long after the bank input is held in place.

Getting the exact same problem.

Video does not show the control indicator. The Huey, Mi8 and KA50 do not bank creep like this. In forward flight a helicopter is stable, because of the airflow straightening it out. To me it feels like a bug in the code allows the bank input to keep creeping up even if the stick is held in position.

That would not make sense. They were very eager to show off the F14 back in April 2015, when it was only the contour of it. They had nothing to show off at that point and they celebrated the site opening. But on the Viggen and Corsair, it has been a complete vacuum on any screenshots. I think my late 2017 for Viggen and December 2018 for F14 is going to be a great bet. Belsimtek announced the F5 on October 15th 2015. They released July 22nd 2016. Belsimtek have clockwork precision on release dates and they always regularly show screenshots. LN announced stuff in Summer 2015, saying something like "September looking good", then no word until Christmas. LN, if you know you won't be showing anything until 2017, then just say so. Saves us excited customers to check the forums regularly only to be disappointed.

"It's almost there (along with 2 other modules) but we can't show you screenshots yet." Why is there not a single screenshot of it? Or how about you just tell us. Will there be a Viggen release BEFORE October 2017? Also I will bet that there will be at least 8 months of time between their first viggen screenshot and release.

Who are these men?