

Martin2487
Members-
Posts
134 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Correct as is? I don't understand. Can I ask for feedback on why this is good? Command bars do not move in the current version. That's not correct.
-
ADI command bars.trk I am attaching a short track from the flight. As can be seen on the track and in the picture, the command bars (yellow) are still in the same position, even though they should show the required pitch and roll at this phase. The inactivity is also evident from flags K(Крен) and T(Тангаж), which would disappear from ADI if the command bars were functional. In this context, I am correcting my statement that command bars should be on the side when they are inactive.. This condition is indicated by red flags T and K. As far as I know, these command bars help not only with intercepting the localizer and glideslope, but also with intercepting the RSBN radial, etc. See MiG-21.
-
Stick deflection limiter override default bind on the Y key. Could someone explain its function and where this button is located in the aircraft? If I understand correctly, its function is to enable override of the angle of attack limitation system. Was there something like this in a real airplane? I thought this system could be overridden with the control stick. That's why I was surprised to see a button here. Thanks for explaining.
-
The ADI shows abnormal and jerky motion in the pitch indication. I have attempted to show this in the attached track. However, the issue is easily reproducible, as it is visible at first view. ADI bug.trk
-
- 1
-
-
When starting the engines, it is necessary to wait 40-50 seconds after starting one engine to allow the starter to stabilize. Only then should the second engine be started. The automatic start in this module does not respect this and starts the second engine immediately after the first engine has finished starting.
-
The command bars on the attitude indicator do not work. When the ADI is turned off, they should be on the side of the ADI. In the MiG-29, similar to the MiG-21bis, this type of ADI and these crossbars should be able to provide information about the necessary pitch and roll to capture the RSBN radial, information about the aircraft's position relative to the localizer and glideslope. I believe that even in Return mode, the ADI should provide information about the necessary pitch and roll.
-
fixed ATGMs not being cleaned up on impact
Martin2487 replied to MetalStormGhost's topic in General Bugs
The landing ship Ropucha in DCS is capable of sailing at a speed of 34 knots. According to public sources, this ship is capable of reaching a maximum speed of 18 knots in real life. -
I tried one of the few faults that can be set in the editor. I tested the left engine fire after the first minute of the mission. The engine fire caused a sharp rise in the left engine exhaust gas temperature. The fire protection system was activated automatically. Correct behavior. However, as the fuel supply to the left engine was not interrupted, the left engine caught fire again. Although the left engine was on fire and flames were visible on the left engine exhaust, the left engine's exhaust gas temperature gauge (2UT-6K) showed the normal engine temperature. Therefore, if the engine burns again, the engine exhaust gas temperature meter shows incorrect values. Therefore, it is not possible to identify a possible engine fire. It doesn't seem like the right behavior to me. I'm attaching a track. Mi-24 exhaust gas temparature not detected repeared engine fire.trk
-
I think I have a suitable proposal to solve this problem. I think it would be good for you to modify the manual for Supercarrier or for Hornet and add this rule there with an explanation. It will be a guide for both pilots and how this situation is handled, as well as for mission and campaign creators. Yes, of course, the conditions are not always perfect and yet it lands. But there is a limit below which one cannot go or it is not necessary or appropriate. Of course, even if the ship is sailing against the wind, the wind may have a variable direction, etc. But I am afraid that some missions are already conditions beyond the border and it is necessary to consider their correction. All you have to do is change the speed of the ship, you don't necessarily have to change the wind speed. However, some of the most problematic missions will need to be adjusted. In my opinion, these are missions: Persian Gulf FA-18C Case I Carrier Landing.miz Caucasus FA-18C Carrier Takeoff.miz C-SUPERCARRIER-HORNET-COLD NIGHT START same as C-SUPERCARRIER-HORNET-COLD START.miz and C-SUPERCARRIER-HORNET-LAUNCH.miz Caucasus FA-18C Case III Carrier Final Approach Landing.miz Caucasus FA-18C Carrier Cold Start.miz Caucasus FA-18C Case III Carrier Landing.miz These missions are usually used by people who are learning to land using Case I. Therefore, I do not think it is appropriate to offer them a solution when the ship slows down. Even with Carrier Qualification, pilots are not exposed to such conditions. CNATRAINST 3740.9D page II-5 defines the tolerated limits for Carrier qualification. I enclose a picture here. Here you can see that as an absolute minimum Wind over deck for pilots who perform Carrier qualification is 20 kt. In conclusion, I would like to thank Gumidek for conducting a mission search and finding out how to resolve the situation. Thanks such a Vincent. I am very grateful to you boys because until today I did not have this information and I often had a very short groove time. Now, thanks to you, we know more. Thank you once again.
-
If the airport has unlimited fuel set in the mission editor and the fuel tanks at the airport are destroyed, the airport is still able to refuel the aircraft. I noticed this change recently. It definitely didn't work that way before. Even if unlimited fuel was set at the airport, it was not possible to refuel at the airport after the destruction of all fuel tanks. The planes that had a spawn slot added at the airport were without fuel. The difference between setting up an airport with limited and unrestricted fuel was that if unlimited fuel was set at the airport, all fuel tanks had to be destroyed because the amount of fuel did not decrease. I sincerely hope it's a bug because most missions, even on MP servers, use unlimited fuel settings at the airport. If I take into account the speed of the runway repair, which is 1 hour, and the impossibility of destroying the fuel tanks at the airport, the airports become almost indestructible fortresses. Since I don't remember it being presented somewhere in the changelog as a change, I decided to report it as a bug. The attached track destroys fuel tanks at Sukhumi Airport. The airport has unlimited fuel set. After destroying the fuel tanks, as can be seen on the track, the aircraft that has the spawn slot at the airport has fuel in its tank and I can even refuel the aircraft. The attached track therefore demonstrates the problem described above. Destroy fuel depot with unlimited fuel setting.trk
- 2 replies
-
- airport
- unlimited fuel
-
(and 2 more)
Tagged with:
-
If you enter coordinates in the wrong format when creating an SLMR turnpoint (STP) and the message ERADA appears on the UFC, it will cause that I can no longer enter any coordinates into aircraft systems (not only STP) because even if I enter the correct format on the HSI page it still appears on UFC message ERADA. So if you make a mistake in entering STP SLMR coordinates, it is no longer possible to enter any coordinates into the aircraft system !!! I checked if this is not a problem only in the navigation system. Unfortunately, no. If I enter the wrong coordinate format on the HSI, the message ERADA will appear on the UFC, of course, but then the system will receive the coordinates. So it works correctly. Therefore, the problem is caused by the AGM-84 SLAM-ER. Coordinate input in the wrong format SLMR turnpoint(STP) causes can not enter coordinates on the HSI page.trk
-
For standards with such a large RCS, it does not seem standard to me. Thanks for your work, but your test plane was a Su-27. The maximum target detection distances per fighter-type target can be +/- real. I don't want to speculate on that. Your Su-27 test aircraft had an RCS of 5.5 m2. I tested it on targets with an RCS of 80 m2. Of course thanks for your work, but my bug report doesn't criticize radar performance on fighter targets.
-
Since one of the previous updates (after version 2.7) there was a problem with the fact that the air to air radar is not able to detect an aircraft with a large RCS above a distance of 80 NM. Tested on IL-76, C-17, B-52, TU-95, E-3A aircraft. The usual detection distance for aircraft of this type is from 72 to 78 NM. That's pretty little. The APG-73 has a theoretical maximum target detection distance of 160 NM. For targets with such a large RCS that I tested, I would expect a target detection distance of around 100 NM. I also performed a test of the maximum detection distance on an aircraft from civil aircraft mode Airbus A-380 which has an RCS (set in the lua file) 80 m2 target detection distance again did not exceed 80 NM. All tests were performed on targets that had an HOT aspect at an altitude of about 30,000 ft, PRF MED / HI interleave, azimuth scan 20 °. Hard to say where the mistake is. It almost looks as if the maximum target detection distance is set to some low value somewhere in the script. Although it is a different goal in terms of size RCS maximum detection distance fluctuates +/- several NM. It worked well in previous versions, I only see the bug in some update after version 2.7 Attached is a track file where the test target aircraft is represented by the C-17A. AA radar range detection test airplane C-17.trk
-
I tried it but, unfortunately, without effect. The SA-10 did not fire on HARM. I don't know if they modified the RCS AGM-88C. But even in PB mode, HARM is detected by SA-10 at a distance of about 31 nm. If fired in TOO / SP mode, the SA-10 will shoot it down. As far as I know, the AGM-88C has RCS set to 0.05m² in DCS. This bug report is about a HARM that was fired at maximum range at high altitude (see Tacview in the first post). Terminal speed was 617 kts TAS, M 0.93, pitch 25 °. The HARM was definitely not outside the parameters of the SA-10. The SA-10 certainly has no problem shooting at supersonic targets. As I mentioned even though the HARM was not fired it was detected at a distance of about 31 NM. I don't think there will be a problem with the acquisition time. The TR 30N6 has an acquisition time of 6 seconds. I have noticed this problem with other systems that have anti radiation missile capability. It will still check it and possibly process a separate bug report. Finally, please stick to the topic. This thread is about SA-10. SA-15 shoots down HARM in PB mode (tested). You just need to set the skill of the unit to excellent (this affects the acquisition time).