Zwillinger
-
Posts
1715 -
Joined
-
Quote:Apologies for not mentioning it in the OP.Originally Posted by GATE-keeper
Since I didn't see it mentioned, I guess we're stuck with the knockback bug? (or should I say "lack of knockback" bug)
We're still investigating it, but the current theory is that an update with the PhysX code is the culprit in this particular issue. Again, we're still digging through the code, so nothing concrete yet, but that's our current suspicion. -
Quote:I think it's Grrrrrrrrroovy. Just doggone grrrrrroovy.Originally Posted by terrible_deli
So we're getting something nice in the store tomorrow then?
-
We're constantly exploring many designs for possible implementation. In this particular case, we don't have any current plans on implementing this feature, and it showing on the vendor was a bug (if you look at the tooltip, it's obviously WIP).
While I love to see you guys theorize and speculate
, I also believe it's important to set appropriate expectations. In this case, do not expect to see this feature in the immediate future.
-
I've got an update about some of the live issues we're currently following up on. We have great news and not as great news (depending on your perspective...I know that some of you will be stoked about the not as great news).
First the good news! With tomorrow's build (we'll have patch notes up tomorrow, or you can check out the beta notes) several issue introduced in last Thursday's patch will be resolved:- Resetting UI bug corrected.
- ATI/AMD Driver Lock out issue resolved.
- Organic Armor will glow again.
- Vanessa DeVore will once again leave the day to day missions to her underlings.
- The Mission Architect rating window should once again function properly.
- Manticore's Poison Gas Arrow will stop preventing Villains from completing SSA Chapter 3.
- The issue which was causing VG Bases to attack players has spread via the Paragon City internet to SG bases, causing Hero side bases with defensive objects to be...defensive...against Heros. Note, this isn't live yet, however it will start happening after tomorrow's publish. So please, if you don't want your base attacking you, remove these defensive objects from your base. While I know that some of you will enjoy this bug, there will be some who do not appreciate the sudden base related aggression. To those who may be upset by this development, we sincerely apologize.
Thanks for bearing with us as we work through these live issues.
-Z
Join the Community Discussion. -
I've got an update about some of the live issues we're currently following up on. We have great news and not as great news (depending on your perspective...I know that some of you will be stoked about the not as great news).
First the good news! With tomorrow's build (we'll have patch notes up tomorrow, or you can check out the beta notes) several issue introduced in last Thursday's patch will be resolved:- Resetting UI bug corrected.
- ATI/AMD Driver Lock out issue resolved.
- Organic Armor will glow again.
- Vanessa DeVore will once again leave the day to day missions to her underlings.
- The Mission Architect rating window should once again function properly.
- Manticore's Poison Gas Arrow will stop preventing Villains from completing SSA Chapter 3.
- The issue which was causing VG Bases to attack players has spread via the Paragon City internet to SG bases, causing Hero side bases with defensive objects to be...defensive...against Heros. Note, this isn't live yet, however it will start happening after tomorrow's publish. So please, if you don't want your base attacking you, remove these defensive objects from your base. While I know that some of you will enjoy this bug, there will be some who do not appreciate the sudden base related aggression. To those who may be upset by this development, we sincerely apologize.
Thanks for bearing with us as we work through these live issues.
-Z -
Quote:To clarify,Originally Posted by Eldorado
Oh, and it's because apparently nobody from QA was assigned to read bug reports from beta, according to one Zwillinger post...
I stated noone from QA currently posts in the forums acknowledging bug reports as received.
Someone from QA reads the forums each and every working night and sends out a report of bugs. -
Updated the OP with some information that may help to alleviate the UI issue. It's not a complete work around, but it should help.
-
Quote:Thanks for pointing that one out.Originally Posted by Necrotron_RO
Also, high priority bug worth noting.
In the first mission of the Signature Story Arc #3, Manticore's Poison Gas Arrow (pet) will not dissipate after he dies, making it impossible to release the hostage Alexis Cole-Duncan, and impossible to complete the mission.
This is indeed considered high priority. -
So to start things off, please always be sure to check the Live Issues thread. We update this regularly with verified issues anytime we have a major publish. Here's the one for Issue 21.
Thank you to everyone for bearing with us as we've been dealing with these issues. I know that a few of them are particularly annoying (UI Bug) so your patience is appreciated.
So everyone is aware, the current high priority live issues we're working on immediate fixes for are:- Base Defense items in Villaingroup Bases are able to attack players, and can likewise be attacked by players.
- Missions using Carnival of Shadows critters may have Venessa DeVore spawns (Elite Boss) making them more difficult than intended.
- For some players the User Interface is resetting after the game client is closed.
- Some players using specific laptop models using AMD drivers are unable to successfully launch the game client.
- An issue is preventing some players from completing the Villain Signature Story Arc #3.
Unfortunately we're unable to publish fixes for these issues to live today, so the earliest we will see any potential fixes will be next Tuesday, 11/15.
Again, our apologies for the effect these or other bugs may be having on your play experience and thanks for your patience.
Update: For those experiencing the UI Issue: One possible work around is as follows:
Configure your UI.
Type /wdwsave
When it resets type /wdwload
You may have to do this repeatedly, so you may wish to create a macro, as follows:
/macro <NAME> wdwload
for example
/macro ANNOYINGBUG wdwload
Hope that helps! -
So to start things off, please always be sure to check the Live Issues thread. We update this regularly with verified issues anytime we have a major publish. Here's the one for Issue 21.
Thank you to everyone for bearing with us as we've been dealing with these issues. I know that a few of them are particularly annoying (UI Bug) so your patience is appreciated.
So everyone is aware, the current high priority live issues we're working on immediate fixes for are:- Base Defense items in Villaingroup Bases are able to attack players, and can likewise be attacked by players.
- Missions using Carnival of Shadows critters may have Venessa DeVore spawns (Elite Boss) making them more difficult than intended.
- For some players the User Interface is resetting after the game client is closed.
- Some players using specific laptop models using AMD drivers are unable to successfully launch the game client.
Unfortunately we're unable to publish fixes for these issues to live today, so the earliest we will see any potential fixes will be next Tuesday, 11/15.
Again, our apologies for the effect these or other bugs may be having on your play experience and thanks for your patience.
Join the Community Discussion Here. -
Quote:Yes, it is a different person entirely.Originally Posted by Xanatos
So the person updating the Paragon Store interface is different from the person that updates the UI interface?
Ok. Sure. Sounds believable. -
If any of you happen to be *very advanced users* (i.e.; you know your way around a computer extremely well) some information that would be helpful for us to pass along to AMD for debugging would be:
WARNING: DO NOT ATTEMPT THIS IF YOU ARE NOT AN ADVANCED WINDOWS USER. WE DO NOT WANT YOU TO BREAK YOUR COMPUTER.
- Set Write debugging information to Small memory dump when a bluescreen of death occurs. This is located under the Advanced System Settings menu on Windows 7.
- Update the System Restore point so Windows can revert back to before the buggy driver installation.
- Install the newer AMD drivers and let the operating system blue screen. Wait until it finishes writing the minidump file in the C:\windows\Minidump directory.
- Load from the saved System Restore point to revert back to the previous driver.
- Email cohcommunity@paragonstudios.com with the resultant file. We'll forward that on to AMD.
-
Update 11/11/11: There will be no maintenance today. We will be performing maintenance on Tuesday. Please keep an eye out for a news announcement very soon for more details.
-
We've identified this issue internally, and are working on a fix. At the moment I don't have an official ETR, however I would expect it very soon.
-
Quote:Worked on.Originally Posted by Stalk_obot_EU
Worked for, subtle difference I know but you are not a developer now are you?
I have always been a Community Manager in a development studio, never in a publishing house.
Do I touch the code? No.
Does OCR contribute to the development of the game? Yes. -
Quote:To put it succinctly, on every MMO I've worked on, that count is up to 4 now, the words Rollback also mean a loss of customer progression from the current time stamp to the point of restoration. This means the loss of every item/loot dropped, any experience or levels, any achievement earned...you get the point.Originally Posted by AmazingMOO
I'm not saying your qualifications for what necessitates a Rollback are wrong or inadequate, but If my customers were to start asking, 'Why is my UI suddenly broken?', I'd personally roll back a production build back on that qualification alone. I'm not trying to grief you, Z or the devs, so please don't take it that.
Adding in the other bugs, which are at least character breaking if not game-breaking, it seems like a straightforward decision.
I know that when I make major changes in a production environment, I keep a spreadsheet of essential steps necessary to back out a change. (This is usually reviewed a few times and gets devs, operators, and at least one manager to sign off on it.) Perhaps its time to consult such a spreadsheet if you guys have one?
Hopefully you didn't make any irreversible database changes?
I heard other folks on Victory trying to figure out how to reload their last window configuration. If you don't roll back, I would at the VERY least, set the GMOTD with instructions on how to reload their saved window configuration.
-- Edit --
I just read the 'Possible Maintenance' post, Z. Thank you for announcing that!
Again, I apologize if I sound like I'm howling. I'm certain you guys are getting it from all directions this evening and that it's as frustrating for you as it is for everyone else.
In Game Development, because there are so many intertwined customer facing systems, there is rarely an elegant way to go in and completely pull out a feature or change. They can sometimes be disabled with a server side client command, but rarely, and I mean rarely, can they just be pulled out like a proverbial hair in the soup without significant risk.
When I tell you that a Rollback is srs bsnss, I'm not kidding.
And no, you're not howling. Questions are to be expected. -
This is a bit outside the normal structure and format in which we post maintenance notifications, however we felt that the Community should know that there is a strong possibility we will be performing a live server maintenance tomorrow afternoon (CST)/evening (GMT) to address some high priority issues prior to the weekend.
As soon as we have an exact schedule we will be certain to let you all know what that is.
Thanks for your patience and our sincere apologies for the possibility of unplanned downtime. -
Quote:I'm not saying everythings peachy keen, because there's certainly some serious issues, however it's not quite Rollback severity.Originally Posted by AmazingMOO
Seriously, this is a roll-back quality patch, even with the trial changes. Roll it back and push the 'Future Build' version when it's ready. In many ways, the game is broken beyond playability for a LOT of characters.
The word Rollback has very, very serious implications when you're talking about a live product. -
Quote:A version of VD was, for lack of a better term, miscategorized, causing this to happen.Originally Posted by Goliath Bird Eater
This was something that was happening on the beta server, and that I *believe* was reported. I was part of a foursome of Titan Weapon characters of various levels that were running radio missions in Peregrine Island. On two separate Carnie radio missions, Vanessa appeared multiple times as an Elite Boss spawn. I'm not sure WHY a EB would be spawning on a radio mission, but she was, and often. No EBs spawned during radio missions with other enemy factions.
We should have it fixed in an upcoming build. -
Quote:Edit: This is, as of this afternoon, a verified issue (we'll have a known issues list going up soon).Originally Posted by Psychoti
Vanessa DeVore seems to be set as a regular Carnival of Shadows enemy now. Doing a regular radio mission in PI I fought her 4 times in different enemy spawns. Kinda ridiculous.
And apparently Carnies have a higher-mag hold now? Getting held pretty quickly on my brute.
Thanks for the report -
Quote:We certainly will not turn you away at the door if you're wearing a cape.Originally Posted by crayhal
Would anyone know if cosplay is allowed? Just wondering if I can get out my cape...
-
Thanks guys,
I've forwarded the Knockback issue along. -
Quote:Can anyone else confirm that this is occurring for them?Originally Posted by Moonshires
...
Seriously, 2 maybe 3 feet is all anything is knocked back now. That's not enough to get most things out of melee range.... -
I had my weekly call with the web ops team this afternoon.
- The random log out bug has been clearly defined to Seattle as something that needs to be addressed ASAP.
- The issues with the Hero Skin has been clearly defined as something that needs to be addressed ASAP.
- The cookie to flag you to log out due to inactivity is currently set to expire at 1 hour. This is, IMHO, a bit short. Originally, I had requested that the log out due to inactivity be set to 14 days. This caused some rather bad things to happen which resulted in the forums crashing over the weekend. We'll be setting it back to 8 hours soon. To be clear: If you are inactive on the forums for 8 hours you will be logged out.
More as I have it.
-Z -
Quote:Many, most, changes we make require us to make an entirely new build (i.e. version) of the game. These builds require hours to compile here at Paragon, many more hours to transfer to Austin (we can't just email them), and even more hours on the Ops side to actually apply to the live server and then QA Smoke test. This process has to be planned out well in advance, quite literally weeks, and when we have to implement an immediate build, it puts the breaks on for every other thing surrounding it.Originally Posted by rsclark
Honestly, is that sentence meant to be in English? I have absolutely no clue what you are trying to say. "The West"? What?
"Require a new build"? Huh? Did you just imply a non-released bug could not be fixed?
You need to explain yourself better.
This applies to all build publishes, not just what you see on live servers.
That being said, we will possibly have a build tomorrow to address this, and other, issues which we believe warrant immediate resolution.