How is the update coming along Tophe?
Still awaiting that pm![]()
How is the update coming along Tophe?
Still awaiting that pm![]()
I need help, I got the server to work and all, but when I put the missions in, it don't show up, so I converted it over to PBO's, and it showed up, but when I went into the server to play and all, its not the same missions, they are missions that I don't even have anymore. So please help! thanks!
---------- Post added at 20:20 ---------- Previous post was at 20:19 ----------
And also, the missions are like ib%20training%20?
"refresh list"
Yeah I did that, what I did wrong is not export it to multiplayer missions
Östgöta Ops [OOPS]
TA2DST - Tophe's ArmA 2 Dedicated Server Tool || A song for Bohemia
ARMA 2:
Random House Patrol Script v1.1 || Simple Vehicle Respawn Script v1.7 || Simple_Guard_Post_Script_v1.0 || Universal Crate Filler v2.01 || Simple Repair Script v1.1
ARMA 3:
Simple Vehicle Respawn Script v1.8
How can i use BE client thing with this? it asked for Rcon code but I dont know where to find that in this tool?
Tophe, just want to thank you again for making this excellent program.
I know you're working on an update and was wondering if you could include a few things:
1) A "requiredBuild=xxxxx;" field for the server.cfg. This way people can know what version you're running of the beta
2) A checkbox to launch Combined Operations instead of having to put "-mod=D:\Program Files (x86)\Steam\steamapps\common\arma 2;EXPANSION;CA" in the parameters.
Thanks!
Can't wait for a new version of this...1.3 seems to throw a ton of "Value not Valid" errors.![]()
Last edited by MavericK96; Jul 5 2012 at 23:17.
Core i7 920 @ 3.995 GHz, HT off
12 GB OCZ DDR3-1600
GTX 680
2x Intel X25-M 80 GB SSD
Windows 7 Pro x64
ArmA2/OA Settings:
1920x1080 w/ View Distance at ~3600
Video Memory at Default
MSAA Very High, AToC=0, SMAA Ultra
Post Processing at Very Low
All other settings at Very High
I actually don't know why it keeps doing that. I am rebuilding the settings file system to use XML or something more stable.
This version might fix some of the those problems as a result of me fixing some other bugs, but I have not adressed that problem specifically. Some people get it often but most never do, so it's kind of a mystery to me. I have to admit I started coding this when I didn't know any C# at all...
Now I know a great deal more, so I'm thinking of refactoring the whole software to be able to add new features a bit quicker.
I'm sending the new (very modest update) to a couple of testers this weekend. Then I'll start on that.
@zuff: Do you have any good links with valid information on your point no.1 first ? I'll try to put that in this version.
Sure:
http://dayzmod.com/forum/showthread....1774#pid191774
It's a big deal with Day Z. It seems people with older beta versions can still connect to newer beta servers. With the drastic changes and anti-cheat measures that vary from beta to beta, it's important making sure your players are all on the same page so to speak.
From http://community.bistudio.com/wiki/server.cfg:
Code:requiredBuild=xxxxx; From 1.60 Patchlog: requiredBuild=xxxxx; in server.cfg preventing obsolete clients to connect.