Jump to content

FSKRipper

Members
  • Posts

    1227
  • Joined

  • Last visited

Everything posted by FSKRipper

  1. Hi Ragnar, I hope it is no misunderstanding from my side but here is wat happens: Picture 1: Bomb Plan Mode, with Master mode selector to ANF I'm getting HUD information to steer to the Popup Point. When reaching Popup, the HUD is automatically switching to target Point. Picture 2: DYK Mode, with MM selector in NAV I get the same reading as in Plan mode, fine for me. Picture 3: When using precision DYK mode (Weapons selector to DYK, MM selector to ANF) I have no indication where the popup point is. HUD as well as waypoint marker are directing me to the target. To get this done I would have to fly in NAV mastermode to the popup point and switching to ANF the same time I have to pull up and the waypoint changes from U1 to M1. Maybe this is intended but since this workload is not needed in the other bombing modes I would be suprised.
  2. Since 2 months and more than 1300 views of the thread could not bring up some info I conclude this could be a bug: During DYK precision mode (set to ANF) and using a popup point I get no steering information on the HUD for the popup point, only for the target. This is different from the PLAN mode where you are guided to the P-Point and then the symbology switches to the real target. In my understanding the P-Point would be much more important in a dive mode so supporting level bombing with steering information but not dive bombing makes no sense imo.
  3. An what brings you to this assumption? I think Wags stated clearly that in the forseeable future we won't see anything like this due to the detail level and memory consumption of DCS Maps.
  4. This is a major problem in my opinion. I think the statement should say: they think they have a better idea of how the plane should work. As very good demonstrated in the F-14 thread they often stand corrected by SME's showing that the open available Natops isn't state of the art or simply wrong in several points. This gets more serious if you have no SME's willing to discuss with the "experts". You find it everywhere, see new Harrier pit texture thread. What does a crew chief know...Everyone who had his ass in a demo plane some minutes knows better... There are several points were we agree (ASL...) but not at FM issues. Even ED's new baby is nearly a year on the market with some issues known and left for nearly the same time. If you read some M2000 FM threads very carefully you will see that most of the complains are based on old Information or a lack of system knowledge (see stall behaviour). For my part I believe that we will see improvement but not withouth mistakes (see the Hawk). Maybe you guys should do a short investigation how long Nevada took to get public. The first Beta for the Cat was announced for 2017 I think. Razbam is doing this work simply in open Beta than closed development. Some may find it offensive some others good. I still wait to see some Viggen issues getting fixed which are known since 12 months but who cares (now).I can only encourage you guys to a lot more patience when it comes to module development. We still wait for a multicrew huey (Since 4 years?). See the good thing: Since the modules don't get finished fast you wont have to pay for Updates (Black Shark 3 f.e.) :lol:
  5. Fair enough. Just a reminder when building your opinion on a module: If you search through 2 or 3 subthreads and see almost the same 10 people bitching around I won't give a cent on their opinion. You will also find those groups in the Tomcat and Hornet forums so you will likely get an idea what I mean...
  6. You will miss a lot by that especially since the Hornet is far away from finished. Regarding the tide, this is (a)social media. The people complaining most are the loud minority.
  7. This is the problem with stories. According to Keith "Okie" Nance in his Q&A (you find it on Youtube) he had never issues with it and it happened only once in his career to him, by a mistake from his side. Solving this issue was no problem at all.
  8. I personally think the AB of the MiG 29 looks much worse especially when looking into the engines while the viggen looks fine for me but as you see different people have different opinions.
  9. Not as long as Heatblur "only" developes the A and this B version.
  10. OK folks. start your business. :pilotfly: Sacrifice some hundred hours and some of your money to get your hands on the FM data from the private owned MiGs. Should be a matter of some hundred flight hour, not more After you did all the programming stuff, the avionics and the artwork (should be only 2-3 years of your sparetime) you can go to early access and get a full load of BS and insults for your work from people already complaining about the ED PFM's. Is that not a good reason to become a 3rd Party dev :thumbup:
  11. Let me simply answer with a quote of Wags from some days ago, fitting perfectly for this and many other situations: "Yep, there is ALWAYS at least one person that will find the negative in anything."
  12. And then ED should charge you for every cockpit seperately as DLC. Or should you buy the module for 80-90$ including all pits? Questions over questions...
  13. So an ex F-14 pilot tells you it really really doesn't matter and the G-Meter is not the most important Instrument for flying this plane. You have a different opinion. Fair enough, but no bug as you were already told but only a question of the view perspective. I think we can stop this right here? :music_whistling:
  14. According to the TID picture the radar was in PD mode so the parachutes should have been filtered out even if detectable in theory.
  15. I have serious doubts that A. a pilot in a 9G turning fight is staring at his G-Meter B. your plane will desintegrate at 7,7 instead of 7,5G
  16. Times change :thumbup: :laugh: Please stop it, this is too much :laugh:
  17. Maybe you should talk to your lawyer immediately because you seem to have no idea how wrong you are :music_whistling:
  18. Sorry, you are Right, I'm not in the position to decide who is wrong. But instead of bitching around and demanding an apologize you guys could take it as what it is, a joke.
  19. Ah, napkin math at work again. Began to miss you during the last months :thumbup: But its April fools day so maybe I was wrong in taking you for real...
  20. Because they can and do it every year so calm down and stay with the stable version
  21. You are definitely the wrong person for an open Beta :doh:
  22. How about finishing one plane and smashing bugs before releasing the second?
  23. Can you add a track and explain the conditions a bit further?
×
×
  • Create New...