We've experienced substantial performance hits as well; I didn't imagine it was due to map size (256x256), but will test.
As I mentioned earlier, it is probably memory related because the 64bit client uses more memory than the 32bit client for logical reasons. The 64bit client executes faster but will perform worse if memory is a limiting factor. It can be memory bandwidth (moving data from memory to CPU), memory availability (how much memory SC2 can use before having to use virtual memory) or even cache coherency (64bit build has less cache coherency due to elements being bigger so using more cache space so fewer fit in the cache).
Again, I have 8gb of ram and two 970's.... the 64 bit client is simply not working as intended when it comes to units. I get 150+ fps on my map via the 32 bit client and 1 fps on the 64 bit client. lol
I think that any sort of negative level of "care" that Blizzard has for the Arcade (If such "negative care" even exists) will be revealed based on how they handle the contest deadline, which can be summed up via the following scenarios
1. They do not fix issues in time that broke arcade games and do not extend the contest deadline to post BlizzCon in order to compensate and maintain the integrity of the contest.
or (most probable)
2. They either fix the issues in a timely manner and/or extend the contest deadline to compensate.
If scenario 1 is what plays out (and I really hope it does not) then I personally translate that to them not valuing those who worked hard on their contest games/entries to only have them broken because of bad timing of the contest deadline and the patch.
The reason I think this will say it all is because, issues aside, Patch 3.0 is amazing and adds a lot of new features, plus the new arcade setup is infact making new/older underplayed games easier to get going.
That said, the contest is where you will find any sort of potential "not caring" because if they truly believe in the arcade, they must also believe in the contest and since the goal of the contest is to reward the best games.... how can you do that if right before the deadline a patch that was deployed broke some of them? At that point it is not about the best game, it is about who lucked out and did not have their map destroyed.
EDIT: Just to clarify so I do not end up being grouped with Blizzard haters, I personally think that Blizzard will rectify this in a way that maintains the integrity of the contest, so I am not saying that they do not "care" about the Arcade, I think they do (Patch 3.0 is a huge improvement for the Editor and Arcade imo) and they will do what needs to be done etc.
I have two 970's and 8gb of ram so its not my PC I think. Everyone who has tested the current issue with units on 64 bit reports the same thing. Also, the units DO hide but like I said, the framerate does not go up/change at all once that is done like on the 32 bit client.
Pitfall - Attachment Points on WoW models break when the unit becomes idle but fix thesmelves when turning or moving. Reimporting the model will fix it in the cutscene editor but not in game
Pitfall - Hiding Units no longer truly hides units/gives performance boosts in 64 bit clients. Basically, if your map requires lots of units (grids etc) that are hidden so as to not create performance issues, it will works on 32 bit but breaks on 64 bit. Additionally, opening maps that have this problem in the 64 bit editor will cause this issue to occur on both 32 and 64 bit clients.
When my units are not turning or moving, their attached weapons break off and just hang in the air. However, if the unit is turning or moving, the attached weapon works fine....
I like this idea, but it would have to be what/who Blizzard considered the "Best of the best" which may or may not result in some people feeling upset that they were not picked.
That said, even if I was not one of those picked, I would still like to see something like this just so arcade developers finally get some sort of top tier acknowledgement for their work.
Description
The battle between Doodads and Seekers continues...
Teams take turns hunting down Doodads as a Seeker and avoiding being caught as a Doodad. Adapt to constantly shifting shenanigans via random events that can assist or hurt the Seekers in their pursuit
FEATURES
Basic
- Three Unique Maps
- Six Seekers to choose from
- Hundreds of possible Doodads to be
In Depth
- Rather then being 100% focused on hiding, Doodad Hunt 2 is about 50% hiding and 50% escaping.
- Randomized Events can help or hurt Seekers in their pursuit to locate and kill the Doodads
- Dares give Doodads the option to be more active and rewards them with time being shaved off from the round. Thus giving the Seekers less time to achieve victory and potentially less events.
I love how even Traysent simply posting about the RTC testing event (Which they also did last year) somehow provokes people to bitch about the arcade. lol :)
Anyways, the only thing I see wrong with this is that it should be at least 2 hours. One hour was not enough last year and everyone felt very rushed which lead to little to no time for decent feedback.
If someone were to use non commonly recognized assets (abandonware) they didn't have the rights to, and a person pointed it out to Blizzard, would that be enough for Blizzard to investigate/disqualify the map, or would Blizzard require action/notice from the company/person that created the assets?
I'm just wondering if it's possible that we're going to see people trying to get each other disqualified.
Yes, they will disqualify the entry.
It is not about "trying to get each other disqualified" it's about fairness and everyone following the rules. For example, I purchased a few music licences for my entries, thus following the rules of copyright. Should someone else just go ahead and take whatever they want without going through the proper procedures of asking or buying a licence, that is totally unfair and they should be disqualified.
0
@Traysent: Go
I'll get this party started
I always get the error "There was a temporary error with your request. Please try again in a few minutes."
0
@Deadzergling: Go
It appears to be broken for the majority of people. (including myself)
0
Again, I have 8gb of ram and two 970's.... the 64 bit client is simply not working as intended when it comes to units. I get 150+ fps on my map via the 32 bit client and 1 fps on the 64 bit client. lol
0
@kelsonTD: Go
It is not due to map size, it is related to units and the 64 bit client from my tests.
0
I think that any sort of negative level of "care" that Blizzard has for the Arcade (If such "negative care" even exists) will be revealed based on how they handle the contest deadline, which can be summed up via the following scenarios
1. They do not fix issues in time that broke arcade games and do not extend the contest deadline to post BlizzCon in order to compensate and maintain the integrity of the contest.
or (most probable)
2. They either fix the issues in a timely manner and/or extend the contest deadline to compensate.
If scenario 1 is what plays out (and I really hope it does not) then I personally translate that to them not valuing those who worked hard on their contest games/entries to only have them broken because of bad timing of the contest deadline and the patch.
The reason I think this will say it all is because, issues aside, Patch 3.0 is amazing and adds a lot of new features, plus the new arcade setup is infact making new/older underplayed games easier to get going.
That said, the contest is where you will find any sort of potential "not caring" because if they truly believe in the arcade, they must also believe in the contest and since the goal of the contest is to reward the best games.... how can you do that if right before the deadline a patch that was deployed broke some of them? At that point it is not about the best game, it is about who lucked out and did not have their map destroyed.
EDIT: Just to clarify so I do not end up being grouped with Blizzard haters, I personally think that Blizzard will rectify this in a way that maintains the integrity of the contest, so I am not saying that they do not "care" about the Arcade, I think they do (Patch 3.0 is a huge improvement for the Editor and Arcade imo) and they will do what needs to be done etc.
0
@ImperialGood: Go
I have two 970's and 8gb of ram so its not my PC I think. Everyone who has tested the current issue with units on 64 bit reports the same thing. Also, the units DO hide but like I said, the framerate does not go up/change at all once that is done like on the 32 bit client.
0
Pitfall - Attachment Points on WoW models break when the unit becomes idle but fix thesmelves when turning or moving. Reimporting the model will fix it in the cutscene editor but not in game
Pitfall - Hiding Units no longer truly hides units/gives performance boosts in 64 bit clients. Basically, if your map requires lots of units (grids etc) that are hidden so as to not create performance issues, it will works on 32 bit but breaks on 64 bit. Additionally, opening maps that have this problem in the 64 bit editor will cause this issue to occur on both 32 and 64 bit clients.
0
Anyone else have their attachments break?
When my units are not turning or moving, their attached weapons break off and just hang in the air. However, if the unit is turning or moving, the attached weapon works fine....
(This is with WoW models)
0
Updated with a new video showcasing the features/content added with the Red Rum Update.
0
I like this idea, but it would have to be what/who Blizzard considered the "Best of the best" which may or may not result in some people feeling upset that they were not picked.
That said, even if I was not one of those picked, I would still like to see something like this just so arcade developers finally get some sort of top tier acknowledgement for their work.
0
Doodad Hunt 2
Created by Bounty
Model Editing by JademusSreg
Music by hakan-eriksson, ScoreStudio, FiluHalon and CyrilNikitin
NA - battlenet://starcraft/map/1/63168
EU - battlenet://starcraft/map/2/184814
Description
The battle between Doodads and Seekers continues...
Teams take turns hunting down Doodads as a Seeker and avoiding being caught as a Doodad. Adapt to constantly shifting shenanigans via random events that can assist or hurt the Seekers in their pursuit
FEATURES
Basic
- Three Unique Maps
- Six Seekers to choose from
- Hundreds of possible Doodads to be
In Depth
- Rather then being 100% focused on hiding, Doodad Hunt 2 is about 50% hiding and 50% escaping.
- Randomized Events can help or hurt Seekers in their pursuit to locate and kill the Doodads
- Dares give Doodads the option to be more active and rewards them with time being shaved off from the round. Thus giving the Seekers less time to achieve victory and potentially less events.
VIDEOS
Trailer and Gameplay Video
0
I love how even Traysent simply posting about the RTC testing event (Which they also did last year) somehow provokes people to bitch about the arcade. lol :)
Anyways, the only thing I see wrong with this is that it should be at least 2 hours. One hour was not enough last year and everyone felt very rushed which lead to little to no time for decent feedback.
0
Yes, they will disqualify the entry.
It is not about "trying to get each other disqualified" it's about fairness and everyone following the rules. For example, I purchased a few music licences for my entries, thus following the rules of copyright. Should someone else just go ahead and take whatever they want without going through the proper procedures of asking or buying a licence, that is totally unfair and they should be disqualified.
0
Shouldn't this be in the Project Workplace?
0
Watch them :)
I personally hope they enforce the rules of this contest very strictly.