C-101 BUGS WE ARE TRACKING

No veo que sea así. Es más, en mi caso los fps son incluso mayores en la cabina trasera. Necesitaríamos más comentarios de más gente.

===

This user reports lower fps in rear cockpit than in front cockpit.

I don't see this happening. Further more, I even see higher fps in rear cockpit than in front one. We would need more people feedback.

I do have a couple of bugs to report though.

1. The mirror doesn't toggle off properly. If you press M, the mirror turns on as expected. But if you press it again, the mirror doesn't go blank. It just keeps the last frame displayed. FYI, I have seen this issue in the M2000C module so it might be a problem with ED's code or the third party interface. IMO, the mirror should behave as I've explained in this post ...

Folding Mirror:

----------------

 

I think when you fold the mirror back, it is not totally disabling the rear-view image rendering. Yes, the rear-view image is gone but I don't notice an increase in my fps. Only when I press the "M" key to actually turn off the mirror do I see a significant increase in fps.

 

Is it possible to emulate the "M" key action when the mirror is folded back?

2. I'm having trouble getting the ground crew to disconnect the GPU once the aircraft's engine is started. He always says "Unable to comply". I don't have the problem if the engine is off. That's the kind of response I would expect on other modules when you request a refuel and rearm and the engine is running so maybe it has something to do with that.

Thank you for your feedback. Regarding the mirror issue, we were already aware of it and it's WIP.

For the GPU to be able to be disconnected, it's already solved but I'm afraid you'll have to wait until ED makes a branch out of trunk version. For the time being you may use the old key commands combination LShift + P.

Yesterday I was testing and do not found a significant difference between the front and rear cockpit.

Roger. Thank you two for your feedback.

Small bug I noticed with the new radios and the stock C-101 quick missions and single missions. When using the UHF presets, the wingman responds the first time but if I then transfer UHF radio to the backseat and use that preset, the wingman won't respond. I think there is just some sort of synching issue with the old missions. I didn't have a problem when I used the actual UHF frequency.

SOLUTION: I removed my wingmen and readded them and everything worked fine.

This is like a 0.5 out of 10 on the critical scale but you might want to look into it when you have a chance.

Thank you, will take a look at it.

I also noticed a small bug.

In the rear seat the landing gear handle can only be clicked if it was clicked at least once in the up position.

"G" works normally.

Version tested: current 1.5.4 release

Reproducible: Yes, every time

Steps to reproduce:

- Place C-101EB in air or on ground, otherwise empty mission

- takeoff (or if you are in the air already, lower the gear by clicking in the front cockpit or by pressing "G").

- go to rear cockpit

- try clicking the landing gear handle. Note it isn't clickable in the down position.

- cycle the gear pressing the "G" key twice. Note it moves, Still not clickable in the down position though.

- Move it up again by pressing "G" or by clicking it in the front cockpit.

- Rear cockpit: You can click it in the up position. When you have done this once it is clickable in the down position as well.

That's it. :)

Thanks, rear cockpit is in implementation right now, still there are things not working yet.

No veo que sea así. Es más, en mi caso los fps son incluso mayores en la cabina trasera. Necesitaríamos más comentarios de más gente.

===

This user reports lower fps in rear cockpit than in front cockpit.

I don't see this happening. Further more, I even see higher fps in rear cockpit than in front one. We would need more people feedback.

Tienes razon. Queria decir lo contrario. La delantera tiene MENOS frames que la trasera. ¿Se va a solucionar?

Por cierto. la linterna no funciona. Parece que hay un conflicto de teclas.

Tienes el retrovisor activado?

small AI lighting bug

While taxiing, the starboard navigation light isn't lit while the port one is. In flight, both nav lights are lit. This is just an issue with the AI.

EDIT: Is seems to be a problem in flight as well. The light does seem to go on when the gear comes down for landing, though.

UHF radio bug

Hi.

I've noticed that you can communicate over the UHF radio even when it is turned off. Front and rear cockpit.

There's a lot of stuff in here!

I just noticed that the Kneeboard won't advance forwards in the C-101EB, it will only go backwards (Previous page). Tried with HOTAS assignment and with keyboard.

