Jump to content

ENO

Members
  • Posts

    3671
  • Joined

  • Last visited

  • Days Won

    5

Everything posted by ENO

  1. I'm sorry- but just because a person thinks something looks good it doesn't mean they are emotionally connected to it. It can, actually, look good. It's amazing that people need to justify their support of the work going on amidst all the nitpicking. We can't even say "wow... that missile on the wingtip looks awesome!" without being told afterwards "well, your opinion isn't really valid because you're clearly a fanboi having an emotional affair with ED's work." Give me a break.
  2. This is just senseless trolling ^ Go pick fly sh1t out of pepper in some other game forum. The shots are a work in progress and they look great. 'Nuff said.
  3. All good!
  4. This is not the case any more. 1024 is generally enough unless the server is more cooperative (human vs AI) based and hosts a larger number of AI- particularly ground forces. 2048 may be needed for larger numbers of ground AI. LAN settings for clients (unless directly attached to the server network) is completely unnecessary. If the server isn't asking you for a password, then it's not password related. If it's only happening on one server, then there's a chance you've been banned from it. In other cases it may be a version miss-match issue. It may also be a failed integrity check- are you running modded files?
  5. I think in many cases bridges and ships are the same in that they don't accurately reflect being hit by missiles. Then consider that a span may need a 2000lb bomb to destroy it in exchange for 6 or more mavericks- assuming they all hit. As for being "warlike and badass" I can't imagine how AI standing off at 8 miles throwing eggs at something is either of those things.
  6. I think this may have already been reported but in case it helps had a non-crash causing error last night described here (the logs / track are included) http://forums.eagle.ru/showpost.php?p=2020469&postcount=31 The lines mentioned in the error were: 4241: if eventData:getCategory() == 1 then -- normal groups 4254: groupsToAdd[#groupsToAdd + 1] = Unit.getByName(eventData):getGroup():getName() Given the times, it would have happened right around the time tankers were running low on fuel and would be respawned / cloned by the tanker script.
  7. [17] = { ["alt"] = 540, ["type"] = "Turning Point", ["action"] = "Turning Point", ["alt_type"] = "BARO", ["formation_template"] = "", ["properties"] = { ["vnav"] = 1, ["scale"] = 0, ["angle"] = 0, ["vangle"] = 0, ["steer"] = 2, }, -- end of ["properties"] Oh! Okay... The above was the lines between 4240 (the [17]) and 4254 but if what you're saying is right then there's no relation with the above. I'll go post this (well, the lines from MIST when I get them) in the MIST section unless you guys have already reported it. 4241: if eventData:getCategory() == 1 then -- normal groups 4254: groupsToAdd[#groupsToAdd + 1] = Unit.getByName(eventData):getGroup():getName()
  8. I'll go into the .miz and see what's up and share my findings. On a positive note this didn't cause a crash- but on the other hand the only reason I found it was because I was looking for something else.
  9. Eh Steve... I'm running a relatively simple mission here and the only MIST functions are those in your script... I'm wondering if you can take a look under the hood and see if you can figure out what's up with this. I think the timing is about right for the tankers to be returning to base low on fuel: 18946.851 INFO SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\Eno\AppData\Local\Temp\DCS\/~mis00..."]:4254: Parameter #1 (unit name string) missed 19512.686 WARNING LOG: 282 duplicate message(s) skipped. 19512.686 INFO NET: Lua: Disconnected client [2] "xxxx" 19512.686 INFO NET: remove: client 2 19512.847 INFO SCRIPTING: mist.scheduleFunction, error in scheduled function: [string "C:\Users\Eno\AppData\Local\Temp\DCS\/~mis00..."]:4241: Object doesn't exist Thanks in advance to anyone who can get their finger on a pulse here... tanker files.zip
  10. I do ctts init and mist is a "mission start" but any command I use for either of them (ie: mist related or ctts related scripts / instructions)I wait 10-12 seconds. Sorry I didn't see this sooner- for some reasons I didn't register a new response.
  11. Time to look through the GUI documentation. Once you dabble in that for awhile, try a few things. If you get stuck- post your mission and someone will help.
  12. Must... resist...
  13. 64 bit only. Why is my troll detector beeping? This can't be real. 3 posts since November 11? All 3 posts about crashing since 1.0.0.9? Naaaaaaaaaaah.
  14. Nice work ranger. Adds some good potential for variety.
  15. Comfort in complacency or familiarity? Is it an insightful proverb or just an old cliche?
  16. This isn't a requirement since 127 and in fact is no longer recommended. For missions light on AI and in particular ground units then 1024 is the recommended setting. When more cooperative missions are being played with more ground units then 2048 is the recommended setting. I'm not sure I've since read that any client has had to use over 2048 since 127 for a stable experience. The server computer can still use a LAN setting to sustain upload requirements -or the highest ADSL. Obviously as the clients start using lower settings this puts less upload pressure on the server and can significantly reduce lag / warping. Oh and yes I was kidding around earlier. ;)
  17. Probably just don't have enough RAM to run DCS reliably.
  18. Not so far... my refresh key is getting worn out.
  19. And just to confirm you did a repair (I know you did a reinstall- but repair may have different affect) and also a reboot?
  20. Good point- hadn't thought of that.
  21. Still not sure what's up Hijack... I've been running MIST missions since the new beta update came out- Granted, I do have a bit of a process each time... which at the very least involves saving a new version of the mission to a new name. Sometimes, if that acts up, I'll go in, delete MIST then save... then reload the MIST trigger at mission start (or init) and save one last time. That generally clears up any mission related errors. With that being said- yours sounds more like a GUI interface problem... I've never seen such a thing.
  22. Sometimes can help to reboot as well.
  23. Looked the same to me... Repair?
  24. I'm with the sli crowd on this. They're becoming more available for cheap now and lightly overclocked the 670 is probably the best card for the money. Depends on your budget measured against other possible upgrades... But sli'd 670s is a really good option.
  25. I keep reading the hog documentation about how they use their canopy to help stack and rack aircraft in the AFAC role and I wish there was a realistic and practical way to apply that. I don't expect it by any means- but between binoculars and the grease pencil I think we're missing a big part of hog culture.
×
×
  • Create New...