Jump to content

musolo

Members
  • Posts

    475
  • Joined

  • Last visited

Posts posted by musolo

  1. @dundun92  Made my day lol. Enlighten us poor red peasants please how close to AWACS  should it become visible? And how often? Every time in met conditions or every other time or less?)  You crearly know exact ranges and conditions better than ED team could ever guess))).  I`m all ears man. Dazzle me 😂

  2. 2 hours ago, Breakshot said:

    We have noticed this for a long time, seems like its some kind of notch-gate effect from the AWACS, but yeah should not be happening like that.

    More so contacts do not appear on datalink wnen are fed to F10 page by this same AWACS in Fog Of War mode.

    Another bug is that Aim-54 is not being shown on the data link most of the times when  shot from Tomcat at allmost same range from AWACS and same ange(aspect), altitute and speed of the Tomcat at the moment of the launch do not differ to any significant margins. Yet more than half of the times missile is not shown on the Datalink. Just to let you guys know about this bug too when you will be fixing Datalink. I can make another bug report with attached track if needed.

  3. There is a bug where contacts that are in direct visibility and are not obscured by terrain from AWACS do not appear at all on datalink (while being called out by this very AWACS) Also contacts that are visible at some point in time dissapear from DL for no reason ( same altitude, speed and direction and in direct AWACS visibility moment after dissapearing from DL screen. And well within detection range and parameters) To reappear random time after that(few dozens of seconds to few minutes) when at the moment of  subsequent appearance its detection parameters are already deteriorated. That goes for both friendlies and bandits.  

    Happens on Su-27,Su-33,J-11A.

    FlankersDatalinkBug

    • Like 1
    • Thanks 1
  4. Hi guys! Wonder what is the difference between J-11A RKL-609 ECM Pod and Su-27 L005 ECM pod? Googling it didn`t help. Are their jamming differences if there are any modeled in DCS at all?

    Are there any advantages ? Or its just different 3d model and name. 

  5. 5 hours ago, Cmptohocah said:

    Does this pass the "cheat" test in MP?

    Yes that`s the beauty of this upgrade. It is just a skin. No code is involed. Texture that turns stock Flanker`s  Datalink into much more informative device. Its like turning a spyglass into a sniper scope with all reticles, mil dots helper markings etc.) Attempt to get closer to picture on modern Flankers MFDs. That is as close as you can get to them SA wise.  You can fly with this cockpit skin on any server that allows custom textures. But there is only one server that makes most out of stock Flankers in bringing them as close as possible to their modern latest versions. Server name is EXERCISE RED FLAG. Su-33 is brought up to T-10M/11 russian Flanker and J-15 Chinese Flanker versions by automatically rearming them with missiles those versions can carry.

    So there are 2 modern verions of that airframe you can fly there. Same goes for base Su-27(T-10) version. It has Chinese J-11B and Russian T-10BM reincarnations present on the server.

    You don`t need any mods to fly them there. Server is IC protected. You connect with your clean client, occupy desired slot and your jet is turned into a modernized beast)

    Server equips all slots with latest and srongest loadouts comprised of missiles that vanilla DCS has to offer. 
    And those loadouts upgrades combined with this datalink upgrade will give you unique experience in DCS withought need of any mods whatsoever)
    Su-37.jpg

     

    T10M11r33_2.jpg

    This is T-10M/11 (Su-35) that i`m flying there). R-33 is a substitude for R-37, R-77 is a substitude for R-77-1.  But man is this DIY Su-35 a damn

     beast))). R-33 does the job atacking targets up to 90km away. R-27ET gets the ones that got through to 45km distance. And R-77 takes care of the rest that  somehow managed to get closer than 25km.  

     

     

    • Thanks 1
  6. I get it when they turn blind eye  for less vital things. But there is nothing that compares to this TTI line importance in BVR fight. Direct misrepresentation of combat potential of last generation of Soviet  fighter jets is what we have here.  And its fixable, its doable. i`ve been told by @Chizh  in Russian branch of the forum about missing tone from heat seeking missiles on Flankrums that -" it`s not  that crucial"  and "that they will implement it when they will do clickable versions". Ok. If you say so). But what about this TTI indication? There is nothing more crucial than this line that Flankrums have been deprived of. 

    Would you be so kind man and finally  tell us what`s up this that feauture? Will it be implemented for FC3 soviet fighters or not? You `ve told me that docks will have the final say in such requests. And tone thing wasn`t that important. Well this time it is the MOST important thing out there. And you`ve been presented with docs as you demanded for such inquiries. 

    So what`s its gonna be? 

     

  7. 4 hours ago, Schmidtfire said:

    While it would be nice to have the full symbology, missing TTI is to be expected from FC3. What about the incorrect OLS-27 symbology or the arcade-modeled Schchel-3UM Helmet Mounted Sight?

    It would be nice if ED went back and remastered the FC3 series. Added and corrected HUD symbology... making parts of the cockpits clickable with all switches and buttons animated.

    Sort of a step between Full Fidelity and what we have now in FC3. 

     

    You`re digressing man) all those things you say are nice and all, but this TTI thing that "Flankrums" are missing is one main thing that would make them know for sure when is the right time to brake lock when usung Fox2. Thus no to commit extra seconds to target and getting splashed coz of that. This indication alone is a BIGGEST factor in combat efficiency and survivability for  those "Flankrums". Not to mention Fox3 missile that makes this TTI line  flashing when missile goes active. Hope it is clear now why absence of this TTI indication line on the HUD  is the most grave hinder for soviet gen4 pilots in Air to Air combat. Hence they are significantly impaired due to this ridiculous "feauture complete" nonsence. Аnd this begs the question - Was that initial  intent or trivial negligence? 

  8. 18 hours ago, Snappy said:

    Ok, I think it  had been pointed out , even by 9line or BigNewy( can't rememember which) that even if a user hands them the necessary documents for certain aspects of simulation, that does not mean they can legally use it

    In this case they can man) It`s Su-27SK declassified document we are talking about here that contains this info. Check the first page of this thread, there is a link to a digitalized PDF version. You can copy text and google translate it.

  9. 18 hours ago, SFJackBauer said:

    Wait what?

    i`m not talking about the way to calculate distance with screen space obvoiusly) I was answering question about adjusting line length to a different screen resolutions(which are only few cases anyway) So you can make initial length of this line to be displayed on HUD and go alone well with any from given resolutions of the screen full HD, 4K etc. Read it again slowly)

    My main point however was that it can be done without disrupting existing code for the plane(if thats the reason preventing them from doing this). By adding extra script that would do the thing you said by itself by reading needed closure parameters between  missile and  target locked by player`s jet radar in STT mode. Call it FlankrumTTI manager if you will) 

  10. 2 hours ago, GGTharos said:

    Sorry but that's silly.   They have been very clear about the state of FC3 vs. DCS FF level modules.

    What exactly do you find silly? That they are very clear about the feauture complete state of feauture incomplete product? That members of the forum are being told by ED representatives counless times that documentation is the one and only deciding factor feauture implementation wise? And when being presented with these docs and asked to implement not all but just a couple of feautures that are vital for combat survival of jet just ignoring them?) imagine yourself in their shues and ask yourself how silly you`d look in that case.

     

  11. 2 hours ago, draconus said:

    All measure values have to be relative, not pure pixel values, otherwise you'll have twice the TTI value on 4k over 1080p. That was my point.

    That`s where screen space parameters come in. There are ways man) I suggested approach. A draft algorithm implementations of which are slightly vary due to specifics of any given game engine. But overall approach is preferable in case you don`t want to reorganize airplane`s existing code base. You just hook to some of the public events? params etc. and use those as anchor points for your UI 'slider". It`s similar nature to that of  a health bar in other games if you want me to over generalize the nature of this matter.

  12. 2 hours ago, draconus said:

    it can't be based on pixels, LOL

    It`s based on range between players plane or pylon or missile and target plane at the moment of the launch. And after that this value is converted into percentage and interpolated into amount of pixels of the horizontal TTI line. Than as  percentage of the launch distance is decreasing so does the percentage of the line length (which comes to amount of the pixels along X axis)
    Read carefully what is written in the post and several posts behind. Look at the pictures given in the topic before LOLing. Otherwise you`ll look silly as you do now.
    And Eagle`s TTI scale operates pixels too, though implementation that leads to that  might be different. Its a UI thing in ALL games. I`m in gamedev for 10 years now. Trust me)

  13. And we are not talking about some minor missing stuff here. TTI indicator is a most vital thing in the bvr engagement for Flankers and Fulcrums. Nobody saying ED has to mimic all subsistems and inner workings involved in this TTI indicator line functionality.

    Just take the ray cast value between player`s missile  and its locked target at the moment of the launch then store and convert it as 100% of the horizontal TTI line length(100 pixels for example), then feed the closing range number between missile on its way to target and interpolate this reducing value percentage to the percentage of the length of this  line on the HUD. That way it will work for every missile on the list. Simple solution to this  issue. It does not have to be coded inside Flanker or Fulcrum main chunk of code. It can be done separately and slapped on the HUD as a patch independent from previously constructed code base. And will not depend on jets code) One extra lua script that will take care of this issue

    @Chizh @uboats This approach shoud do the trick guys. Please at least try it. 

     

  14. Eagle`s vertical scan is not  working properly allmost every other time. Combat feauture that is to be the most reliable among all other F-15 radar mods. That said Soviet Flankers And Fulcrums are the only Russian jets available in DCS whereas bluefor has 3 very potent clickable jets that are constantly improved. 

  15. 2 hours ago, Cmptohocah said:

    This is all fine I guess, but I don't want anyone to ever call me out as an conspiracy theory advocate when I say that ED is neglecting red side (not technically only red 'cause of FC3, but in practise yes)

    Given that i`ve been told by Chizh that they need documental evidence to proceed on a any given issue this looks like its not too far fetched conclusion. 

×
×
  • Create New...