Vibora

Las texturas del F-18 español las hizo mi compañero de AvioDev, Pablo, ya que las originales que iba a sacar ED tenían errores y, por decirlo de alguna manera, tenían una serie de deficiencias. Hace ya meses Pablo observó este error que apareció en las texturas debido a una modificación arbitraria de ED, y lo reportó, proporcionando la corrección. Ahora se lo ha vuelto a recordar a ED y aparecerán corregidas en la siguiente actualización.

Our internal version, mostly equivalent to Open Beta, except that cockpit textures are correct, specially lighting (i.e. engine instruments digits lighting, etc). But that shouldn't make a difference to follow the FD bars, keep speed and read altitude, HSI and ADI. I used the attached mission, but, really, you don't need any specific mission, just put your head down looking inside the cockpit and look outside when you are at 200ft above airport altitude for example. That would be minimums for CAT I, which is what you can do with this airplane. You can also get into the rear cockpit with IFR hood on, and jump to front cockpit when you get to minimums. Tips: Use active pause at mission start to set up your cockpit. Make use of DME Hold function, open the kneeboard to look for TACAN/DME paired frequencies. Set 108.8 MHz and set DME Hold switch in DME HOLD. Set ILS 110.3 MHz with course 122º (128º - 6ºE). Airport elevation: 1574 ft. ILS Minvody.miz

I've flown a CAT III approach (with 200 m of visibility) in the C-101EB and C-101CC to test this, landing without issues, though vertical bar is a bit too sensitive. If you try to persuit the bar you end up overrreacting. We have changed sensitivity to make it behave similar to the C-101EB. Check it in next update.

We have never seen that issue. It could be due to a bird strike, but usually you would get warnings in the cockpit. The issue with missing marks in the runway is also something we have never seen either. Try to save a working trk next time that happens.

When a panel or instrument loses it's paint due to wear, the integral light will be seen through it, this was simply overdone in previous version (too much wear or, in other words, too much percent of total surface with wear). It will look better with new textures.

C-101EB and C-101CC new cockpit textures will be available in next Open Beta DCS update.

I'm talking just about our module. C-101 cockpit lighting and C-101 landing lights beam.

We have lighting issues solved, but you'll have to wait for next DCS update, which currently are been delivered at a longer pace than it used to be. You can dim the reticle (pipper) with the knob on the left of the gunsight, but you won't be able to get rid of that odd red brightness.

Congratulations! We are happy to see you using our module and enjoying it :)

Thank you! I don't recall having got any report about such bug. Do you have a screenshot?

Yes, but no ETA.

We have been working on new cockpit textures that are nearly finished, just missing some minor items. We could have released it in last DCS Open beta build, but we decided to have it fully finished so that you get a satisfactory experience from the first moment. You can see some screenshots in our Facebook: https://www.facebook.com/Aviodev

What Spanish handbook do you mean? The REV mode is meant to be used when flying a Back Course Approach. The signal to the Flight Director is reversed so that it provides correct guidance indications to follow the localizer. Otherwise, when flying a back course approach, as the airplane is flying in the opposite direction as the normal front ILS course, the guidance would be in the wrong direction (i.e. fly left when is should depict fly right). BTW, when flying a BC Approach in the C-101 you have to set the same course in the HSI as in the front ILS. Let's say you want to fly a BC in Batumi to RWY 31, you would set 110.3 MHz, Course 119 and press REV in order to get FD guidance. Or just fly a raw data approach following LOC deviation indications in the HSI. You can see some info about BC approaches in this link, or just google for back course approach: https://www.boldmethod.com/learn-to-fly/systems/how-to-fly-a-localizer-back-course-approach/#:~:text=When%20you%20fly%20a%20localizer,with%20a%20few%20key%20differences.

There should be no relation between easy comms and radionavigation. I've tested it and ADF works both with easy comms and without. White dashed needle in RMI and pink needle in HSI (if bearing select button is pushed to select ADF instead of NAV) point towards the radio station tuned in the ADF control panel. If you still see something else, please provide more details about it. Thank you.

I'm sorry to see that you decided not to buy our module because multicrew is not completed. We have in our plans to work on it in a few weeks.

C-101EB mirrors exactly real aircraft data. You can fly IFR in a realistic way using any of the cockpit instruments. EB engine fails when exceeding an ITT of 832°C for more than 5 min, this limitation is removed in CC according to subject matter expert.

De nada :)

This was commented before. We are planning to add some additional capabilities to the Sea Eagle, but it is right now in a low level in our priorities list.

I don't think they were using a joystick extension but rather just a conventional one. Joystick configuration is something very personal. You can use it as a reference if you like. Personally I don't use any curves except for rudder. It also depends on the quality of the joystick you use. A low quality or very deteriorated one would probably need a lot of curve and neutral zone. Hope that helps.

We will probably do it in the future for the C-101CC, but not right now.

I was talking about the real airplane. To be compatible with NVG's a cockpit should be black and with green lighting. We could implement it in DCS but that would be highly unrealistic, because the C-101 cockpit is grey and with red lighting, not to say that it was never done IRL in this aircraft, it would need that specific colour and lighting obviously. We could implement it for playability but that would take a rather large amount of time and we have other priorities.

That is know and already fixed in internal version. It will be OK in next update.

We are busy with other stuff now. I hope we can get back to multicrew soon.

This is known from long time ago and already solved, will probably be in next update. Why would L-39 flaps be similar to C-101 flaps, even angle of extention? Our module shows precisely the flight model of the real aircraft. See the attached screenshot comparing a real situation with our simulation, showing around 3º of pitch with flaps at takeoff. Of course weight and other parameters can make data vary slightly, but this shows you that parameters fit. I'll try to give an answer soon. We don't publish bug lists, we manage it internally. We fixed an error in the FM code some time ago, we are not working on anything else regarding flight model right now. Txs for your reports.

It's how it works. When changing from VOR to TACAN you change the source for the presentation in the HSI, but distance window keeps showing distance to the station set in the TACAN equipment. You have to set the inbound course, not the outbound course if you are flying inbound, otherwise you will get opposite indication. That is the cross and dot indication window. The model will look better in next update. That is known. Txs.