C-101 Campaign

[MAXsenna]

I definitely tried to use the mouse zoom on the approach plate with no success but if you say it can be done then I will assume I was doing something stupid.
 
"You guys have to improve your IFR flying skills" - Vibora
 
I completed mission one on my first attempt thank you very much   
 
Now as for mission two...  

I can confirm that the new files provided can be zoomed.
Tested on both stable and OB.
Cheers!

Sent from my MAR-LX1A using Tapatalk

[Rudel_chw]

On 2/2/2021 at 11:28 AM, Vibora said:

Campaign zip file updated. You can grab last version from my post above.

Changes: Higher resolution briefing image of the VFR flight map in dead reckoning mission #7.

 

 

Hi Roberto,

 

The Campaign included on today's Open Beta update is the same? or the one on your post is newer?

Cheers,

 

Eduardo

[Vibora]

Unfortunately ED didn't update the files. The one in my post is the latest.

[lwalter]

First, thanks for the C101 campaign.

 

I went through the 1st mission without any issue, although the ILS landing on Batumi was a bit scary: almost no visibility until almost on the runway...but this was fun!

 

On the second mission, I have no clue how to find the insurgent helicopter. I take off and then, impossible to find it. Is it already gone because my startup is too slow? Something I'm missing?

 

[Rudel_chw]

21 minutes ago, lwalter said:

On the second mission, I have no clue how to find the insurgent helicopter. I take off and then, impossible to find it. Is it already gone because my startup is too slow? Something I'm missing?

 

Yes, you need to startup quickly, as the initial position of the helo is very close .. here you can see that while I'm taxing and taking off, I look everywhere to try to find and keep current of the helo position as much as possible:

 

 

Yeah, I know, horrible landing

[lwalter]

34 minutes ago, Rudel_chw said:

 

Yes, you need to startup quickly, as the initial position of the helo is very close .. here you can see that while I'm taxing and taking off, I look everywhere to try to find and keep current of the helo position as much as possible:

 

Yeah, I know, horrible landing

Thanks a lo for your video! 

