Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Ghostyy

Pages: [1]
1
Hosting & Management / Re: Battleye Issue
« on: Apr 22, 2017, 11:36 AM »
Was due to Battleye Server Issue. 2 hours later the issue resolved itself.

Also, I will remind everyone incase they haven't seen it.

BEC and Battleye for x64 require you to rename the beserver.cfg to beserver_x64.cfg before it will work.

I know it has probably been mentioned somewhere else but no harm in posting it here again.

Regards,

2
Hosting & Management / Re: Error with extDB/HC?
« on: Apr 22, 2017, 11:34 AM »
Currently looking into that now.

Fixed the battleye issue by deleting the main dlls and re-validating the server. Guess there was a problem with one of the files being corrupt. Had to do this twice in order for it to work properly.

Also have now double checked everything a few times and had a 2nd set of eyes look over it and it seems to be fixed.

Line 798, I did use the latest proper x64 branch that had extDB3 support. I am going to double check that again later on as I have been staring at this for the past 12hours (UK Time) and honestly all I am currently seeing is code and 1s + 0s...

Link to repo I used -> https://github.com/A3Wasteland/ArmA3_Wasteland.Stratis/tree/extDB3
Not sure if this is missing something, I will compare the persistance files to the altis version and see.

Thanks for pointing that out though Matt

EDIT::
Compared my oSave.sqf to the Stratis and Altis extDB3 Branches and all 3 match.
I also double checked extDB\postObjectSave.sqf + world\postObjectSave.sqf
All identical, so I have no idea.

3
Hosting & Management / Error with extDB/HC?
« on: Apr 22, 2017, 05:49 AM »
I have recently posted a post in the Server area below this about Battleye. That has been down to a BE Issue that still isn't resolved on my end with BEC. That story remains the same..

I have just updated my pbo completely and the server to extDB3 and x64.

I tested this all on a separate server on a different port. Everything seemed to work fine.

I moved all the files to a new folder and took the old server down, put the new one up in a different folder (for backup and redundancy) and changed the ports. The ports are now the same as the old one.

However, the majority of my players cannot connect or not for longer than 5mins due to a Steam Ticket Failure or a Battleye Error.

Recent RPT Posted in Pastebin -> https://pastebin.com/UrrYNy5C

Also players are getting kicked for a mismatched addon which I found is currently a running problem with ARMA3 and there is a port in the FT (Feedback Tracker) for it.

I am just wondering why this error is popping up.

I have disabled HC in the main_config and also do not have it running. There is nothing about HC in description.ext either.

When I connect I either get Connecting Failed or I get in but am unable to pick any of the player slots to load in.

Any help would be appreciated and if I find a solution I will post it.

4
Hosting & Management / Battleye Issue
« on: Apr 21, 2017, 08:48 PM »
Just completely recoded our server. As of today, the day I decide that it is finally ready, I am now continuously getting

Could not connect to BE Master.

BEC is also not connecting to the server using either localhost / 127.0.0.1 or the server ip.

This is now constantly kicking 5 - 10 people about 2minutes after connecting.

Is anyone else currently having this issue or is it just me? I know it has happened in the past and it turned out Battleye was down or in the middle of an update.

I have checked RPT / extDB3 / BEC logs and have nothing. BEC just says "Lost Connection Closing Socket" and RPT Says nothing relating to Battleye.


Any help would be appreciated.

5
Infos & Tutorials / Re: A3 v1.58 difficulty options
« on: Apr 24, 2016, 08:44 PM »
Probably not related, not sure

Have you read Dwarden reply here https://forums.bistudio.com/topic/190168-battleeye-rcon-new-settings-tutorial/

"you also shall not need to add the RconIP entry
as undefined equals to 0.0.0.0 (all IPv4 local IP addresses)
setting it to e.g. 127.0.0.1 will prevent it to respond on external IP
setting it to e.g. external IP will prevent it to respond on localhost 127.0.0.1"

Our BESettings.cfg have a port set and the IP is not.

