Jump to content

SGT Coyle

Members
  • Posts

    1388
  • Joined

  • Last visited

Everything posted by SGT Coyle

  1. Do you need to cancel order and try again, or will it resolve with time?
  2. Creat 5 random points in my poly zone and retrieve the first point to spawn a RadiusZone. But I first have to get a Vec2 position to put into the Radius_Zone:NewFromVec2(vec2,altitude) function. I removed the smoke but still did not get what I thought I should. [ClassName]=POINT_VEC2 I was expecting an x and y numbers.
  3. And years of silence from DEVs on bugs and missing features, is the difference. In this thread, 10 days ago, I asked: I would think that an easy question to answer.
  4. Can we get a an copy of the "Keyboard.html" from the InputLayoutsTxt folder for download? I'd like to the field running with a TARGET script ready to go.
  5. It might help if you told us what you want to do.
  6. Can I remove a Bullseye from the mission with the ME? Can't some planes make their own Bullseye Marker in the cockpit?
  7. Trying to create a Radius Zone without using a ME placed Group/Unit/Static. Been kicking around this idea for the past few days on Discord, although there's been plenty of help, I haven't been able to crack this nut. So this is the script: MPZ = ZONE_POLYGON:NewFromGroupName("MPZ") -- Master Point Zone - A Poly zone to contain and generate random point. MPZ:SmokeZone( SMOKECOLOR.White, 10 ) -- temporary for testing local vec2Points = {} -- Table of vec2 points to be used to create trigger zones --local coordPoints = {} -- Table of vec2 points to be converted to LLMDS/MGRS/F10Marks/BRA/BullsCall for i = 1, 5 do local RPoMPZ = MPZ:GetRandomPointVec2() RPoMPZ:SmokeBlue() table.insert(vec2Points, RPoMPZ) end navZone_1 = vec2Points[1] [b]-- this variable is nil and code breaks here.[/b] How can I get my "vec2Point[1]" to produce something I can use? I assumed there was useful data in that table, as all the random points get blue smoke within the poly zone. Any help or thoughts would be appreciated. Thanks
  8. Yes, please do not require a lock button operation on the fuel shutoff lever.
  9. Logs. If the game crashes, how do you recover a track file?
  10. 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.
  11. Is it possible to detect when a player creates a new waypoint?
  12. 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
  13. Track File.
  14. I thought the question was related to DCS not real world. I wasn't arguing with you. :flowers:
  15. 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?
  16. 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?
  17. 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.
  18. 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.
  19. 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!
  20. I can't wait. I can't wait so bad I have to pee.
  21. Glad to see you made it to the party. I noticed your absence. and I couldn't agree more.
  22. Welcome aboard. Please don't touch the brass.
  23. Know worries. I was hoping you might have some chapters complete, but I can wait.
  24. Excellent! I would be glad to help in that regard.
  25. 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.
×
×
  • Create New...