[POS/ADV Alarm on cold and dark state]

19 hours ago, Foka said:

What's the date of the mission?

You talk about the date in game ? I see what you mean, but it's 1/6/2020. So it's not the GPS and year of the mission thing.

I try to reproduce on a completely clean mission, just the Hornet on the map on ramp start and nothing else

[POS/ADV Alarm on cold and dark state]

20 hours ago, Foka said:

After INS alignment you need to turn INS knob to IFA, not NAV, if the mission has active GPS.

No, it's not the problem. No matter the INS position, the bug is still there. I think 'ill make a track. I've tried also to change the POS option, not working too

[POS/ADV Alarm on cold and dark state]

Hi,

When you do a ground start, in my case with GPU, after a certain moment, you have POS/ADV error message appearing and disappearing causing the Master Caution to switch ON and OFF.

I was unable to correct this, even after INS alignement and settings changed in HSI/POS page.

Is there something to know about that or is it a bug (very annoying by the way)

 

Thank you very much.

[Starter button = immediate 20% RPM; even without priming]

Thanks, hope the team can do something

[Starter button = immediate 20% RPM; even without priming]

Hi, there's quite a bug there.

 

When you push and hold the starter button with all mags OFF (I mean in both cockpits), the engine starts and there is the engine running sound playing, which is completely wrong. The engine even stabilize at 20% with only the starter, which is not correct. The starter only gives initial rotation impulse to start the engine. If mags are off, no ignition is possible, the engine must just be rotating inconsistently following compression strokes of cylinders with very low RPMs.

 

In DCS, hold the start switch and the engine goes to 20% and hold there until the start switch is released.  

 

I don't feel the need to provide a track since it's so easy to reproduce, but I will if asked to.

 

Can we have a fix ?

 

Thank you very much, have a good day.

[Couple of bugs after update (july 2024)]

When starting up, we have between many users navigation systems default

 

POS/ADC constantly flickering, same in the HSI/Data/AC page : NOSEC and GPS flickering too

[Hydraulic pressure too high]

Ok, thanks for your answer !

 

Have a good day

 

[Hydraulic pressure too high]

Hi,

Just noticed that one of my hydraulic circuit runs far too high in pressure. I don't have the CHECK HYD GAUGES warning light but I think that's expected since it's not a pressure drop.

 

I don't see anything in the manual about overpressure. Is it a bug, a random failure, and if it is, what are we supposed to do ? (except check carefuly before take off, I think I checked after right engine start, but not after the left engine start)

 

Thanks

