Westford

This. I have heard through the rumorville, that accounts are getting banned for using AutoIt, AHK and whatnot. Triggerbots, no-recoil and such. Those players got a 3 day temp ban and subsequently a permanent ban. This is not related to the OP's situation, as he has a new laptop. Not sure what the Make and Model is, hopefully he gets this resolved with support.

Is it ? Or did LO have all of the appropriate monitoring tools in place to capture issues, anomalies and crashes ? If they did , good for them, This influx of players definitely tested this new system. YEAH... mission accomplished. They already said that this Test uncovered "critical issues". YEAH ... mission accomplished. Was the expectations of those that participated in this "Test" , thought that this was "Play" time ? Well that would be unrealistic. Predictions into an unknown, is just that. Unknown... But they knew what the population might be with this beta ... Yes, based off of a UE 3.0 (32bit server & 32bit client) with custom code that has been replaced to work with the 64bit env and UE 3.5. I disagree that nothing good came from this test. They found critical issues during this test. YEAH ... mission accomplished. Yes,, yes , many player wanted to "play" , and were very disappointed. Some, even angry ... But testing the functionality of District play time has to first pass the other Application layers. Login World Server ..and then we play and report "those" bugs. I am curious,., when we do get to Test District play time, and there will be bugs, will we see the same level of outrage... ? I have no predictions ,,

You seems to be still biting on the "stress test " Not at all. I'm not pushing Stress test or anything specific, you are. You see today's test as a failure. You were disappointed, maybe even angry. I get it. Get over it. And do not set yourself up for disappointment in the future. Wait for the live release of the Engine Upgrade. You will be much happier. Cheers

Well, you seem to know what you're talking about, so I will have to stop here. I will add one small suggestion. The next time LO has a Beta test, you might want to sit that one out.

You really have know idea. Seriously, there is no cure for you my friend. Either you understand Application Testing or you don't. Not everyone does, give yourself a break. Oh, and by the way, Performance Testing is not the same as Stress Testing, is not the same as Unit Testing is not the same as System Testing.

"predict the stress(POP)" I'm sure they did. Based on a UE 3.0 config (32bit server & 32bit Client) Guess What ? It Didn't Work. But why didn't it work for a UE 3.5 (64bit server & 64bit Client) ? Perhaps it had something to do with a completely different application ? Ya think ?

I posted this in another thread, but I thought it would be helpful to post this here as well, for the benefit of those "who have little knowledge" about Application Testing. ___________________________________________________________________________________________ I think some people might be missing the point of this open Beta test. Yeah, it would have been great if we could have connected to a district and test the game. So instead, we are stress testing the application layers that allow us to connect to a district. Login Server - (Application layer) World Server - (Application layer) District - (Application layer) The dev team only ever had more than a handful of testers connecting concurrently on their test servers. Not 100+ players trying to connect. So the benefits of today's test is to isolate root cause at the different application layers. I only connected to the District select screen once after multiple tries. Once these issues are resolved, they'll have another Beta test where we can test the game. For those that are expecting a finished product, play the currently released game.

I know.... I know. I hate myself.

We get it , you're a gamer. You were expecting to play a game that is finished. You goofed and stumbled onto a Beta Test server. My suggestion, play the currently released product, and leave the testing to those who's expectations are in check.

Not sure why someone thought my comment was funny, I was being serious. What happened today is what you do to test a system. How else to you stress test the different application layers, with 4 or 5 people ? /shrug

Glad we could help with the Stress Test. I look forward to the next open Beta test. Thanks

I think some people might be missing the point of this open Beta test. Yeah, it would have been great if we could have connected to a district and test the game. So instead, we are stress testing the application layers that allow us to connect to a district. Login Server - (Application layer) World Server - (Application layer) District - (Application layer) The dev team only ever had more than a handful of testers connecting concurrently on their test servers. Not 100+ players trying to connect. So the benefits of today's test is to isolate root cause at the different application layers. just my opinion I only connected to the District select screen once after multiple tries. Once these issues are resolved, they'll have another Beta test where we can test the game.

Got past the Error on Login. Got Past initial Disconnects. Selected connection to Asylum, As I was loading into Asylum, message read "Exiting District: Asylum" After 5 min of waiting, ERROR / World Server Disconnected I'll wait about 30min and try again.

Until the new engine comes out , and restrictions to custom crosshairs that bypasses the "in-game" bloom mechanics, I choose to use Custom Crosshairs. This will be great. Thank you. I will have an advantage, and maybe that is all I need.

Hmmm... So I would no longer rely on the "in-game" cross hair turning Red (because of crosshair Bloom) , but I could effectively stay on target with the custom crosshair ? I choose the custom crosshair. My eye sight is good. Enemy is in my sights. And no, I do not care if I have an advantage.. I think I said that right ...