Search the Community
Showing results for tags 'correct as is'.
-
correct as is hsi hsel not affected by magnetic/true changes
Coding posted a topic in Bugs and Problems
at around 08:05:40 I fiddle with the hsel option from the hsi page. when changing the aircrafts heading mode from magnetic to true the hsel value is not changing and it stays in magnetic mode. bugflight.trk -
Hi noticed when the DED is on the markpoint page the TGP input stops working > ICP 7 (to get the mark point page) > DMS up to move to HUD > TMS long to get to HMD designation > TMS up twice to make a mark point > DMS down to get TGP as the SOI now none of the tgp buttons work (eg TMS left to change camera type or TMS up to make a point target or slew function to move the camera) go back to the default DED page (return on the dobber) and the tgp works again I would think the tgp when set to SOI should work regardless of the DED page
-
Hello together, I have discovered some interesting behaviour of the HARM when shot in EOM mode without spike or nails on the RWR. When shot, the Harm overshoots the steerpoint and when the plane gets the ping, the harm turns itself very harsh and track the target. Is this really possible? Trackfile and Tacview attached. Thank you! Harm-EOM-Behaviour.trk HARM-EOM-Behaviour.acmi
-
Wind over deck and recover speed would be 25-30 knots in direction of landing axis. Not in BRC direction. I need to say, that I didnt checked the campaign missions, only single and quickstart missions. Persian Gulf FA-18C Case I Carrier Landing.miz: Carrier WP0: 25kts WP1: 5kts Headwind: 5kts Result: Carrier slows down I player try to land with insuficitient WOD. Persian Gulf FA-18 Strike Fighter.miz: Carrier WP0: 11kts WP1: 11kts Headwind: 4kts Result: Carrier with insuficitient WOD 15 knots. FA-18C_IA_PG_Flown the Coop.miz Carrier WP0: 21kts WP1: 21kts !!! TAIL wind: 3kts !!! Result: Carrier with insuficitient WOD 18 knots. FA-18C_IA_PG_Missile City.miz: Carrier WP0: 0kts WP1: 27kts Headwind: 7kts Result: Carrier with WOD Overspeed 34 knots. FA-18C_IA_PG_GOPLAT Defense.miz: Carrier WP0: 17kts WP1: 17kts Headwind: 4kts Result: Carrier with insuficitient WOD 21 knots. FA-18C_MAR_IA_Hot Start.miz same as FA-18C_MAR_IA_Cold Dark.miz same as FA-18C_MAR_IA_Free Flight.miz: Carrier WP0: 17kts WP1: 17kts !!! TAIL wind: 4kts !!! Result: Carrier with insuficitient WOD 13 knots. Caucasus FA-18C Aerial Refueling.miz: Carrier WP0: 11kts WP1: 11kts Headwind: 7kts Result: Carrier with insuficitient WOD 18 knots. C-SUPERCARRIER-HORNET-COLD NIGHT START same as C-SUPERCARRIER-HORNET-COLD START.miz and C-SUPERCARRIER-HORNET-LAUNCH.miz Carrier WP0: 10kts WP1: 11kts Headwind: 15kts (45° port side) Result: Carrier with WOD 24 knots, not bad, but wrong carrier course results more port wind than desirable for safe landing procedure. Caucasus FA-18C Carrier Takeoff.miz Carrier WP0: 11kts WP1: 11kts Headwind: 7kts Result: Carrier with insuficitient WOD 18 knots. Hornet 1989-Alert 5.miz Carrier WP0: 20kts WP1: 11kts Headwind: 5kts Result: Carrier with insuficitient WOD 16 knots. Hornet 1989-CAS.miz: Carrier WP0: 20kts WP1: 11kts Headwind: 12kts Result: Carrier with WOD 23 knots - could be little more, but almost ok. Hornet 1989-OCA.miz Carrier WP0: 18kts WP1: 18kts Headwind: 12kts (20° Starbord side) Result: Carrier with WOD 28 knots, not bad, but wrong carrier course results more starbord wind than desirable for safe landing procedure. Caucasus FA-18C Case III Carrier Final Approach Landing.miz Carrier WP0: 25kts WP1: 11kts Headwind: 5kts Result: Carrier with insuficitient WOD 16 knots. Caucasus FA-18C Carrier Cold Start.miz Carrier WP0: 11kts WP1: 11kts Headwind: 7kts Result: Carrier with insuficitient WOD 18 knots. Caucasus FA-18C Case III Carrier Landing.miz Carrier WP0: 25kts WP1: 11kts Headwind: 5kts Result: Carrier with insuficitient WOD 16 knots. -
When I press the FOV button on the MAV page, the FOV sometimes does not change (Can be seen at the end of attached track file) mav_fov_not_working.trk
-
After the designated point has been changed by the tgp, I expect that by switching TDC to the mav page, that mav will try tp lock onto the designated point. Sometimes this works but somtimes not (See attached track file @08:02:52) mav_lock.trk
-
Hello, Following scenario : multiple targets close to each other with waypoint set over one target. I designate the waypoint then uncage the mav. Its locking one target. Now I want to shoot at another target close to it : I undesignate then start to slew my seeker. If I'm clumsy and do not release TDC depress right over my target the seeker is not stabilized anymore and it gets real hard to lock anything espacilly if moving because I have to compensate for the aircraft moving. Is this intended ? Track showing the issue attached. Thanks. ground.trk -
Hey all, After the last update the A-10 has had some bugs it seems. Bugs: On startup there are errors including: IFFCC fail CADC fail GCAS fail Left Gen fail Hud fail This seems to be online only in hot and cold started planes. This was with me and 2 others in my group
-
correct as is Destroyed SAM Hawk units don't burn and smoke.
diditopgun posted a topic in Object Bugs
Hello ! Destroyed SAM Hawk units don't burn and smoke. I test on BTR-80, Shilka and Patriot site, they all burn so it's maybe only Hawk's related. Latest Open Beta patch. -
So me and my 2 friends where on the same server (a client server) * We all aligned our HMD with the correct process. * We activated the forward hud and locked our FLIR at target with HMD *The target shows up spot on in the FLIR MFD * we activate the FLIR MFD for some fine adjustment * then when about to shoot a mawerick for example, you can se in the front hud how the flir indicator is way off, but the MFD FLIR is still spot on target * The bombs is also way off target at impact. Even tho the FLIR MFD is spot on I tried the exact same setup in singelplayer, and it works flawless I should add that im not an super pro DCS guy, still learning. So in best case it could be on me and my friends. But its odd when the same setup and process works without issues in singel player... See attached for TRK-file *Edit (oh, the TRK file is 38 mb, max upload size here is 5mb) -
Basically the title. Basically if you over speed the gear while taking off, when engaging in an a2a fight, the radar will lock the target but none of the air to air missiles, except the ones mounted on the wingtip, will fire. In the track provided I was using fuselage aim-120c's, aim7 sparrows on the inner left and right pylons, x1 aim-120c on the outer left and right pylons, and wingtip 9x's. Once the target is locked I try firing with both the -120c's and aim-7s, neither of which will fire. the 9x's will fire though. I waited until an in range cue is given to try to fire the -120c's and aim-7s but they still will not fire. Ive tested this in both single player and multiplayer. Track file below is in a single player mission and I have included it. bugtest3.trk bugtest.miz -
Hello! I attach a track where I wanted to attack the SA2 at WPT-2. I released 4 JSOWs and they flew to the target waypoint, circled around the target and finally navigated into the sea without attacking anything. Did I do something wrong? It was a hotstart on the ground - A-G Mode, JSOWs where aligned, released at aroung FL300... JSOWs_NoAttck.trk
-
[NOT A BUG] In the A-10C II, changes made to a weapon's profile from the DSMS->Select Station->PROF page (and saved) are not persisted. If the same changes are made from the DSMS->Select Weapon->VIEW PRO path, the changes are persisted. I believe this behavior may be leading to reports of autolase working inconsistently as, if the player's changes aren't saved the airframe doesn't know it should be autolasing. i7-8700K, 32GB RAM, 2TB SSD Windows 10 Pro 10.0.1.19042 DCS 2.7.6.12852 Thank you!
-
This potential bug relates to navigating to pages on the a10c2 Tank killer CDU. Summary: Pressing STEERPOINT on the WP Menu takes me to the WAYPT Page instead of to the STRINFO page. Steps to Reproduce: 1.Press "WP" on CDU. 2.On WP MENU, press either WAYPOINT or STEERPOINT soft keys (top right or top left respectively). 3.Note how in either case it navigates to WAYPT page. 1b. Now on UFC, press Func 2b. Press 0 (Steer) 3b. Note how the CDU now navigates to the STRINFO page. Thoughts: Is this intended behavior or should STEERPOINT soft key navigate to STRINFO when pressed on the WP MENU? This behavior can also be produced using the CDU display on the right MFD. And by using UFC Func, then 3 (WP) to navigate to the WP MENU.
-
The off road performance of the F-18/16 is just pure fantasy. These fighters were never intended for any soft field ops. Common sense applies here. No U.S. fighter should be able to go at 300 knots off road, simply because they were not designed for it. (duh) This is a somewhat annoying issue since now it is totally possible to troll people in multiplayer by landing on a mountain for example and taking off behind an enemy hornet off road.mp4 Meanwhile the aircraft that did have soft field capabilities (MiG-29, SU-25) are completely useless on soft fields since the steering always breaks and the structure collapses on some random bumps. But that is a topic for another ticket. Hornet off road.trk
-
correct me if im wrong but this is a bug right?
-
Hi all! While flying at night and with the instrument's backlight I noticed that on the left side of the course (CRS) switch on the UFC there is a "+"; when the switch is moved to the left, the course degrees are reduced and not increased... I don't know how it's supposed to work but I thought I would drop a message here just in case...
-
Hello everyone, I am sure many players have been most pleased with the addition of a substantial depth to our beloved F-16 Electronic Warfare capabilities, opening up a new field to explore. This post is intended to seek some extra details and clear up some confusion about the ALQ-184 ECM pod, namely it's effect on the onboard sensors. Let us begin. As we have been informed by Matt Wagner's recent videos and Mini Updates, the ALQ-184 has 2 main modes of transmission: Self Protection Jammer (SPJ) mode Barrage Noise Jammer mode One of Wags' videos explains what they mean, SPJ mode attempting to break a radar lock on the aircraft, and Noise Jammer mode denies radar range information from hostiles. In terms of the ECM's interference with the onboard sensors such as the FCR, HTS and HARM, the 184 seems to have another 2 modes of operation, as explained by Matt: Radar Priority mode ECM Priority mode To explain how these modes work, here is a quote from one of Wags' Mini Updates: When in ECM Priority, the FCR and HARM/HTS are silenced; When in Radar Priority and the jammer is transmitting and ownship radar and HARM/HTS performance is reduced by 40%. Currently in DCS it seems that the Noise Jammer mode, in Position 3 on the ECM panel, functions in ECM Priority, turning off the FCR. The other SPJ mode can function in both Radar Priority or ECM Priority, using switches 1 and 2 respectively. The interesting behaviour arises when selecting Position 3 Noise Jammer, beginning transmission, then switching to Position 1, which now allows the FCR to operate. Position 1 seems to now work as the Radar Priority mode toggle instead of enabling the SPJ mode, when ECM is still transmitting in Noise Jammer mode. I am uncertain if this is correct behaviour. On one hand it would make sense to have the Position switches be multi purpose, and make them double as toggling the Radar Priority mode when transmitting Noise, as there is no Position 4 to enable Radar Priority in Noise Jammer mode. I also have my concerns that the Noise Jammer mode should function in Radar Priority in the first place, it being in ECM Priority and disabling the FCR, HTS and HARM is not mentioned anywhere by Wags, quite the contrary, he has told us that Barrage Noise Jammer mode is intended to be turned on, and left on as a preemptive measure, which would be unwise to do if it would turn off all the sensors, as it does in DCS. As a summary, the main question is: is it correct that switching from Position 3 to Position 1, while ECM still transmits in Noise Mode, enables the FCR to function? I am aware that things may still be work in progress, this post is intended to clarify some details about the workings of the ALQ-184, as it is a complex system that I am sure required a lot of development time. Best of luck with the module moving forwards, and happy holidays! ECM.trk
-
OB 2.7.9.17830 SP Persian Gulf F-5E-3 with AI wingman Take-off from Shiraz #-key works on ground to trigger the comms menu, menu is working NWS button on joystick in flight does not trigger the comms menu (despite seeing the button pressed on the cockpit-stick). F-5E-3_with_AI_wingman_NWS_not_triggering_COMMS_menu_in_flight.trk -
Using JDAMS and Tpod, Waypoint Designate, the Tpod slews over target OK in test mission (not in multiplayer). Test mission in Multiplayer and the Tpod slews but is way off the target. So I need to undesignate and slew manually. Is there a problem with the Tpod in multiplayer? -
I've been experiencing some pitch instability with the Hornet, and it seems like it might be worse at higher altitudes like 15k and higher. It'll pitch up a little, then a few seconds later it'll pitch down some. Is it something I've set wrong in the aircraft configuration? A problem with my joystick? Thanks, Dave
-
When in the editor selecting start from runway they start from parking hot. This happens in multiplayer only. To be clear, when you start the mission by your self they behave as expected, here taking off from runway. However, start that same mission file as a multiplayer session they start from a parking spot hot and taxi to the runway. Why is this an issue? If you have placed units on the ground at various parkings to liven up the airfield they potentially spawn into blocked parkings by stationary parked aircraft. Hope so see this issue resolved.
-
Hi all! Just found out the following: 1) set air radar on the right DDI (I haven't tried this on the left DDI) 2) press OSB 7 SIL to put the air radar in SILENT mode (SIL should be boxed) 3) press the Sensor Control Switch (SCS) towards the right DDI (where the air radar is displayed) 4) the air radar exits SIL mode but "SIL" on OSB 7 is not displayed anymore 5) if switching to surface radar and back to air radar, "SIL" comes back Questions/notes: 1) is the air radar supposed to get out of SIL mode when the SCS is pressed in the direction of the DDI? 2) the surface radar does not get out of SIL mode if the SCS is pressed towards it Request: 1) would it be possible to enlarge the TDC area of selection for "SIL"? It always takes me a few hits to enable it with the TDC (I always seem to miss the "soft spot") Thank you!
-
That's not as intended, is it? (clip starts at 2:04)
-
Previously no issues using Harms with F16 Today tried Harms and wanted to use POS/EOM. With mixed load of AGM88 and GBU31 the Harm displays would not show any target info on weapon page. Harms powered on and Master Arm on. HUD cues for target looked fine but nothing on HAS or POS and Harm would not fire. Tried again with just Harms, First target all worked fine and destroyed SA6 site. Went to next SP and this time same problems no info on WPN page and no launch in any mode. Is someone able to replicate this? Thanks
