Jump to content

SGT Coyle

Members
  • Posts

    1388
  • Joined

  • Last visited

Everything posted by SGT Coyle

  1. Yes, please do not require a lock button operation on the fuel shutoff lever.
  2. I like this. Has all sorts of promise. You could have a trigger zone foe detecting the player present and tuned to certain freq. Yes I like this.
  3. Is it possible to detect when a player creates a new waypoint?
  4. Not sure if I'm asking this right, so here goes. Why can't I go directly to my DeskTop from Game, with LWin+D? I always have to Alt+Tab to get to something open on DeskTop, before I can LWin+D to the DeskTop. I hope that makes sense and someone can explain it. Thanks
  5. Track File.
  6. I thought the question was related to DCS not real world. I wasn't arguing with you. :flowers:
  7. Trying to stay within the bounds of the OP, will the Harrier accurately model the interaction with JTAC? It's not specifically mentioned on the store page list of features, but I would assume that it would be. How is this to be answered based on the features listed?
  8. I know this is late, but I think the consensus is "No". I'm not even going to bother quoting every opinion or bit of speculation as to why in this thread. Razbam_Elmo, can you give an update as to where we are, and where we are going, as to the ability of DCS World JTAC to send info directly to the CAS page?
  9. Players to contribute, Testers to investigate, Report, Communicate to Devs, and Track. Done right it should save money on labor and reduce to a minimum "Forum Drama". With automated notifications, a reporting player and any player wishing to subscribe, should be able to receive changes in status. Also players should be able to view and search the data base of reports.
  10. Bug tracking should be an ED enterprise and not left to the third parties to track on their own. They a;ready have a "Ticket Reporting" system built into their website. That I believe is the bug tracker NineLine referred to when he, BIGNEWY, and tea_cipher are using to get Razbam on track. ED needs to build a public facing BT for the players to interact with and use as a source for info on what's up with the bird. This shouldn't be left to third parties, any of them, to manage in the public eye. And I agree thee with Lorthirk's post about change and transparency.
  11. I'm voting to stay the way it is. I would for the time being follow tea_cipher and BigNewies lead. Do what the do. A lot of the old threads are probably going to to get resolved with listed updates from the Status thread. But I would pick a few of them everyday and check if they are still broke and go through the routine. But don't get bogged down and get behind on new ones. I like to see the tags on the threads that tell me a cursory glance whats going on with the bird. [invetigating][reprted][need trak].... And don't let people treat the bug section as a general chat. And don't touch the Brass!
  12. I can't wait. I can't wait so bad I have to pee.
  13. Glad to see you made it to the party. I noticed your absence. and I couldn't agree more.
  14. Welcome aboard. Please don't touch the brass.
  15. Know worries. I was hoping you might have some chapters complete, but I can wait.
  16. Excellent! I would be glad to help in that regard.
  17. Can we get whatever chapters that may be complete, hosted for download. I have several questions about Nav, CAS page, and some other systems, but I can't intelligently articulate them because I don't have a basis for understanding. There's just to much contradictory, or guesswork information on these forums to sift through.
  18. Unfortunately, after reading pages four to eight of this thread, I don't think many of us trust that Ron will make good on his obligations to the player base or to ED. I've looked at Razbam's discord and Facebook page, after Ron's post, only to see the same attitudes toward the ED player base they've demonstrated these past years. Maybe to a lessor extent, but it's still there. BigNewy, NineLine, and tea_cipher (that guy is doing yeoman's work) are rapidly getting the bug section of the forum under control. Thank you. Is that going to be the plan going forward? Will ED be managing the bug section of their forums from now on? Because if the answer is "No", or "We'll see", I don't have the faith required in Ron to continue with a steady rate of progress or to not disappear off the forums again without ED's ever present over site.
  19. I forgot to say thank you for the status report.
  20. I would add "Resentment," but otherwise agree wholeheartedly. I accept your explanation of events and reasons for what has been done/needs to be done, but that acceptance comes at a price. I expected, and do expect to see a more detailed road map and better communication of circumstances/events/set backs (good and bad). Had you stayed present on these forums with sort of material instead of teasers for future projects, I think we would be in a better place. I look forward to seeing you and Larry on these forums on a regular basis. If you have any questions for me about my concerns or past posts, feel free to PM on these forums. Good Hunting
  21. GIUK Line. Get me some Red Storm Rising on.
  22. Probably because there was no progress. I posted a long list of missing key binds and they classified as "Low Pri" (understandable), "New Feature Request"(infuriating), and had status of "Working on it," for two years. I believe you would be talking about posts showing off new projects. Maybe how the pilot body is coming, while people have been clambering for fixes to old bug reports, or acknowledgement of bug reports at all. I believe that point was made several pages back. I was glad to hear you stepped down. I thought you had gotten a raw deal. You were in an impossible position. Being the middle man between an annoyed public and a company that was ignoring them. I wish you luck with whatever your doing.
  23. This why I think a public facing bug tracker would relieve a lot tension these forums have. I for one would not have my current attitude with Razbam, if I new ED was tracking bug reports and communicating those reports to the Third Parties, customers, and It's Self. Having a closed loop, single source, transparent system of reporting would greatly reduced the work load of so many. Not to mention the perception of screaming into a black hole. if whaen I make a report about any module I would to expect that it be investegated and comunicated the result of that investigation. If valid, reported to the Deloper and put on a clock, say two weeks (See what I did there?:lol:). Not to completed, but to remind ED to nudge the Developer. ED: "What's up with this?" "You got a plan?" Developer: "Yeah, it needs animation and waiting on pilot body for VR" Then I could get that message in my inbox and know I am valued. All would be well and flowers would pick themselves.:thumbup:
  24. Concerning the use of the forums as bug reporting system has always bothered me. It's great if you want to have a conversation about bugs/issues, but as a reporting and tracking system it is horrible. I for one, I know there are many more, would like see a change to the ticket reporting system. It should be a searchable and browse-able data base for the customer to investigate weather his/her issue has been reported. Or what's going on with a particular module. Update and add more reporting fields/filters. As it exists, there is only the bare minimum of info required. I would like to see fields as to Aircraft System/Graphics/Flight Model, ect... The feed back to the customer seems OK. I've used the ticket system only a few times for non game related gripes and was satisfied with the experience. I don't think there were game issues reportable then. But that was a long time ago. I know there is concern about the public messing around in the internal ED bug tracker, but separate public facing BT would offer a tremendous cost savings. It can't possibly cost any more in man hours than the current system, as I understand it, of scanning forums, passing to testers, testing, asking for track file, watching track file, acknowledging / reporting, ect... At least the scanning forums for bug reports can be reduced. Let alone the endless duplicate reports because of a finicky forum search function. Just food for thought. And make it official reporting platform for modules. So we don't have to go through this again. Please
×
×
  • Create New...