Jump to content

CHRISXTR3M3

Members
  • Posts

    471
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by CHRISXTR3M3

  1. As I’m sure all of you are aware, there is a major discrepancy between ED modeled missiles and your own. I for one a very happy with what you guys have done with the SD-10 and was hoping that it would inspire much needed changes in ED’s missiles. Though it has inspired change I’m not sure if it will be enough. I know I am just the middle man here but if you could provide some much needed data to back up your modeling it would go a long way. If you have already then my apologies for this message but if you have not, why? It would clear up so much controversy and would set the benchmark for ED to shoot for.

     

     

     

     

    The ONLY reason ED changed the flight model on the AIM-120 is because of all the people who were crying about the SD-10 actually challenging SPAMRAAMERS. It's hilariously and disgusting at the same time due to ED stating they realize their missile codes are off and were giving the code a revamp....BUT THEY ONLY REVAMPED THE AIM120. Why not revamp the R77, 27-ET, 27-ER, etc?

     

     

    Because since christmas 2019 was arriving ED was probably fearful that no one was is going to buy ED produced hornet and falcon modules during their winter sale unless they buffed the aim-120

  2. Correct. The main issue is TOF of the weapon vs the reaction time of the defense system. In the case of glide weapons their TOF is basically forever compared to missiles/bombs. The JSOW program understood this, and tried to make the munition "stealthy" to make it harder to engage by those systems since by having a reduced RCS the detection range would be shorter (how this is actually modeled in DCS IDK). The GB-6 is "stealthish" like the JSOW, however the LS-6 is more or less a bomb with wings, and should have a much larger RCS, so if any munition is engage it should be the LS-6.

     

     

     

     

    I don't understand what the argument truly is in this thread...BUT, I do bring forth that I have witnessed Roland sites and hawk sites taking out both my JSOW and LS-6. So the sams are capable of defending themselves from these weapons.

  3. my fellow Jeff Squadmates...please, this is exactly what those ****ers on bluefor want...they want to divide us. We are already few in number...so lets get along shall we?

     

     

    Now as for that AAR, I am looking forward to it and I too want HMD pretty plz.

     

     

    BUT, not before the RWR and MAWS gets fixed

  4. Talking about range & speed for any A2A missile with no launch/target condition is just nonsense.

     

    U can get a AIM-120 kill over 30NM if U like, what U need is just a "correct" initial condition.

     

     

    I love it. I effing love it.

     

     

     

    Sadly, blue is just here to complain. Here's a thought for those flying against the JF-17....:helpsmilie:YOU ARE TOO USED TO BEING ABLE TO LAUNCH A SPAMRAAM AND CONTINUE PRESSING BECAUSE YOU'VE ONLY HAD TO FACE THE VERY BADLY RANGED AND FLIGHT MODEL OF THE 27ER AND R77.:megalol:

     

     

     

    So now that you have a fighter that is capable of sending a competitive AAMRAM you are stuck in your ways of pressing after launching your 2, 4, or 6 spams. Learn tactics. If you have FC3 I highly suggest becoming versed in the Mig-29 and Su-27/33. Only then will you understand how to truly go into combat against an AAMRAM

     

     

    And don't take this in a negative light OP.

     

     

     

    I seriously highly suggest you learn the tactics we have been employing as flanker pilots and are now employing them in the JF-17 with much effect (obviously).

     

     

    :pilotfly:

  5. Soooo...

     

    Online, blueflag Persian gulf. Issues witnessed/reported by many people.

     

    RWR not working online.... Generally speaking...

     

    Betty does call tracking and missile. MAWS shows at least some missiles in rear aspect. (personal exp)

     

    No Nails from any target, "tracking" doesn't show any targets but betty reports tracking... (personal exp)

     

    Rumor: Possibly the RWR is showing targets that spawn AFTER the JF17 spawns (so new enemy players, but never SAMS)

     

    Moreover IFF doesn't seem to working. Lots of buddy kills. (personal exp)

    Data link is sort-of working, it does show friendly's but other friendly's showing as unk/hostile (f16 that I buddy killed for example) Definitely showed "yellow" (personal exp)

     

    SRS not working for the JF-17 (not sure that's Deka's problem).

     

    As mentioned, WPT, PP, RP not working online (personal xp)

     

    Countermeasures didn't deploy (personal xp)

     

    Hotfix plz.

     

    sorry no trackfile. It would be too huge to upload anyway.

     

     

     

     

    So, here's how I got my stuff to work....and i had all the issues you listed. I uninstalled the JF-17 Module. Ran DCS Clean-up tool. Ran DCS Repair Tool. Reinstalled JF-17 Module. And rebound all my hotas keybindings from scratch.

     

     

    Problems solved

  6. First of all, Deka you guys are amazing. Thank you for working so hard and fast to repairing as many bugs as possible within the first week of launch.

     

     

    Secondly, I want Deka and all people posting bug reports(including myself) to consider the following:

     

     

    IT APPEARS MOST OF THE BUGS BEING REPORTED AFTER THIS LATEST UPDATE COINCIDE WITH MP SERVERS/MISSIONS THAT HAVE NOT BEEN UPDATED TO LATEST UPDATE OF DCS WORLD.

     

     

    My friends and I have been trying to replicate the following bugs on different servers and have come to the conclusion that they only appear or happen on MP servers or missions which have not been updated to the latest DCS OpenBeta update:

     

     

     

    1) No A2A RWR threats being displayed on MFCD.

    2) Counter measure programs not working or being available for selection.

    3) Unable to use F10 map markers to create WPT, PP, and RP.

     

     

    Another thing to consider:

     

    As weird as this sounds, in servers which DO seem to have been updated to latest OpenBeta version, not all 3 of the listed above bugs/issues are resolved. At best 2 out of 3 are resolved with one still being an issue.

     

     

    I hope this helps weed out any problems and I hope this helps us properly report and document bugs and our tests of them for you Deka.

     

     

    :pilotfly:

  7. more details?

    MP host or client? flare emergency button works or not?

     

     

    I confirm the combat page is also not reading proper chaff or flare programs. Unable to select any programs that are set up in special options menu and cannot release any counter measures at all in MP as host or client.

  8. So many important bugs were not fixed! And some things that worked properly were broken. Bye JF-17, maybe next year.

     

     

    LOL i can't imagine you owning the F-16 or the Hornet with that attitude

     

     

    SOMEONE DELETE THIS THREAD AS IT IS NOT EVEN AN ACTUAL BUG REPORT. JUST LAME SPAM!!!!

  9. Hello,

     

    Looking at the special options there is an slider namde "Hud radar slew rate"

     

    Does this mean that the radar can be projected onto the hud?

     

    Also seen on this book

     

    Kind regards

     

     

    Per your resource, the JF-17 should also be able to display the the EO imagine on the HUD, similar to NAVFLIR and for targeting. I wonder if this is for the latest Block 2 iterations

  10. I'm not sure if this a bug or expected behaviour and ignorance on my part:

     

    I created a load-out with 2 * g10, 1 * wmd, 2 * pl5, 4 * g12 (two/pylon, loaded on a rack).

     

     

    Configured profiles:

    - A/S1 with the G10's, set the fuze to n+t / auto mode, quantity 1, 1k ft altitude etc

    - A/S2 with the G12's, again set the fuze to n+t etc

     

    After I release either a G10 or G12, it seems that the profile resets back to the defaults, e.g. the 2nd G10 will have a default fuze of safe etc. Is this expected behaviour (we can only set up the profile for one munition at a time) or ?

     

     

    Remember the profile has to be set on all weapon stations. Make sure you cycle between stations and set the profiles equally. Otherwise, yes, the weapon station you did not modify will have the default (unarmed) profile.

  11. Another thing i noticed is there wasn't any aircraft in our group list with the Asterisk (*) indicating they were the master datalink aircraft. But when I was on an empty group channel and i was in master mode, the asterisk appeared next to my own id. Also, how far ahead did your wingman land from you? he had the W designated to him on my end the whole time I had network connection with you guys through datalink. you can see in video around the 7:58 minute mark.

  12. ***EDIT*** THIS IS IN MP WHERE I AM SEEING THIS ISSUE

     

     

     

    So, it is my understanding that the DATALINK once employed correctly if you are in MASTER NES then you should be displayed as the L (Lead) ROLE in the GROUP LIST. And if you are in SLAVE NES then you should appear as W (Wingman) ROLE in the GROUP LIST. Currently, this is not how this is being displayed. MASTER is showing up as W and SLAVE is showing up as L. Another thing, is there seems to be an issue with AI AWACS and player controlled MASTER DATALINK where the SLAVE aircraft in the flight group get kicked off the Network because the AI and the MASTER player controlled are both conflicting with each other in the DATALINK GROUP LIST.

     

     

    I hope I am understanding correctly of how this is supposed to work.

     

     

     

    Video is linked and this was looked into with the help of ShadowFrost and his wingman (I'm sorry bud I forgot your pilot tag).

     

     

    Keep up the good work Deka! I love this module more than any other at this moment!

     

     

  13. Still trying to wrap my head around this jet's systems but I can't find any documentation regarding this issue anywhere yet.

     

    I've had a couple of instances now where I've tried to select the pod to power on but it will continually show a "No Aux Connection" error message in the center of the screen. Am I missing something here in the procedures or is this some kind of randomized failure built into the module? I can't select anything other than refocus when it displays this message so it just turns the pod into dead weight on the jet.

     

    Any insight into this would be much appreciated. :helpsmilie:

     

     

    Someone else discovered a way to get the TPOD to work. Usually this happens on cold start planes. But the way to get around it is after you follow all the steps of selecting the pod and then powering it on, make sure whatever screen you have the pod on is you SOI (asterisk "*" symbol on the bottom center of screen) and then you press IFF interogation start/stop keybinding. you should see a grey picture after that, next step is to uncage the TPOD by pressing "cage" on the tpod screen.

  14. Just tried it at Senaki so far, I need a way to get out there. The Viggen has or had the same problem, but it has a thrust reverser, so it's cool in that case. Here it's not.

     

    If you need to know which shelter, it's this one:

     

    https://www.google.de/maps/place/42°14'41.5"N+42°02'59.6"E

     

    (that was a lot faster to get than the actual ramp number because DCS even on an SSD takes ages to load up)

     

     

     

     

    Can confirm any hanger slots in Senaki the Thunder spawns reversed. Even checked mission editor to make sure orientation of aircraft is supposed to be facing the hangar doors

×
×
  • Create New...