Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#182Yep, lets all be patientThey've been working ever since launch to fix the bugs...I hate it when ppl expect So much from otm in such a little time, and fail to realize how hard they are working...not playing ch for a few days or a week or So isnt going to kill u...Well scrue them! They got 3 days of playing now its our time!
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#183If we keep on reporting OTM can make the engine once perfect. Once... Keepon reporting Folks!
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#184They know the problems, just give them time to sort out.If we keep on reporting OTM can make the engine once perfect. Once... Keepon reporting Folks!
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#185No there are 100000 problems and i bet they dont even know the half of it. Ifya can walk into a wall thats also a bug etc. Ifwe want it perfect we needa report every bug we see
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#1861- when i use a book of alteration to add skill points, I can't see the previous skill number, also it doesnt show how many points are from gear and how many are added by me!
New skill popup will fix these issues. It's implemented and going through the QA process.
2- when i try to type the name of a person to whisper them, if they aren't on my friend list or in area, the option does not exist anymore.
Because players can have a first and last name now you need to put a comma after the name then type your message.
3- when i equip my offhand it's invisible and the fight animation shows that I'm not using my offhand, i would have to keep switching offhands until my offhand stops being invisible and actually works
The team is aware of this bug and is working on finding a fix.
4- fortsguard tops have no texture especially the white one even though i reported it before in beta.
A fix has been put in for this it's going through QA.
5- black quartermaster eyepatch has no spakles anymore and i paid a lot of money to buy it for the sparkles.
We've had a few reports of this it's been passed over to the design team to be re-sparkled.
6- my ipod touch 4 still can't log at all same problem i encountered in beta, i would like a clear answer if my internet cannot handle this game anymore and if I'm supposed to upgrade to a faster internet with double fees.
Can you provide more details of what you mean by still can't log? We have an issue with ipv6 cellphone carriers in some territories that will be fixed when we get our networking bug sorted out.
7- it's super hard to target mobs like mordris, especially after killing a sent then going back to attack mordris, i end up just standing and trying to pointlessly target mordris while it's not working. many people had this problem too.
Going to get the team to drill into targeting issues tomorrow morning.
8- on ipad air very hard to scroll up or down my backpack and bank, everything is just super slow too.
What tabs and how many items do you have roughly in them?
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#187Hi alb I'm not sure, I will need to check with the design team tomorrow morning and get back to you.Hi so I've heard talk of there having been a mage buff along with the new engine. Supposedly energy shield was buffed and cooldown slightly reduced, damage skills also hitting harder. Is this true OTM? Patch notes?
Albericus of Herne
Lazydrunks founder
Ranger skills still broken...
Lazydrunks founder
Ranger skills still broken...
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#188We know what the problem is with this bug, once we find out from the programmers how big of a fix it is we can do a server restart to fix it. Will try to get this sorted for tomorrow.Not sure if someone has mentioned this already or not but:
The way to recreate the trade bug (The user is currently busy) is to simply talk to a vendor. If you talk to a vendor you put yourself into the bugged state and need to relog in order to trade.
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#189Sorry alb I don't have an update on that yet, I've sent a mail over to the design team will update once I get a reply.Hi alb I'm not sure, I will need to check with the design team tomorrow morning and get back to you.Hi so I've heard talk of there having been a mage buff along with the new engine. Supposedly energy shield was buffed and cooldown slightly reduced, damage skills also hitting harder. Is this true OTM? Patch notes?
Re: [FEEDBACK THREAD] iOS Destiny Engine & Yule (inc crashes
#19012/10/14 UPDATE
Hi Everyone here's today's update!
Strike teams met this morning and are continuing investigation into our critical issues. We deployed server code this afternoon to address the skill and chat lag and it looks to have fixed many of the server related lag issues, though we still have reports from some players that it's not completely gone. We are monitoring this overnight but would appreciate any further reports on skill or chat lag, please include your device if you're reporting this.
Crashing - Team has identified a number of memory improvements and are prototyping out some fixes. QA spent a good part of the day gathering performance metrics on the live game.
Server disconnecting - We've found a value on the client that will also help improve stability. It's likely that we will get an internal test version of this client tomorrow to see if it works.
Character Loading - Strike team has made good progress on this. Particles now load after characters have finished loading and we've got a handle on a few fixes that should significantly speed up rendering.
Chat - Ketesha attacks bugs with scary efficiency. The missing chat background has been restored when the chat window is closed. Copy/paste is working again but we need to sort out layout issues on various devices. Other chat differences vs. the old client have been identified such as hiding the group menu and status effect icons when the chat window is open, the height of the chat label and chat log text justification when the chat log is first opened.
Random Name Sizes - This fix is done and will be deployed in the next client release
Character Draw Distance - Still testing various character draw distance issues
Busy Character Popup - Team has identified what is causing the issue, need to implement the fix and deploy a new server
Hi Everyone here's today's update!
Strike teams met this morning and are continuing investigation into our critical issues. We deployed server code this afternoon to address the skill and chat lag and it looks to have fixed many of the server related lag issues, though we still have reports from some players that it's not completely gone. We are monitoring this overnight but would appreciate any further reports on skill or chat lag, please include your device if you're reporting this.
Crashing - Team has identified a number of memory improvements and are prototyping out some fixes. QA spent a good part of the day gathering performance metrics on the live game.
Server disconnecting - We've found a value on the client that will also help improve stability. It's likely that we will get an internal test version of this client tomorrow to see if it works.
Character Loading - Strike team has made good progress on this. Particles now load after characters have finished loading and we've got a handle on a few fixes that should significantly speed up rendering.
Chat - Ketesha attacks bugs with scary efficiency. The missing chat background has been restored when the chat window is closed. Copy/paste is working again but we need to sort out layout issues on various devices. Other chat differences vs. the old client have been identified such as hiding the group menu and status effect icons when the chat window is open, the height of the chat label and chat log text justification when the chat log is first opened.
Random Name Sizes - This fix is done and will be deployed in the next client release
Character Draw Distance - Still testing various character draw distance issues
Busy Character Popup - Team has identified what is causing the issue, need to implement the fix and deploy a new server