All other modules worked okay.

V1.5 - haven't tried v2

Found a small bug in open beta branch.

The covers for the fuel shut-off valve and boost pump switches aren't clickable. Works fine in release version.

Found a small bug in open beta branch.

 

The covers for the fuel shut-off valve and boost pump switches aren't clickable. Works fine in release version.

Thank you Kontiuka, we are checking it.

Wheel brakes assigned to axis does not work. (but the 'W' key does work)

RCTRL-Enter, to see control axis, is not working

Is the C-101CC supposed to be flyable? I can create a mission and set the plane to "client" but it defaults to AI.

The wheel brake issue is because the C101EB is still using a simple flight model, and the brake axes are not supported.

The C101CC still hasn't been released. Wait for an announcement regarding both these things Maulkin.

Controls window (RCTL+ENTER) is on the to-do list. There are other priorities right now. Thank you for your understanding.

Thanks for the update folks!

Welcome.

everytime i want to fly your jet, my dcs is crashing.

every other module works normal. any ideas?

Be sure you use an up to date version and make a repair if necessary.

After reading about large update for C-101, I want to remind of the very old issue with controls.

Long ago (almost 2 years) support for axis-based head-tracking devices (ones that use joystick axes instead of TrackIR protocols, such as EDtracker) was removed from this module. I raised an issue in this thread https://forums.eagle.ru/showpost.php?p=2331537&postcount=159 and it was acknowledged as bug, with promise to “fix and post an update ASAP” https://forums.eagle.ru/showpost.php?p=2331668&postcount=160. It was 28.02.2015.

The problem is C-101 is the only module which do not support any head-tracking device except TrakIR/FreeTrack.

I never used it for 2 years despite many good reviews from other users – it just not very enjoyable to use DCS-level module without head-tracker. I waited patiently in hope at some point I be able to use this module again.

But now it stated that C-101 is almost finished and I decided to ask one more time.

So I would be extremely grateful for clarification.

Is there any hope that axis-based view controls be restored?

Or it never be implemented and I should stop waiting and move on?

I am sorry for my poor English.

After reading about large update for C-101, I want to remind of the very old issue with controls.

 

 

Long ago (almost 2 years) support for axis-based head-tracking devices (ones that use joystick axes instead of TrackIR protocols, such as EDtracker) was removed from this module. I raised an issue in this thread https://forums.eagle.ru/showpost.php?p=2331537&postcount=159 and it was acknowledged as bug, with promise to “fix and post an update ASAP” https://forums.eagle.ru/showpost.php?p=2331668&postcount=160. It was 28.02.2015.

 

 

The problem is C-101 is the only module which do not support any head-tracking device except TrakIR/FreeTrack.

I never used it for 2 years despite many good reviews from other users – it just not very enjoyable to use DCS-level module without head-tracker. I waited patiently in hope at some point I be able to use this module again.

But now it stated that C-101 is almost finished and I decided to ask one more time.

 

 

So I would be extremely grateful for clarification.

Is there any hope that axis-based view controls be restored?

Or it never be implemented and I should stop waiting and move on?

 

I am sorry for my poor English.

Hello Mordhar. Here you have a quick hot fix for the issue you just described. Please check it and let us know if that works. The fix will be included in the nearest C-101 module update.

The address for this file is: Mods\Aircraft\C-101\Input\C-101EB\joystick\

default.lua

Hello Mordhar. Here you have a quick hot fix for the issue you just described. Please check it and let us know if that works. The fix will be included in the nearest C-101 module update.

The address for this file is: Mods\Aircraft\C-101\Input\C-101EB\joystick\

Thank you very much. I really appreciate quick response and help.

I used the file you provided and everything works perfectly. All axes for camera control are now present and bindable.

I also want to apologize for my previous post, after reading it today I find my wording may look rude.

Good luck with the future development. It is easy to miss small details when progress is seen in small portions, but today I was able to compare current version of C-101 with extremely old (as it been 2 years ago) and difference is apparent. Thank you for your hard work.