Jump to content

shyjonathan1588

Members
  • Posts

    44
  • Joined

  • Last visited

About shyjonathan1588

  • Birthday 05/21/1984

Personal Information

  • Flight Simulators
    DCS
  • Location
    Reston, VA
  • Occupation
    Government Attorney
  • Website
    https://www.youtube.com/user/shyjonathan1588/feed
  1. Removed - duplicate of separate thread. ok to close/delete this thread
  2. HACKING ATTACKS I got an email someone (not me) tried to log on with my username from a foreign IP address last night. I searched the forums and I am seeing several others complain of this in the past few days. What's going on?
  3. No, but not for morality or realism reasons. I'm skeptical about nukes playing nice with all the countless other, more fundamental, things being simulated in DCS. It just seems like an invitation for more bugs. I value bug fixes more than rolling out new features.
  4. Spend the least amount of money possible on the stick if you refuse to get the TM warthog right now. You will be getting it sooner or later. I spent $250 on the Logitech G940. Force feedback is nice, but you'll still miss 20-40% of this game's awesomeness using anything short of the warthog. Buy cheap now because if you play the game as it is intended to be played, you will eventually fork over the money for all the proper hardware. I wish I hadn't wasted time and money on anything short of the warthog, but if you must, keep this prediction in the back of your mind: you will be buying two joysticks.
  5. My guess is the combination of the many thousands of trigger conditions and starting on the ground at Kolkhi stresses the CPU? Take a look at the infantry detection triggers (5-10 toward the bottom of the triggers list-I think?-with American names). I KNOW those take a toll on CPU resources because each one has 700 conditions. I play on a pretty unremarkable system. Using version 1.2.8 (and recording on fraps), my anecdotal experience has been stable framerates around 17-25 for hours at a time, except during startup, taxi, and takeoff, when it gets as low as 0-5. Example with links to fps checks in description: Not sure if there really is a performance hit on which versions, but again, anecdotally, I noticed a huge hit going from 1.2.6 to 1.2.8. For example, I was getting the same fps testing my master unit library (10x as many platoons and 10x as many trigger conditions) in 1.2.6 as many people are now reporting on the taxiway in normal missions in 1.2.10.
  6. All missions are random within the stages. I created IPs in all missions. They are just arbitrary points but JTAC communications utilize them to relay positional information. I have low expectations for any of this working well in future versions, EDGE, etc... everything is subject to change, and I accept that. I have no plans to try to keep pace with the updates because you're right; I can't. I just wanted to share this with the world and let others do with it what they wish. If nothing else, the names and scoring system could be fun for other builders to have laying around. Special hugs and kisses to anyone who can figure out why sometimes infantry starts shooting and my triggers activate (they clearly have situational awareness and are performing JTAC/CAS enroute task as intended), yet they insist "no further tasking available" when the player radios them. See http://youtu.be/LdzxhH1kfl0. Thanks for the tip about ogg. I'll be sure to do that in the future.
  7. Thanks for all the feedback and words of encouragement! Looks like it struggles HARD with recent versions of DCS, so I will: (1) add a big, ugly disclaimer to the announcement post, and (2) not update my own version beyond 1.2.8 so I don't suffer the same fate! Thanks again guys.
  8. Also (if anyone gets in the air with tolerable FPS), don't be discouraged if you finally get a JTAC request, but they respond to your availability with "no further tasking available." The JTAC tasks are all "enroute" tasks requiring real situational awareness. Everyone is on the move down there, going into and out of JTAC range, and terrain occasionally blocks line of sight.
  9. Interesting and disappointing... What version of DCS are you running? Low FPS at or above airports? I've registered my complaints about how performance of this campaign gets worse with every update (http://forums.eagle.ru/showthread.php?p=2105259#post2105259), and that thread has some discussion of the airfields/objects issues. Since then, I actually downsized the number of triggers/conditions in the campaign itself, lowered some of my settings (the usual mirrors, water, etc.), and added some fans and memory to my system. I also made this tweak to the high.lua file, and it gave me a boost: http://forums.eagle.ru/showthread.php?p=1970664&highlight=config#post1970664. I built it on version 1.2.6. It is tolerable for me playing in 1.2.8 right now, but I haven't updated beyond 1.2.8 yet out of fear of continued performance loss. :( Curious about what kind of performance others are able to get, and on which versions of DCS...
  10. NOTE: SEVERE PERFORMANCE ISSUES REPORTED IN RECENT VERSIONS OF DCS (I.E., 1.2.9 and 1.2.10) Available Now: Large SP campaign focusing on long duration on-call CAS flights where infantry radios you their JTAC requests. Lots and lots of randomness. LIHV = "low intensity, highly variable." More features and a download link at my website: http://hawgslihv.com/downloads-2/
  11. Thanks. I'll have to study that and go in that direction.
  12. Radio Call: I used the existing JTAC speech files, but edited them to say "this is [callsign] [number], tasking available." I threw in some random cadence and volume differences, as well as some static and small arms fire, to make it interesting. Triggers: I make one trigger zone with a 500m radius (approximate infantry engagement range). I make a trigger for each infantry platoon. Each trigger has hundreds of "or" conditions, one for every enemy unit on the map, of the type "unit inside moving zone" where the zone is centered on the platoon leader. There is no quick way of doing that. It took me many months to make about 75,000 of those "or" conditions for my campaign project. When activated, (1) a radio message specific to that platoon plays, and (2) a triggered action makes the platoon start its JTAC task.
  13. I have between six and ten per mission, and 100 missions in a campaign. All infantry. They are linked to unit inside moving zone triggers with a zone radius equal to infantry engagement range. I have them walk on roads with unpredictable gauntlets of enemy insurgents, and only if/when a firefight breaks out, they radio the player requesting CAS. It makes for unpredictable and replayable SP gameplay. Here's an example starting at 3:25 of a highlight video of one such mission:
×
×
  • Create New...