Jump to content

falcon_120

Members
  • Posts

    2271
  • Joined

  • Last visited

Posts posted by falcon_120


  1. Hi, not a native english speaker ... looked up cosplay on a dictionary and couldn’t understand its meaning on a DCS context ... can you please clarify?
    He means "fictionary" weapon, as not really used for those variants or countries that operated those versions, but maybe employed on similar variants of other countries...

    Enviado desde mi ELE-L29 mediante Tapatalk

  2. Mission: F18 AIM 120 Amraam (Base game mission)

     

    Behavior: Target locked on stt, Amraam on pitbull goes for totally different target (original target is turning to my right, while the target the AIM120 decides to engage is flying straight and slightly to the left. This happens on the second launch approx 1.30 min after track starts.

     

    Expected behaviour (could be totally wrong): Since the Aim120 is being supportef in STT all the way (and maintained prior and after TTA), and given differences in target  aspects, the AIM120 should have an easy time discerning between those targets based on velocity gates and target aspect. This is considering this has been implemented in the last patch as advertised.

     

    Please review to see if its normal behavior or maybe any of the parameters used to discern targets is not working as expected.

     

    EDIT: Attached second track, this time happens on the first launch.

    Amraam bug.trk

    Amraam bug 2.trk

    • Like 3
  3. For certain missiong I see a very prominent lines and artifacts on clouds, specially on borders or when the layer is very thin. 

    Attached Picture.

    image.png

    Mission: F18 AIM120 AMRAAM Mission (base mission included)

    Attached track.

    Other relevant info:

    -1080ti, NVIDIA driver 496.13, clean installation, and recently repared and cleaned additional files.

    image.png

    Clouds bug.trk

  4. 5 hours ago, InitiatedAunt74 said:

    I own the A10C but decided to try the Flaming Cliffs trial, and that has the A10A module in it.  It installed, and it flies, but nothing in the cockpit is clickable.  The mouse cursor appears normally when you LAlt+C, and the mouse cursor stays yellow and never changes to indicate that something is mouse over and can be interacted with. This does not happen in the A10C, only the A10A.  I see other forum posts about various planes/modules doing this in DCS apparently it's a DCS bug that's been lurking for years.

    DCS 2.7.6.13436, Win10

     

    Not a bug. Its a product design decision. 

     

    The short history background is that FC3 modules date from 2005ish  IIRC when full fidelity modules were not a regular thing. I say regular because at that time there was a full fidelity module; the KA50, and shortly next it came the A10C. But that was it. Nowadays is almost impossible to think of a non clickable module other than a mod. Lets see what happens with MAC, announced many times but totally silent for some months/1 year.... But MAC is like a stadnalone FC4 geared towards a different audience.

    • Like 1
  5. I wonder if A2G radar technology used for the F16 is exactly the same as on the hornet, or if improvements have been made along the way.

    Just saw the video and I got the impression that Exp resolution on the airfiled was incredible; clearly discerning aircrafts and surrondings, have not been able to get so good resolution with the APG73 radar of the hornet in DCS. It could be just my memory playing tricks on me ofc. I'm looking forward to receiving the new A2G mode for the viper in the upcoming patch, that way we will be able to compare apples with apples.

    • Like 1
  6. 7 hours ago, C3PO said:

    Hi - I recently interviewed Matt for PC Pilot magazine and we talk about Vulkan, multi core development and other stuff extensively. Details of when the article is out will be released very soon. Oh, there’s another fantastic feature - under development - discussed in the article.

     

    Make sure to leave here the link when is out please. Looking forward to it.

    • Like 1
  7. 1 hour ago, Coole28 said:

    Wait, are SA-15s supposed to be able to shoot down LD-10s now?  I’ve taken down at least a dozen this last week and none of them even attempted a shoot down.  Only thing that ever gets engaged by SAMs for me are 802s and LS-6s.  SA-19s will engage GB-6s with guns only.

    Basically in DCS now both AGM88 and LD10 are shot down by modern sams (like SA15 and SA10). However from my testings I can see that they are only attacked when their speed drop to some extent (I dont know the threshold). 

     

    So for example, if you attack an SA15 from just outside its max range or just when he start shooting at you, the system will not be able to take out your ARM. Same with SA10 or SA11 if you make a pop up attack from close enough. 

     

    I don't know if that makes total sense, other than a very fast missile gives no more than 6-10 seconds response time, while when launched from further away it will provide up to a minute and a half of preparing time for the site to defend.

     

    The missing piece of the puzzle are bombs, which are still totally invisible to SAMs, so a JSOW is taken out easily by a SA11 while a GBU38 is a secured hit (if coordinates are ok ofc)

  8. You answered the question yourself. Why they no longer say a thing about future projects but until it's already to be released few days later?

    People expectations are too high for whatever reason it is, people get too nervous about next projects/release dates, people want things right now or the day before, but software development to the highest level as DCS is takes time, a lot of time. It's not Tetris they are coding, hence so many times it takes many more time that anybody can foresee and people expect miracles in the form of ridiculously short development times. Better not to say a thing and it's fixed, that way when they release anything new be it modules, features, whatever people get hyped in the right time but not before, specially too much before.
     
    S!
    I do not agree. Obviously there has to be a sweet spot between silent and telling too much, which is no good, but in general, the way you keep clients engaged and involved is by treating them as investors or important stakeholders, letting them know when important milestones are postponed or delayed.

    A perfect Customer management in this case is something like: (August 2021)"Guys we know we estimated a Q3 vulkan realease, we were really going for it, however current progress and complexity of the task, as well as some other very expected items has made us rethink the roadmap, we are aiming at Q3 2022 with confidence..."

    That's it, no more questions until next july/August...

    Enviado desde mi ELE-L29 mediante Tapatalk

    • Like 1
  9. 5 hours ago, Tavo89 said:

    I was hoping this EF would be based on a specific variant, I will await its release and its evaluation by someone with knowledge, who can tell whether or not it looks like the real plane.

     

    I know what you mean, but I don't think that has existed in any of the consortium AFs. Take of them at any moment in time and you will have at least 2 tranches and different software versions (which is not minor as some of those totally change their weapons and capacities...)

  10. I think it's time for ED to do something, it is in fact a problem at a lot of daytime hours/settings. It's not cool, even if I were to hear it's "realistic", I don't know why can't we have an option for "unrealistic" yet visible mfds, in the same manner we have option for jhmcs in both eyes


    PS. I know it might sound like a rant, but that was not my intentions. I just really think that is a quality of life feature that would be incredibly welcome all around, and that has been requested for very long. Hopefully something is in the pipeline...


    Enviado desde mi ELE-L29 mediante Tapatalk



  11. After the F16 radar has been worked on, results will be a bit better. There are from my PoV 2 major things going against the F18 and favouring the F16:

    1. Detection range of the F16 is wrong, after the rework an F18 vs F16 should see each other at a similar distance, with a little advantage if any for the hornet pilot
    2. Currently the F16 radar in DCS does not suffer any degradation caused by jammers. It should be the case that in the future, the reduced detection range of the F16 gets a bit more exacerbated by the use of jamming by the hornet.

    With those 2 points in mind, you are basically degrading really long +40nm amramm shots in the viper, to around 25nm ish while giving yourself a bit of room for a first shot.

     

    As a side note, hopefully with an increase in radar range of the F15 after the patch, this plane would regain his throne as the best BVR fighter in DCS only hindered by the lack of Link16 and JHMCS.

    • Like 2
  12. Guys, you are missing the point GGTharos was making before. Manpads are really, really dangerous against ANY fighter, even a high performant one. This is due to a compilation of several reasons:

     

    • They are really difficult to spot, in fact they could be launched just after you overfly one, so they can be virtually invisible to the receiver, requiring wingman visual support.
    • They are shot from very close range/altitude and they are FAST (
      ). You cannot make a proper missile defense, as normally you are just 2 seconds away from an impact. 
    • At those altitude, normally you may not be as fast as you would like to, or you just made a gun or bomb run and you maybe low of speed.
    • Modern Manpads have very good CM resistance.

    So, can you evade a manpads by a coordinated maneuver? Well...Yes, you can perfectly do it in DCS, you just need to be aware of where it is, be prepared, and have enough speed to orthonal roll or split-S the missile, which is normally the best methods. But in reality, both IRL and also totally applicable to DCS you should consider the following:

    • You just dont enter a manpad WEZ...ever.
    • If there are manpads in the area, Gun or bomb runs are made at 14.000-16.000 feets, not lower, and always with preventive flares and no AB
    • If you enter is only because you don't know it was there and because is just part of your low alt ingressing route (imagine a Viggen, tornado, F111...), in which case you should be going really fast giving you evading options
    • You always hit a target and replan a new attack, you just don't get flying around, slow and low in a manpads infected area, its a recipe for disaster.
    • Like 3
  13. On 9/9/2021 at 2:09 PM, bertOC said:

     

    I can't agree with this, when i'm in the front seat using the sight myself, i can clearly classify infantry and make out MANPADS quite easy.

    Well, In DCS they stand stupidly still with the manpads even after firing it (even when they can't reload anymore). Also you have superzoom.

     

    In RL, a person with a manpad can look like a civilian or even a sheperd with his flock, and 5 secons later, just when you take your eyes off him, he/she take the manpadas hidden under a blanket of behind one of his sheep and shoots you in the face. So as a compromise with RL, I would always treat any soldier as a potential manpad carrier until better animations and IA of enemy infantry is achieved some years from now.

     

    For me the better improvement would be for manpads soldier to not stay still, dropping the manpads after shooting, take cover, take his weapon... basically behave like a real soldier....

    • Like 1
×
×
  • Create New...