跳转到帖子

nickos86

Members
  • 帖子数

    374
  • 注册日期

  • 上次访问

最新回复 发布由 nickos86

  1. 5 hours ago, Raven (Elysian Angel) said:

    Yes the current implementation is brilliant, just like in the Mirage F1 and new MiG-29, unlike the (better than nothing but fake) effects other modules with visors use (Mirage 2000, F-15E, MiG-21, OH-58). It’s what the community has been asking for for the last 7 years 🙏

    Why argue?! Just read the topic name. I've asked for the option for the user to decide on his own... I didn't ask to completely remove the current implementation.

    For some the current implementation in VR makes the flight very unpleasant. Nothing to do with real life or whatever. PC and VR got limitations.

    • Like 2
  2. Like IRL, a unit that when placed somewhere on the map will form a temporary landing strip (including night landing lights). The C130 may find itself landing somewhere in the middle of nowhere to support special operations.

    • Like 9
    • Thanks 1
  3. On 5/14/2025 at 5:43 PM, ChillNG said:

    It's a core DCS issue, nothing that can be amended at my end.  All DLs are set up correctly and turned on, sometimes it just takes a while for the AI to appear.  They usually do eventually though.

    Do you "restart" the AI aircraft (I guess to refill his fuel tanks)?  Because the AI don't initially appear on the DL but they do reappear later... If you're doing something like that to manage their fuel- can you do it 5 min after mission start to overcome the DL issue (5 min should be more than enough to complete startup and stored heading alignment)  

  4. I think it was already requested in the past. I think it's super useful and important. Moreover, it's a low hanging fruit. It will be so easy to implement (ATIS in kneeboard or via F10).

    Problem is, that generally speaking - ED tend to over complicate solutions for relatively simple problems. I bet it will be part of their new ATC system... But till then - they won't do an "ok" solution (while people don't even need more than "ok"). 

    I hope I'm wrong... and ED will implement an ATIS brief (AI generated voice as it is IRL for AWOS and in ATIS at some airports... Or even just a written note). Same for METAR (that doesn't really change anyways at the moment... But of course can update... etc.

    • Like 1
  5. 2 hours ago, MAXsenna said:

    Just bring the volume down, unless something changed.

    Sent from my SM-A536B using Tapatalk
     

    At the bottom of the scale, before going OFF - you can still hear the morse sound. Usually this kind of hardware will have an On/Off detent at the edge, then a range based on the potentiometer to control the volume. I guess that if ED simulated the knob as a virtual axis then instead of going -1 (off)-->0(on)-100(max) it goes from 0(off) to 100(max)... So there is no "0" - the system works but the volume is muted (or it is implemented is way that is too sensitive for using with mouse clicks...)

    Not a super big deal... but the ILS sound is annoying when doing a full ILS approach. It seems to be a very quick and simple fix. 

     

    • Like 1
  6. 12 minutes ago, BIGNEWY said:

    Hi, no plans to be able to change existing route, but we may see the ability to share created routes in the future. 

    thank you 

    Thanks for the quick answer! One more - will there be an option to add "Navigation target points"? 

    • Like 1
  7. @BIGNEWY, are there plans to expand the "route tool"? At the moment it doesn't interact with the route the plane already got. It would be great to be able to edit it. Moreover, it's relatively uncomfortable to share the route to other players in your flight... Can you elaborate on the future plans for it?

    • Like 1
  8. 2 hours ago, rayon89 said:

    Whenever you want, we'll meet on a server and you can show me your skills. Maybe the problem was wanting to make a missile to be able to play PvP and be on an equal footing with the Russians, why I highly doubt that a 120c missile behaves like that in reality.

    I highly recommend you to watch some of growling videos on BVR (like the one I'll attach below). He's doing a really good job explaining how the tactics matter A LOT. 

    You can also look for the discord and youtube videos of the TACT - you'll see how when someone experienced flying against someone less experienced - he manage to shoot him down even at 25NM+.

    Don't take this personally 🙂 The implementation on the 120C of course never going to be 1:1 as the real deal... The real guidance algorithms are classified and the exact characteristics of the internal radar and electronics are classified... But per the assumption ED published in their newsletters - they took a realistic approach... So good chances the current implementation not that far from the real thing.  

    Regarding your tacview, you were very slow when shooting the missile (~1.01M) for 25NM... Try accelerating to at least 1.3M-1.5M and shoot with a 20-30 deg of LOFT. Put him on the gimbel after firing and support the missile until pitbull. 

     

     

  9. 17 hours ago, rayon89 said:

    You can try it yourself, shoot a 120C with the F18, give mile 15 to an F5E, see how many kills you get, even having everything in your favor, the missile is always lost, in addition, the fight outside visual range no longer exists. why at those distances it is better to use other types of missiles, why combat outside visual range no longer exists in this game

    Hi, please note that BVR is a VERY TRICKY game. Against a really good opponent - it will be VERY hard for you to shoot him down even at 6-8 miles because he knows how to defend (energy, not flying straight at you, etc.). The BVR game require A LOT of knowledge and experience. No offence but the problem is not the missile but it's you  🙂

    I strongly suggest going to servers like growling sidewinder, getting killed MANY times, exploring the TACVIEW and learning. You'll see guys hitting each other from 20+ NM and in other cases people dodging 120C from 7 NM... All a matter of proficiency. 

    The 120C ain't a 'magic' weapon that will hit it's target from 30NM no matter what. I think you'll find it's super interesting to learn how to employ it properly and fight a good BVR fight...

    Just a small video showing how you can kill from ~18NM and at the same time - dodge the missile from your enemy  

     

  10. Note, there is not digital ALT map correlated to the RDR for the 15E. If you designate a target while the waypoint you fly to (via UFC) or picked up in the RDR is far from the designation - you'll get a large ALT error because the plane will try to interpolate the ALT.

     

    • Like 1
  11. In general DCS got quite a gap in all related to ground unit damage modeling and the effects caused by a weapon onto a specific unit. 

    Just as you've pointed out, IRL you won't see a "DCS style" explosion when a charge hits a unit. It's not a GBU12 🙂

    The "explosion effect" simply showed when the unit get destructed. You can argue that currently the damage effect and units damage models not modeled well... I'll be the first to agree with that. 

    • Like 2
  12. 20 hours ago, Hobel said:

    Is the same principle.  The tgp caused strong "drifts" before the update and with the GBU38 it could be reproduced best. 

    So it should have been:

    "Fixed: TGP+GPS guided weapons = 15-20m Miss. Note: 3 Second laser or AGR required before release for increased accuracy."

    There should be nothing special about the GBU-38 in comparison to the rest of the GPS weapons. 

     

  13. Hi,

    The increased accuracy followed by 3sec of lasing or AGR - is it a weapon thing? Is it relevant to all modules? 

    Or is it a platform thing? In this case, what mechanism was flawed and now is modeled correctly? ED, could you please share some info regarding this fix? 

    Thanks.  

    • Fixed: TGP+GBU38 = 15-20m Miss. Note: 3 Second laser or AGR required before release for increased accuracy.
    • Like 1
  14. An interesting feature. If you designate a target via the RDR while the waypoint selected in the UFC is in the target area, the TPOD cues automatically to the designation and the elevation is quite close to the actual one (comparing to the F10 map). If you des a target via the RDR while the waypoint selected in the UFC is FAR from the target area- the delta between the RDR des and a TPOD will drastically vary.

    Attached two pictures. The target area is at waypoint 2. The target coordinated from the F10 map are: N 30°21.066'   E 34°50.382' and alt of 1385ft

    For the first picture ,I've entered waypoint 2.A into the UFC and designated a TGT . The coordinates are very accurate. Same for elevation - 1380 vs 1385 ft.

    As for the second picture, I've entered waypoint 1A to the UFC and designated the target. Note that now the elev is 1900 ft!

    Something to consider and take into account when designating targets using the radar.

     

    image.jpeg

    image.jpeg

    WPN1.jpg

    After seeing the following thread:

    KlarSnow important input: "The Air to ground radar pulls the elevation from the steerpoint you have input at PB 17 in the upper right of the radar display. If you do not have a steerpoint up there, it pulls from the closest steerpoint. This is why your targetting pod is pointing in the air. It has no way to generate elevation off of an HRM map, only coordinates." 

    So it's a good habit to set the steerpoint closest to target into PB17. But, seems like the "if you don't have a steerpoint up there, it pulls from the closest steerpoint" - doesn't work as intended. Rather, it pull data from the waypoint set in the UFC.

    • Like 1
×
×
  • 创建新的...