C-101 BUGS WE ARE TRACKING

Thank you very much!

 

 

Be sure you don't keep the speed brake switch depressed. Release the switch after using it. The airplane keeps trimming while the speed brake switch is depressed.

 

 

Don't know if this is the reason why that happened to you but, the engine can catch fire if you keep an ITT higher than 831ºC for more than 5 minutes in the C-101EB. Or, there's a failure programmed in the mission, of course.

 

ah Okay, speedbrake makes sense.. happens often in my pit :D i am going to test that and replay here. nice to see there is an easy resault for that :)

 

 

I watched the track and your engine did catch fire but it was mid flight. Not on the taxiway.

 

yes thats true. sadly i played in Singleplayer when it happens. but even when i land it happens in on case (single player as well -.-) and there i had my engines in idle..

 

but thank both of you guys for your commitment! its amazing to see how quick u guys try to help poor little pilots like me :D

You were right about your suspicions. The plane flies again exactly as I imagined! :)

 

Be sure you don't keep the speed brake switch depressed. Release the switch after using it. The airplane keeps trimming while the speed brake switch is depressed.

 

is that so wanted that the Trim responds with the speedbrake or is there still adapting?

You were right about your suspicions. The plane flies again exactly as I imagined! :)

 

 

 

is that so wanted that the Trim responds with the speedbrake or is there still adapting?

 

It's the real behaviour of the aircraft. This is to avoid the pitch moment of the speed brake. The real aircraft has a spring loaded switch in the throttle. Try to use a spring-loaded type of switch. Otherwise, be careful to not keep the switch depressed.

all right understood :)

Is it me or uncaging the standby ADI on the C-101CC is really buggy when using the mouse on the caging knob? I don't remember seeing that before.

For me, with the plane already started up at the start of the mission, the backup ADI knob gets stuck after rotating it a little. From a cold start I can’t uncage it.

 

In addition to that the lights for the ignition, beacon markers and MPR also get stuck after rotating them a little.

Same, I can't uncage the standby ADI either. It's been like that for a couple of months at least.

Thank you for your report. I see a discrepancy in some of the files we committed to ED and the ones actually used in the 2.5.5 install. Checking this with ED. Nevertheless, knobs inputs binding is WIP, so having the possibility to bind all knobs to keyboard and HOTAS will still take some time (some knobs are done and some are pending yet).

True, but at the moment the issue has to do with any sort of interaction (mouse clicking, scrolling mousewheel, etc.), not just input bindings. Thank you for looking into it. We appreciate it.

True, but at the moment the issue has to do with any sort of interaction (mouse clicking, scrolling mousewheel, etc.), not just input bindings. Thank you for looking into it. We appreciate it.

As I said: I see a discrepancy in some of the files we committed to ED and the ones actually used in the 2.5.5 install. Checking this with ED.

In other words, ED has to use the files we provided them instead of old files.

Once this is solved, the issues that you guys described with clickable cockpit will be solved.

Excellent.

Hello -

 

Several people I fly with have purchased the C-101, and so far we're having a lot of fun with it. However we've come across an interesting bug that I haven't seen mentioned yet (but I could have missed it in my search).

 

This happens when multi-crewing the aircraft. The rear seat / instructor pilot causes the bug to appear - so far this is in the C-101EB, we have not tested it in the C-101CC yet.

 

If the cockpit lighting knobs are turned to illuminate the cockpit lighting (the 2 knobs on the forward right panel), the landing gear deploys immediately, with the gear handle light constantly blinking. When this happens the gear cannot be retracted, and we're forced to have to land the plane.

Roger, added to our internal bug list. Thanks. Take into account that multicrew is much WIP yet.

Odd repeatable crash on a friend's server, happens if he sets dynamic or static weather: hop in a C-101CC, and

 