It definitely helped me taking off much faster (I didn't know you could do it without external power unit...).

However, even if I manage to take off very fast, the helicopter is already gone while I face again Vaziani.

I'll try it again another day, else this will become too frustrating

 

[Rudel_chw]

23 minutes ago, lwalter said:

I'll try it again another day, else this will become too frustrating

 

 

You can also edit the mission a tiny bit (it is not protected), take the enemy helo and move it further away from Vaziani, to give yourself a bit more time .. not too much or the mission will not be challenging

Cheers.

[Bagpipe]

Mission 3, I can't move. 

 

Its a hot start mission and parking brake is off yet when i push throttle to full it only reaches 51% N1 and doesn't go anywhere.

 

What am I missing? Running today's OB patch

 

EDIT: not just on the campaign. Any mission. If its a hot start, like instant action takeoff missions, if my hotas throttle is set to 0% then I start the mission rolling at 97% N1 (which is wrong) so I move it a bit and it registers that it is at the lower end of the axis and drops the engine power. But it never recovers and will not go past 51%...

 

EDIT 2 : Tested a third mission and tried this fuel flow reset button which dropped the idle fuel flow readout a little but still can't fly this aircraft. Think it is broken

 

EDIT 3: Shut down engine and restart fixed the issue but on hot start, because the mission is kicking off with the engine at full pelt when controls are at idle, it seems to be messing something up which prevents the engine spooling past a certain point.

 

@Vibora

Edited May 20, 2021 by Bagpipe

[Vibora]

I don't know. Unable to reproduce. Would need a trk. Can you record one and pass it?

[Rudel_chw]

Maybe its an axis conflict, check that you don't have red conflict marks on your throttle axis assignment, like these:

 

 

[Vibora]

You said you can advance throttle to 51%, so I excluded the red warnings inputs issue. A better explanation on your side could help. It could be that you have another peripheral interfering with your throttle.

[Bagpipe]

Ok so it is something my end. I will run a repair and see if that helps.

I don't have any conflicts as I sorted them previously. If I can't get it working correctly I will send over a track.

 

Thanks for prompt responses

 

EDIT: Attached a trk as repair didn't solve the issue. 

 

At mission start (hot start takeoff) the controls indicator shows my physical throttle being fully forward when it is in fact at fully back. What this causes is for the mission to commence with engine N1 at 97% or more, a caution appears and quickly disappears as the engine rpm drops. I thought the rpm was dropping when i moved my throttle slightly, as this would force DCS to recognize the true position of my physical throttle, but it drops instantaneously regardless of whether i move my throttle or not.

It's very strange, i will keep messing about but if you could have a look and let me know what you think that would be great!

 

C101rpm.trk

Edited May 20, 2021 by Bagpipe

[Bagpipe]

Another one demonstrating the issue followed by an engine restart 

 

I tried removing a couple community mod aircraft too but that hasn't helped either.

 

I may try reinstall the C101 module if nothing else works

 

This also rules out controller issues as it flies perfectly fine after the re-start. There seems to be some hot start engine logic corrupted somehow

 

 

C101rpm2.trk

Edited May 20, 2021 by Bagpipe

[Vibora]

It seems your airplane engine compressor stalls because you move the throttle instantly to full power. How do you manage to do that? Lookt like a potentiometer issue in your peripheral. Also, the throttle and brakes are at 100% at mission start, that is not normal either, at least for brakes.

[Bagpipe]

2 hours ago, Vibora said:

It seems your airplane engine compressor stalls because you move the throttle instantly to full power. How do you manage to do that? Lookt like a potentiometer issue in your peripheral. Also, the throttle and brakes are at 100% at mission start, that is not normal either, at least for brakes.

 

The peripheral is fine. It doesn't do this with any other module only the C101 I am afraid.

The brakes are on because I am pressing them because the aircraft starts the mission at full throttle.

I was hoping you could tell me why the throttle is at 100% because it only happens with this aircraft lol

 

added a track of the F86 takeoff mission with no issue with the throttle.

 

Its this module my friend, but why???

F86rpm.trk

Edited May 21, 2021 by Bagpipe

[Bagpipe]

I have now re-installed the module and still the issue persists. 

I have also tested my HOTAS in the Thrustmaster software and there is no issues there either.

 

[Bagpipe]

Could you have a look at the log attached and see if there are any clues in there?

It does not repeat across any other modules or sims so it's not hardware related.

I have tried setting saturation of axis to 95% but it still does this on mission start.

When I load the mission and open the controls indicator it shows my throttle at idle but the minute I press "Fly" it jumps to full power, stalling the compressor and only returns to idle when I nudge the throttle

dcs.log

[Vibora]

Did you delete or back up your inputs saved games?

[Bagpipe]

8 minutes ago, Vibora said:

Did you delete or back up your inputs saved games?

Just tried that, deleted both EB and CC input folders and restarted DCS.

Ran the mission and still the issue persists. Even on the default keybinds with no red !'s

This is driving me barmy

 

Tried just dropping it in the ME with a hot runway start and same issue so it's not a mission specific bug either 

Edited May 21, 2021 by Bagpipe

[Bagpipe]

OK got a fix for now...

 

If I switch off "synchronize controls with hotas controls at mission start" it doesn't cause this issue. Engine Rpm remains around 30% and i can accelerate off the runway.

Which is weird how only this module is affected by that...

Maybe C101 is not synchronizing correctly at mission start, who knows?

 

I will leave it with you but please if you could look into that it would be great!

[Nodak]

Try this, go into your saved game folder, config file, input, C-101-XX, joystick, in there you'll see a .diff file, get rid of it.  Those red ! should be gone and your good to go.

[Vibora]

I still think there could be something faulty with your peripherals or your axes settings in the C-101. Did you try unplugging your peripherals, using keyboard for throttle and using another joystick or another axis as throttle? Even though you deleted inputs in saved games, when entering DCS it assigns default axes, maybe some of them is faulty or interfering with your throttle assignment, delete them all before entering the mission, and make some tests assigning specific axes to throttle until you determine the faulty one, if there's any.

In any case, we have made some changes in the code so that compressor stall doesn't happen at mission start, if switches or axes are not in the correct position yet.

Edited May 22, 2021 by Vibora

[Bagpipe]

2 hours ago, Vibora said:

I still think there could be something faulty with your peripherals or your axes settings in the C-101. Did you try unplugging your peripherals, using keyboard for throttle and using another joystick or another axis as throttle? Even though you deleted inputs in saved games, when entering DCS it assigns default axes, maybe some of them is faulty or interfering with your throttle assignment, delete them all before entering the mission, and make some tests assigning specific axes to throttle until you determine the faulty one, if there's any.

In any case, we have made some changes in the code so that compressor stall doesn't happen at mission start, if switches or axes are not in the correct position yet.

 

It would surely affect other modules if this was the case? It doesn't happen anywhere else in any other module or other sim.

Something about this modules throttle axis is not marrying up with DCS the way the other modules are.

Hopefully the code change helps in the mean time

[bazza772]

Same issue as Bagpipe.

 

All other modules work fine and no control conflicts.

 

Of those C101 flights I tested it only occurs on Missions which start Hot on runway - all others, eg airborne start, seem fine.

 

On the hot runway starts all of the other engine instruments increase in sympathy with throttle position except N1 (stops increasing at 51%). After throttle closure the ITT stays up at red line while other instruments return to idle. The throttle has been sensed, just like on all other modules and C101 when in flight.

 

I also created a fresh mission with hot runway start and no failures preset and this still occurs on spooling up.

 

cheers.

Edited May 23, 2021 by bazza772

[Bagpipe]

Glad I am not alone in this.

 

The funny thing is too that I don't usually do hot starts in the C101 because one of my favourite things about the module is performing a cold start following the checklists believe it or not!

 

It just so happened that mission 3 was a hot start and it started playing up