[Altimeter doesn't work in some starting conditions]

@gulredrelyes, but in cold and dark or in flight starting conditions, it doesn't happen

[Altimeter doesn't work in some starting conditions]

@gulredrel as I said in my original post, altimeter works fine in cold and dark or in flight start. I just tried again and I confirm the bug on my side. It doesn't work with parking hot start and runway start. I've saved a track.

MB339 Altimeter bug.trk

[Altimeter doesn't work in some starting conditions]

On 5/1/2024 at 1:29 PM, MAXsenna said:

Can you provide a track for the devs? What Airport is this, or rather. What's the elevation?

Sent from my SM-A536B using Tapatalk
 

I'll try.

The airport was Andersen Airbase on Mariannas. Can you try on your side ?

On 5/1/2024 at 4:39 PM, gulredrel said:

Track would be helpful. Also there is a random instrument setting feature in the MB-339. Assumed during the last flight, the ambient pressure was totally different, the setting will be like this during spawn. You need to set it to the correct current value.

Also I've posted this long time ago, I don't think this has been changed, so be aware when having a different sea level pressure than standard atmosphere (29.92" Hg / 1013 mbar):

 

It does not seems to be a random failure at all since it happen every time at the start if it's a runway or ramp hot start.

[Altimeter doesn't work in some starting conditions]

Hi,

The baro altimeter doesn't work when you are starting on parking hot or runway. When you want to set a pressure, the pressure value does change, but the altitude needle and indicator doesn't move. When you take off, the altitude doesn't change.

It does work when you start in flight or in cold and dark state.

Thanks

[I do not hear the radio when making a request to the tower nor do I read the text]

Ground crew is ok for me. But ATC and AWACS are not responding at all

[I do not hear the radio when making a request to the tower nor do I read the text]

Hi guys, I would like to up this thread, I have a similar problem, but with the AWACS on a multiplayer server (French BFR server). On this server, the maps rotates between Caucasus, Mariannas and Syria. Everything works fine on Caucasus and Mariannas, but on Syria I have no comms at all with both AWACS and ATC. This seems to happen only with FC3 aircrafts. Full fidelity modules seems to work correctly. 

I can hear when another player asks ATC or AWACS something, but when I ask a Bogey Dope for exemple, there are no dialog neither from the demanding aircraft or the AWACS. I have the ''AWACS request bogey dope'' binding on a custom key, but I have also tried to go through the usual communication menu. Same results, nothing at all. And the AWACS dont communicate by itself anymore when an enemy group pops for exemple.

I have tested on my own missions and it works fine. I have discussed with the server staff and they said they have the basic IA AWACS running, no scripts, mods or special editor things running except SRS, but since comms works on the other maps, I suppose SRS have nothing to do with that.

Is this related to the ongoing bug or another problem ?

If mods think its necessary, I can move this post into a specific Syria or FC3 bug/problems thread. 

 

Thanks.

[Lasercode on GBU not adjustable in mission]

Can a dev say something about this please ?

[Mirage F1EE Alignment]

Be a bit more precise. What happened ?

I had an INS alignement which was stuck at 968 for me in Syria, despite the continous green ready light.

Did you have the same problem ?

 

[Asymmetrical braking]

I flown the F1 today and I found that turning completely off the steering system will help you keep centerline on braking. It doesn't overcome the problem since with the EE, as grim_reaper68 tested, the aircraft will go on the left on braking, but having only the rudder available reduces the induced oscillations when braking, making it easier. I should try with the SPAD and steering both turned off.

Hope it will help by the time devs take a look at this.

[Asymmetrical braking]

I have a single axis for both brakes, so both left and right are supposed to brake exactly the same in theorie. Yet, even with gentle braking, the aircraft wont hold centerline.

[Lasercode on GBU not adjustable in mission]

I Up this too, via kneeboard like most other modules able to carry LGBs

[The Cyrano, the armament and it's relation to the F1M]

So we should have the A/G features on CE, EE and BE too ?

[Asymmetrical braking]

Same here. I did a little training with just runway runs to try to get better, it's really hard to brake correctly and you get really fast in what we can call ''pilot induced oscillations''.

Is there any word from the devs about that ?

[datalink et target point useless]

Hi, in a French mutliplayer community, many of us also pointed up that right now the DL is completely offset and useless. I walked through the detailed start up and aliglement process without success. Even a short 5 mins straight line flight results in the DL points to be offset by several kilometers.

In the ME, INS is in realistic, and alignement on normal + gyrocompassing.

I doubt a DL which points 10kms away from the designated point should be considered as ''correct as is''.

Is there something to be known or is it a bug that require a fix ?

Thanks

[Question about the test of hydraulics pump during start up]

On 2/9/2022 at 1:13 AM, RustBelt said:

If you're on Ground power, you're mostly doing things that you would rather have the systems stay isolated for. Like running one engine, while changing the hydraulic fluid on the other side etc...Since you're supposed to pull Ground power once your Right engine stabilizes (because Ground power is right up next to the left intake and so you wouldn't want to unplug it after starting L), it's no big deal in normal operations since you check the Hydraulic Transfer pump between starting R and Starting L.

Ok, thanks for the answer

[Any way to enable or add night vision to su27?]

On 1/25/2021 at 6:19 PM, Ironhand said:

AFAIK, you can’t. I seem to recall a mod for the Su-25, -25T, and A-10A. But it wouldn’t work on the FC3 fighters because the background coding didn’t exist for them.

Do you know if this mod is still available and working? Didn't found it

Thanks

[Question about the test of hydraulics pump during start up]

Hi guys, I up this because, few years later, I still had the same question as lucky-hendrix and I found the answer, but it also bring another question about the hydraulic transfer system :

If you turn off electrical ground power before cranking left engine, the HYD transfer pump will pressurise the COMB hyd. system from the FLT system.

But if you don't turn off electrical gorund power, the HYD Transf. Pump wont work. It means this HYD transf. pump is not working under GPU ? 

Thanks

 

EDIT : It's in the NATOPS : When ground power is on, no working hydraulic transfer pump, except if the ground crew make it running. I still wonder why this choice.