2020-01-14 06:47:55.107 INFO    EDCORE: G:\Games\DCS World OpenBeta\bin\Weather.dll
2020-01-14 06:47:55.107 INFO    EDCORE: # C0000005 ACCESS_VIOLATION at A21C13C4 00:00000000
2020-01-14 06:47:55.108 INFO    EDCORE: SymInit: Symbol-SearchPath: '.;G:\Games\DCS World OpenBeta;G:\Games\DCS World OpenBeta\bin;C:\Windows;C:\Windows\system32;SRV*C:\websymbols*http://msdl.microsoft.com/download/symbols;', symOptions: 530'
2020-01-14 06:47:55.108 INFO    EDCORE: OS-Version: 6.1.7601 (Service Pack 1) 0x100-0x1
2020-01-14 06:47:55.510 INFO    EDCORE: 0x00000000000213C4 (Weather): Weather::IAtmosphere::getTurbulenceInLayer + 0x164
2020-01-14 06:47:55.510 INFO    EDCORE: 0x0000000000022C92 (Weather): Weather::StaticAtmosphere::getAtmoWind_w + 0x242
2020-01-14 06:47:55.510 INFO    EDCORE: 0x00000000000954AB (FMBase): EagleFM::AerodyneFM::simulate + 0x98B
2020-01-14 06:47:55.511 INFO    EDCORE: 0x00000000004DB11E (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.511 INFO    EDCORE: 0x000000000036527F (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.511 INFO    EDCORE: 0x00000000003620BF (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.511 INFO    EDCORE: 0x0000000000002D11 (World): (function-name not available) + 0x0
2020-01-14 06:47:55.512 INFO    EDCORE: 0x00000000000031DF (World): (function-name not available) + 0x0
2020-01-14 06:47:55.512 INFO    EDCORE: 0x0000000000574132 (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.512 INFO    EDCORE: 0x0000000000585688 (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.513 INFO    EDCORE: 0x0000000000556994 (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.513 INFO    EDCORE: 0x00000000001C8FBF (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.513 INFO    EDCORE: 0x000000000073B946 (DCS): (function-name not available) + 0x0
2020-01-14 06:47:55.513 INFO    EDCORE: 0x00000000000159CD (kernel32): BaseThreadInitThunk + 0xD
2020-01-14 06:47:55.513 INFO    EDCORE: 0x000000000002A561 (ntdll): RtlUserThreadStart + 0x21
2020-01-14 06:47:55.648 INFO    EDCORE: Minidump created.

 

I've seen threads suggesting weather-related crashes were fixed, but not this one it seems...

 

Crash dump for that was auto-sent to ED, can upload it for you guys too if you want. This is from current Open Beta.

Hi, guys.

 

Just reporting a few lighting bugs in open beta 2.5.6.

 

1. When starting cold and dark, all the external lights are on.

2. The cockpit flood and storm lights illuminate the tarmac / runway below the cockpit.

3. The rear cockpit's storm light seems to partly illuminate the front cockpit.

 

And, not sure if this is a bug but when you turn on instrument lighting, some of the instruments like the airspeed indicator have bluish-white light reflections on them. I've been trying to figure out what the light source would be.

Edited February 18, 2020 by kontiuka

ED made many internal changes in last build some of which are affecting our module. We'll have to work on it to see if it's something that we or they have to modify.

The issue with GPU not connecting or disconnecting with engines on was already fixed by ED, will be included in next release.

the CC-101 EB a Civilian Aircraft has TACAN radio, the CC version a military aircraft, doesn't???

The C-101EB is a military aircraft. There are no TACAN stations in Chile.

Hi, guys.

 

Just reporting a few lighting bugs in open beta 2.5.6.

 

1. When starting cold and dark, all the external lights are on.

2. The cockpit flood and storm lights illuminate the tarmac / runway below the cockpit.

3. The rear cockpit's storm light seems to partly illuminate the front cockpit.

 

And, not sure if this is a bug but when you turn on instrument lighting, some of the instruments like the airspeed indicator have bluish-white light reflections on them. I've been trying to figure out what the light source would be.

Looks like item # 2 has been fixed. Also, landing/taxi light bug is fixed and GPU not disconnecting is fixed. Thanks guys.

Looks like item # 2 has been fixed. Also, landing/taxi light bug is fixed and GPU not disconnecting is fixed. Thanks guys.

You are welcome.

We have updated our Open Beta 2.5.6.43872 changelog:

https://forums.eagle.ru/showpost.php?p=4218508&postcount=88

You are welcome.

We have updated our Open Beta 2.5.6.43872 changelog:

https://forums.eagle.ru/showpost.php?p=4218508&postcount=88

Some nice improvements. So, if the batteries overheat and you isolate them, they will cool down now? I did a flight pre-patch and I couldn't get them to cool down. I eventually got the battery warning because they were disconnected too long.

Today's hotfix includes some updates in our module:

https://forums.eagle.ru/showpost.php?p=4220357&postcount=89

Today's hotfix includes some updates in our module:

https://forums.eagle.ru/showpost.php?p=4220357&postcount=89

 

 

Thanks a lot :) ... you've got to stop updating the module on every update, as you are embarrasing other developers :D

I bought this module on day 1 - it is nice to see that it comes along so nicely. Keep it up! :)

 

Gesendet von meinem ONEPLUS A6013 mit Tapatalk

Some nice improvements. So, if the batteries overheat and you isolate them, they will cool down now? I did a flight pre-patch and I couldn't get them to cool down. I eventually got the battery warning because they were disconnected too long.

Batteries cool down if they are isolated. It is simple to check. Start a mission with an OAT of 45ºC, switch on the starter and the batteries will reheat rapidly. When isolating them they cool down after several minutes. You can check them independently.

I don't quite understand what you mean in the last part of your message, please explain and/or add a trk.