Flosstradamus

1.68 Bugs Megathread Discussion

104 posts in this topic

EDIT: Please see this post for the temporary simulation fixes:

And see this post for fixes to the Database (player Hitpoints):

- kuplion

Preparing for the shit storm that 1.68 will cause when the update comes out next week.

Going to do things a bit differently this time around.

Please don't go off topic, derail this thread or treat people with disrespect because the fix hasn't come quick enough for you.

Will unlock when 1.68 hits :)

ONLY POST BUGS THAT ARE RELATED TO 1.68 PATCH

Follow this template:

Information:
Operating System, version?
Post your system specifications. (Hardware)
Please try to include helpful evidence related to the bug, such as screenshots and videos or pastebins for your Server .RPT(http://www.pastebin.com) 

Bug Description:
A concise description of what the problem is.  Pure description, no narrative or conversational language.

Troubleshooting/Testing Steps Attempted:
Describe anything you did to try to fix it on your own.

22 people like this

Share this post


Link to post
Share on other sites

Follow the instructions above! May the Arma Gods be with us all.

13 people like this

Share this post


Link to post
Share on other sites
Advertisement

Prior warning; off-topic posts or asking things like "why does my status bar not work" or anything else irrelevant to 'EXILE' and 1.68 will result in warning points.

6 people like this

Share this post


Link to post
Share on other sites

Posted (edited)

Having an issue with the arma3server_x64.exe.

All 3 servers refuse to unlock when ready as i've set the configs to do.
None of the servers have an RCON connection when running the 64-bit .exe.
None of the servers are being displayed on A3Launcher as being "Online" same with Gametracker, i'd expect something is broken with the Steam Query port.

Servers are running Windows Server 2012 R2 with Quad Core Xeons @3.40GHz & 16GB RAM

Included Exile.Tanoa's RPT while it was (trying to) running the 64-bit .exe Here (Nearly 1 million lines of errors generated and the server was only running for 5 mins): RPT File!

Reports of clients unable to open doors and access vehicles.

Fix for the server: Run the 32-bit client, all is okay. I will have a play with parameters too.

*EDIT*

The doors seem to work fine if you remove and replace the object. Will continue testing.

Edited by GamingAtDeathsDoor
Update

Share this post


Link to post
Share on other sites

 

14 minutes ago, Alexis said:

extDB2 not supported x64

Wait, so we need extDB3?

Share this post


Link to post
Share on other sites

Please be aware that the extDB2 database .dll we are using is not compatible with 64 Bit. We are most likely not going to upgrade to extDB3 for multiple reasons.

I advise you to stay on 32 Bit servers and go 64 Bit on the clients - as this is where it really can help.

If you think 64 Bit is like a silver bullet for you, then you can follow these instructions to upgrade to extDB3.

PS: I am curious what broke this time xD

5 people like this

Share this post


Link to post
Share on other sites

Dwarden: FYI, attention, beserver_x64.dll needs beserver_x64.cfg !!

1 person likes this

Share this post


Link to post
Share on other sites
5 minutes ago, ILLUXNNN said:

 

Wait, so we need extDB3?

Yes, you need to use extDB3, just set it up via the link below:

 

Share this post


Link to post
Share on other sites
Advertisement
Guest
This topic is now closed to further replies.

  • Recently Browsing   0 members

    No registered users viewing this page.