6
Infos & Tutorials / Re: A3 v1.58 difficulty options
« on: Apr 24, 2016, 06:54 PM »
What does your restart script look like. I was a moron and forgot that my restart script had a portion in there to copy a profile that I could edit while the server was live. Then during restart would copy that file to the active profile. I have this for a bunch of my config files. So that I can make changes while the server is live and update them at reboot.

Our restart.bat looks like this ->

Code: [Select]
@echo off
taskkill /f /im "arma3server.exe"
taskkill /f /im "arma3client.exe"
taskkill /f /im "servermonitor.exe" /t
copy F:\Games\Arma3\A3Master\battleye\bans.txt F:\Games\Arma3\A3Master\battleye\server2.txt
start /wait F:\Games\Arma3\A3Files\Arma3updater.bat
start /wait /b /high /affinity 7F F:\Games\Arma3\A3Master\arma3server.exe -maxmem=4096 -noPause -filePatching -noSound -nosplash -autoInit -name=Fractured_Server -profiles=F:\Games\Arma3\A3Master\BattlEye\1 -config=a3config.cfg -cfg=basic.cfg -BEPath=F:\Games\Arma3\A3Master\BattlEye -world=Stratis -port=2302
@echo Server Initiated
:bec
taskkill /f /im  "bec.exe"
timeout 10
cd "F:\Games\Arma3\A3Master\BEC\"
start "bec" "F:\Games\Arma3\A3Master\BEC\bec.exe" -f Config.cfg
@echo Server Bec initiated!
@echo Waiting to launch Headless Client
timeout 10
@echo Launching Headless Client
tasklist /fi "imagename eq arma3client.exe" |find ":" > nul
if errorlevel 1 taskkill /f /im  "arma3client.exe"
start /wait /b /high /affinity 80 F:\Games\Arma3\A3Master\arma3client.exe -client -connect=127.0.0.1 -port=2302 -profiles=F:\Games\Arma3\A3Master\BattlEye\1 -name=headlessclient
:monitor
timeout 30
tasklist /fi "imagename eq servermonitor.exe" /fi "status eq running" |find  /i "servermonitor.exe"  >nul && (
goto end
) || (
start "servermonitor" "F:\Games\Arma3\A3Files\servermonitor.exe"
)
:end
@echo Server Startup Complete
@echo Closing Down
timeout 5
exit

7
Infos & Tutorials / Re: A3 v1.58 difficulty options
« on: Apr 23, 2016, 10:43 PM »
I am unable to investigate this at the moment as I have 2 big final exams tomorrow.

School takes priority.

We are just getting abit annoyed as we are having to ask other admins/founders to login to our backend to click these ok buttons so the server restarts on time..

8
Infos & Tutorials / Re: A3 v1.58 difficulty options
« on: Apr 23, 2016, 10:21 PM »
According to your RPT, your server Arma3Profile would be located at "F:\Games\Arma3\A3Master\BattlEye\1\Users\Fractured_Server\Fractured_Server.Arma3Profile", is this the one you are editing?

That is the one we are editting, and I have deleted the file and created a new one that matches what you posted above, we also tried the new version posted on the BIStudio Wiki.

I did notice an inconsistency between my own DTA folder located in the Arma3 main directory and the one in the root directory of the server.
I deleted the folder and ran steamcmd to validate the game and it downloaded the latest version. They are identical (Old one was missing class CfgDifficultyPresets) now and the error is still appearing.

9
Infos & Tutorials / Re: A3 v1.58 difficulty options
« on: Apr 23, 2016, 09:56 PM »
I continually get this error and have to click "ok" in order for the server to restart, this puts a damper on auto restart.
Code: [Select]
No Entry
'Config.bin.CfgDifficultyPresets'

Any idea on a fix, we've been at this since the update and can't seem to figure it out.

When we delete everything it repopulates the list with the default settings as bolox listed above. The settings added are still there but still get the error for the server start up.

RPT Logs Below

Server RPT -> http://pastebin.com/yTiPZ5yZ
Headlessclient RPT -> http://pastebin.com/0d89BHHK

Issue occurs even when editting the a3config.cfg to reflect a different difficulty and it also occurs when we change the arma3profile difficulty settings to reflect the older format or the newer one.
No idea what is causing the issue.

Pages: [1]