gulredrel

@NineLine Still an issue in DCS/2.8.5.40170 (x86_64; MT; Windows NT 10.0.19045) So I guess still WIP? So these threads are also related to the hydraulic system:

Still an issue with current OB. 2023-06-06 07:15:10.565 INFO APP (Main): DCS/2.8.5.40170 (x86_64; MT; Windows NT 10.0.19045) Hydraulic pressure will not bleed after engine is stopped and cycling flaps or cowl flaps.

Thanks for posting. This was also a thing I noticed having bought the P-47 lately. From a my point of view, having that little handpump will not instantaneously increase pressure to 800 PSI. This should look like increasing a bit during a stroke and needing several strokes to reach 800 PSI. Hope this can get fixed in the future.

just watch the intro... Would be nice to see some assets, but better not get greedy. Let's let them do their job with the plane and map first.

Rocket salvo attack on this row of containers 36°43'10.6"N 115°39'15.7"W. RTB touchdown imminent a bit fast in the turn... Internal fuel only is so low. I had to refuel at Creech to be able to get back to Nellis, after flying multiple attack runs at the target range.

ups... you're right. Something ending on ...us Nevertheless, content and feedback of both is appreciated.

Thanks for sharing. Even being a small helicopter, twitchy FM and returning stick to center to stop rolling was always weird compared to the other helicopters. Love the "Loading Barundus AI..." on the tablet. Hope he will return to the Gazelle with the updated flight model. Like his Mi-8 tutorial videos.

Thanks @Rudel_chw, Have I seen it correctly, you changed the arguments in range min / max values 0.9/-0.9 to 0.5/-0.5 for the cockpit argument in range aileron roll axis triggers? How can someone identify the plane / cockpit argument numbers and it's values to use them as triggers?

I've created a ticket and added the info there.

Hi there, I also get these Sim PostStart hanging on mission load. I placed several ground personnel units at Nellis ramp. I've installed target range mod, but this wasn't a problem since. Sometimes the mission loads, when I opend unit preview in mission editor. I've deleted this temp folders but this didn't help. Some logs attached. edit: dcs_mission_load_success_2.log added after successful loading after clearing metashader and fxo folder. Thanks Jens dcs_hang_on_mission_load.log dcs_hang_on_mission_load_4.log dcs_mission_load_success.log dcs_hang_on_mission_load_3.log dcs_hang_on_mission_load_2.log dcs_mission_load_success_2.log

If I read the mission triggers correctly, you need to bank left and right (move stick left and right to it's extreme position). Do you have any curves / dead zones / or something double mapped in your controls setup so that the stick travel can not be maxed out? If time permits, I'll try on my end. Do you use stable or OB (single / multi threaded)? EDIT: Can confirm your findings. Mission will not proceed in Step 11 of after startup checklist. Doing aileron control check, nothing proceeds and there is no option to proceed with spacebar or something like this. Track can be found in the following link as it's quite large: C-101FA-Lesson-01-Start-Up-V4.miz_23052023_115500.trk

Hello, can someone with MB-339 and Syria map please check if it constantly crashes when hitting the Fly-Button after mission load and passing control to player? DCS/2.8.5.40170 (x86_64; MT; Windows NT 10.0.19045) MIssion and datacard file (same as mission file but with .txt goes into following directory ...\DCS.openbeta\Config\MB339\Datacards) attached as well my various crash logs. Created new Syria mission, only MB-339 placed at Beirut Intl. Created datacard with some waypoints and flightplan. I've a mission in Caucasus, where I can load and start mission with my datacard navigation file. Loading mission without the datacard in Syria works. Could be related to this, which isn't fixed yet. But in November I got Persion Gulf datacard to work, haven't tried in Syria until now because of the wrong HSI bearing which was fixed in this week's OB. So decided to try this in Syria. Thanks Jens 20230520_1_crash_dcs.log 20230520_2_crash_dcs.old 20230520_3_crash_dcs.log 20230520_4_crash_dcs.log mb339sightseeing.txt mb339sightseeing.miz

Yes, noticed the same, but there was nothing mentioned in the patch notes, so I didn't expect it to be fixed.

*bump* Still an issue. Was flying in Syria today. File with Syria nav data was created with the name .autogenerated.txt. Is there something new or how are your plans to get the FD working? Maybe there's a chance to get this fixed during development. Glad that RNAV bearings are now working again with yesterday's patch.

Looks like this is fixed with yesterday's open beta DCS 2.8.5.40170. Having TACAN switched on and selected, I was able to talk to ATC on approach.

Real life interfering here. Hopefully I'm able to check later in the evening. Update after a long day had a chance to fly a short mission. Can confirm, issue is fixed with yesterday's DCS 2.8.5.40170 OB. Thanks IFE.

Glad I'm not the only one having seen this after coming back to the Viggen. I also was used to hit the reference button once lined up and slight deviation was corrected. Now it's perfectly aligned.

Here you go track attached and short video. First turning left no problem, but at the end coming back near the original heading, it is clearly visible, that something is not working as intended in how the IDN needle is pointing and changing: https://www.youtube.com/watch?v=jeVQgHEoqck 20230508_F1EE_IDN_heading_to_WP_jumping.trk

Hello, just wanted to report a massive height difference near a river / lake about 8 NM north of Stoney Cross at this coordinates: N 51°01'53.57" W 1°40'21.07" Thanks Jens

Hi @fausete, did a flight today using full ALN mode in Normandy 2 map. Much better with this but noticed a different behavior of the heading needle and don't know if it's part of the INS wip things. One of the waypoints was roughly at a heading of 340° from my present position. Flying 350° the heading needle pointed 10° left. As I steered to the right and turned on to a heading of 010°, the needle pointed first to about 30° left and than jumped to 30° right! Turning back left and crossing roughly 0° the needle jumped back to around 20° left. If needed, I'll recreate this and take a quick track and video. Thanks Jens

Stored heading alignment is implemented, but currently not working properly. Aerges is working on this.

Hello, noticed the following with the F1EE's IDN mode indicator. 1. With the INS off, the mode indicator needle points to NAV-VA: 2. With the INS in standby, the mode indicator needle points to RNAV-N: 3. If you than right click on on the mode selector, the needle jumps to the NAV-N position: Problems here: What are the correct off and init positions? Regardless of the position, first click on mode selector should only switch to the next position. Thanks Jens 20230426_F1EE_IDN_Mode_Selector_strange_init_MT.trk

Okay, thanks. Will use full alignment. Do I have to wait a certain time after switching on "Heading and Vertical reference System" and the "emergency gyro magnetic compass switch" before starting the alignment? Or are they independent of the INS platform?

First: unlock the open canopy. Second: Click on the little canopy clamp (in manual named "canopy partially closed position device"). This will position the canopy in the partially open position. Clicking the clamp again will close it fully. Same works wen coming from the closed position. I noticed, that the click spot on the clamp is only active, when the canopy is not locked open / locked closed. Hope this helps.

Added info. Looks like problem with cold start and alignment?! Not sure if it's on my end. Need to do more testing. Used stored heading alignment without changing positions. Do I need to wait after engine start and generators online before starting INS alignment? From hot ramp start mag vs. true north is okay in Caucasus: From cold ramp start and stored alignment, mag vs. true north is too far away in Caucasus: