Jump to content

tophe

Member
  • Content Count

    1122
  • Joined

  • Last visited

  • Medals

Everything posted by tophe

  1. Check your firewall. Make sure you forward the right ports. Try turning it off all together for your server machine, just to make sure.
  2. You have probably loaded an older profile. Max Packets Size in perfomance should ne 1400. if you load an old profile it will be zero.
  3. hehe.. I thought of you ;-) But this is actually unrelated to the problem you had. When the profile initially loaded on startup the mission folder would not get scanned if the profile was loaded from disk. It would only have earlier missions in the list. Every time you switched profile, reset or clicked refresh it would scan though. So I doubt anyone noticed that bug. Just realized that he program has come quite far from the first release
  4. New version out. See first post. 2.4 - 2013.10.02 - New: Cleaned up the interface, added icons and some color to the interface New: Set the difficulty level on each cycled mission individually Fixed: Mission folder wouldn't scan when program starts
  5. Figured that ;-) It's a great way to learn programming.
  6. Yes, if you use and old profile with the new version of TADST the Maximum Packet Size value will be zeroed out. Just put 1400 in there and you're good to go.
  7. I don't think that's possible. The only thing TADST does is start the server exe with your selected settings, it does nothing to the server or game after it has launched.
  8. Make sure you have the TADST.exe in your game root C:\Program Files(x86)\Steam\SteamApps\Common\Arma 3\TADST.exe. You can't have any subfolders. I have no clue what could be the problem if you're doing everything right. I don't think there's any locality problems in the code that could ever mess up the paths. The path you have is no problem for the program.
  9. You're not supposed to put your MPmissions anywhere else than in the MPMissions folder. Just put the PBO-files in there. If you run TADST from your A3 folder (C:\Program Files(x86)\Steam|Steamapps\common\Arma 3\) TADST wil detect the missions. If not, I don't know hat you might be doing wrong.
  10. It might be that the sockets are set to zero. The default value is 1400. This will be set with a new profile, but not if you load up a profile from the old version - then you'll get a zero.
  11. Strange. Did you delete your old profile and start fresh?
  12. Haven't tried with the old profiles. You'd be safest off with a new. But try... if it works it works. Check all your textboxes and settings and resave. It's the stuff in the GUI that goes into the config files. ---------- Post added at 05:25 PM ---------- Previous post was at 05:24 PM ---------- Thx, great input. For now you can put the performance bits in the "extra parameters" box. The update thing is probably next.
  13. Version 2.3 out. Updated the first post! 2.3 - 2013.09.27 - New: Added Maximum Packet Size option (class sockets{maxPacketSize = <limit>}) New: Added Required Secure Id option New: Server now supports headless clients New: Doubleclick password fields to autogenerate readable passwords (just for fun). Improved: Dabbling with some colors to make it less depressing, let me know if you hate it. Improved: Arma2/Arma2AO beta servers now uses the correct -beta command line Improved: Steam ports moved to top of config file Fixed: Persistens Battlefield settings Fixed: BattlEye checkbox fixes Fixed: Default difficulty in profile Fixed: Required Build now collects Arma3.exe build, it also saves to profile. Fixed: Kick duplicates checkbox state now saves to profile Fixed: Tooltips checkbox state now saves to profile Fixed: Launch As Is checkbox state s now save to profile. Fixed: Terrain Grid didn't transfer to config file, fixed now. Fixed: View distance didn't work, working now. Fixed: Server scripting textboxes are now saved and loaded correctly
  14. And oh... Found the difficulty bug. I didn't know they added a difficulty = "veteran"; to the .Arma3Profile file. What are the valid values? Is it "recruit", "regular", "veteran" and "expert"? I always mess the last one up, sometimes they call it "Mercenary" and sometimes "Expert".
  15. New version out tomorrow! Mostly bugfixes and some new features. The Headless thingy will be in next release (next week - at most)
  16. Loads of new input! I'm completely flooded with work at the moment, but I'll try to have a new version out within a week or two. First off bugfixes!
  17. Hey guys. I've been a bit busy working and doing all kind of exciting stuff, but I'll get back to fixing this tool real soon. Not sure why the game resets the difficulty. But it shouldn't have anything to do with TADST. I think they might have disabled it in the BETA. TADST will write the difficulty to your config file (you only change he settings for the difficulties under the Difficulty Settings tab, the actual difficulty is chosen under Missions.) When the server is launched TADST will not do anything else and the config files are correct. But the files are always overwritten by the server and if BIS has disabled some settings the game will overwrite them. At least I think this is what's happening. TADST writes the chosen difficulty and then something happens when the server launches that has to do with the game binaries. I'll look into it!
  18. I'm afraid not. Might have to wait for the final release of A3. But you can still use the A2 version of the script, except for some features. I'll try to get to it as soon as I can. Sorry for keeping you waiting!
  19. If anything needs to be added to the configs, you can always generate your configs, edit them and then launch with the "run as-is" box ticked.
  20. Yeah, sorry guys for pulling it down and thank you for understanding! The A2 version is still up, it works with A3 as well (not all functions though). I'll look into the module thingy and see if my script is at all needed or if I can streamline it a bit. Right now I'm caught up with concerts and work. But soon :-)
  21. Not sure, gotta look into the whole Rcon thingy. Never used it. I hope to have it figured out within two versions.
×