gulredrel

Hello, back from a flight in the C-101CC where fuel warning came on short after a touch and go. Went around, landed and during taxiing back, fuel pressure warning came on first flickering and shortly afterwards was solid and the engine quit. I started my flight with 1980 lbs of fuel regarding to mission editor. With the engine quitting during taxi, the fuel totalizer showed 1400 lbs of used fuel. The fuel gauge showed around 200 lbs. Haven't found something in the manual regarding usable fuel and reliability of the fuel totalizer or the fuel gauge. What should be taken into account for fuel planning if neither the fuel gauge nor the totalizer is showing accurate data?! What amount of fuel needs to be considered as not usable? I have the track file, but it's 6.7MB large and you would need to watch more than an hour of just a scenic flight in SA map. Thanks Jens

That's not specific to L-39, it's a general DCS issue, where everything else than concrete or asphalt is like muddy glue. Don't know if this will change or not. Grass airfields on WWII maps should work. I have no idea how the terrain characteristics are modeled.

Voted for sticking with the satellite imagery. Don't think that popularity of the map will rise when changing everything to hand crafted textures. I like the latest performance improvements. This and maybe creating more local assets is what the resources should go into. edit: That's just looking great as it is:

Punta Arenas training sortie. Puerto Natales - Aeropuerto Teniente Julio Gallardo

Thanks, no more jittering for the trains. Trains below railway on some maps and wheels not turning is an open issue, regarding the other thread.

Is the issue with the wheels not turning also known issue / related to being below the tracks?

Currently there is no keybind available for that, but IFE is aware of it. See this thread for details.

Hopefully this will get fixed soon: "At the moment we are working to fix some annoying issues on the CDU and Custom Data Card and other issues related to the navigation, and we are finalising in parallel the flight director." Has been said here:

+1 for this. I also would like to filter search results or search pre-filtered results. Anyway would do it.

Thanks, confirmed fixed, also tried it on my end some minutes ago.

Huge changelog, thanks for support, download in progress. Looking forward to this next iteration of S-3B, B-52 and B-1B 3D model.

Here is how it works with the corresponding frequency range switching via far/near switch in Beslan - first select the OM frequ. 250 kHz in the lowest frequ. range on the ARK-5 control panel - check on the ARK-5 control panel, that in the highest frequency range 250 kHz corresponds to 1050 kHz (slight needle swing on radio compass) - set frequency range back to the lowest on ARK-5 panel - on the left, there are three switches. You need to select the highest for the third range - now switching far / near switch you can see frequency range dial changes position without the change of the rotary on the ARK-5 panel And the track from 2.9 MT, from which I created the video. Regards Jens 20231116_MiG-15_Beslan_OM_IM_near_far_frequ_range_change.trk

See derelor's description in one of the threads above. With the three switches on the left, you select the sub-range for near switch. Need to correct my post above. The airport with B was not Batumi, but Beslan where it used to work. Maybe I can create a track to show case. I don't know if there is a pdf or thread which lists the compatible airfields but these are not many. The maps and navigation aids do not match with how the nav aids were set up for an early cold war era airplane. L-39 has a more modern navigation set where you separately can tune frequencies for inner and outer NDB to be used with the near/far switch. MiG-19 has a work around, where you can set up different frequencies regardless if they match the position of the tuning crank in different sub frequency bands, like it needs to be in MiG-15. Best is to only use one NDB and arrive at it at the runway heading.

I don't know, but there are only a few airfields in Caucasus, where the FAR/NEAR switching works. You only set the FAR frequency, the near frequency than depends on the selected range. and the frequency is held into place. I think, it's Batumi Beslan which is set up to work correctly with the outer marker frequency position matches the inner frequency position in the different range selected. Please see details here: or here:

Great update, thanks for the continued work on the map.

Thanks for moving the thread. Did a quick test with just the AI F1BE and me sitting on the ramp. F1BE landed and released the chute after landing at mission time 08:05:46: Plane arrived at parking spot: 08:10:34 Ended mission with plane parking and mission time: 08:22:28, chute was still on the runway around 17 min after releasing the chute. Tested in MT 2.9, track attached. 20231110_F1BE_AI_drogue_chute_RW_time.trk

Thanks for the reply. @Flappie Can you move this thread to DCS general objects bug or should I report a new bug there? Need to create a track anyway I guess which shows the problem. The mission in which I took the screenshot was long and I noticed this on my landing roll, that the chute from the AI plane was still on the active runway.

Hello, had a mission with a F1BE AI plane landing before me at Kobuleti. I noticed, that the dropped chute stayed on the runway really long. Plane landed RW 07 and was long on the taxiway almost all the way back to the beginning of RW 07. I know, it will not do anything to other planes, but the chute should be collected / disappear shortly after the AI planes leaves the active runway, regardless how long the taxi route will be. Or is the chute object hard linked to the AI plane and will only disappear when the AI plane gets deactivated? Flight was in 2.9 MT. Thanks Jens

Hello, some examples of my data card testing a while ago. The file "mb339nelliscreech.txt" dates back in May 2023. mb339creechnav.txtmb339nelliscreech.txtmb339navigation.txt 6S.Duke stated somewhere, they are working on Flight Director and improvements regarding data card. I posted some bugs regarding the data card usage. It will also not work correctly on some maps, cause the default for the map is or wasn't generated correctly back then. Currently I'm waiting for the FD and changes to data card to try some more mission creation with data card. Regards Jens

Thanks, maybe the issue is related to this general DCS thing as Flappie noted in the thread regarding similar issue in F-86. So in best case, nothing to do for you.

Thanks, will try with next OB update. This was my report in F1 bug section:

@Flappie Is it specific to the F-86 or a general DCS thing? Had similar tracer smoke in the F1BE cockpit when firing the gunpods.

presenting the new toy

Hello, did a single player flight in the BE and changed between front and rear cockpit. Is the rear seater's "fuselage indicators selected light" working or currently WIP!? I couldn't see any difference when setting the front cockpit's fuel gauge selector switch to feed or fuselage position. Can anybody show a picture with the light in off and on state? Maybe it was to dim on my end? Thanks Jens

Hello, sorry if this is known or has been reported elsewhere but I haven't find an entry for this here. When shooting the gunpods in the two seater version, the smoke trails from the rounds are visible within the cockpit. Please see the following short video taken with DCS 2.9 MT version: 20231031_DCS_2.9_MT_F1BE_gun_smoke_in_cockpit.mp4 Thanks Jens