As a regular mouse, yes but the macro functionality doesn't work as of two weeks ago.
Printable View
woah keyboard and mouse support for ps4? THANKS SE
Even thou I play on pc. I brought the ps3 version just for the artbook that was in the collectors edition. the ps3 version is horrible to play on. thank god they gave us the free upgrade to ps4. even thou I was thinking of buying the collectors edition again for the ps4.
And this was my plan all along.
Thanks for sharing :D
hmm if DoH or DoL ever become much more viable, the Vita looks like it might be worth looking into.
Unless Sony changes stance and allows you to install software that isn't a PS4 game then keyboard and mouse macro buttons won't ever be usable. The system won't recognize extra keys without drivers specific to the hardware nevermind software to program the macros. Not much point in getting a full blown gaming KB and mouse for PS4.
While true, at least they don't have investors who don't give a shit except about the $ who aren't even affiliated with SE.
As far as I know, the only people they need to please as far as business and profits is people within their own company. Which IMO is a great advantage. Can also be a great disaster waiting to happen, but since ARR has essentially saved SE financially, I don't think they'll be willin to give the game up anytime soon.
Which is good news for us consumers as that means they will strive to bring out quality to keep us active.
Well yes, most new PS4 games coming out will be running full 1080p at 60 fps
So this is obviously a choice SE has made, the PS4 hardware is well capable of running it at a higher framerate
Oh and it has already been confirmed PS4 will have full mouse and keyboard support.
I for one am just excited to try the beta soon :D
Watched the trailer and honestly, it didn't look much different from what I play now. On the PS3. Only neat thing I saw was the Vita remote play, but it's not something to get a Vita over. Nor is this a game worth getting a PS4 over. I'm not impressed. I'm going to keep playing on a PS3 for now. Maybe when a must-have title makes me get a PS4 I'll jump the shark.
The only thing im looking foreward to with the ps4 launch is the promise of DX11 support for pc, which is what we were told would happen with the ps4 launch.
I want Dx11 :(
I just hope people are prepared to see that DX11 will not be fully utilized when it comes. I remember in one of the interviews Yoshi stating that they will only be using certain aspects of DX11, and things such as textures will not be improved upon.
.... what exactly were you expecting? Its FFXIV at higher settings and better FPS. I wouldnt get a PS4 or a Vita for FFXIV either but you will definitely notice better performance. The graphical upgrades will likely be subtle so youll have to look closer to notice them (more foliage, better less jagged shadows, more detailed reflactions from more sources, etc). PS3 is way overset (hence the almost unplayable FPS) but unless you have a more powerful PS3 than everyone else, youll at least notice much smoother motion (FPS).
Glad they decided to support keyboards, and the Vita thing should be interesting.
Greetings, everyone.
As there have been some comments and questions about the migration of saved data from the PS3 version to the PS4 version, I'd like to share the below comments from Hiroshi Minagawa about this topic.
Hmmm..
- PS3 version is 30 frames of 720p fixed, but I can play comfortably at 60 frame 1080p display of the PS4 version?
Mr. Yoshida: Yes. They do not want to limit too much the frame.
- In the PS3 version, from memory limit, there is also a limit to the display, such as the number of characters In addition, the limit of that area is also more loosely the PS4 version?
: Mr. Yoshida I referenced to the PC version.
http://game.watch.impress.co.jp/docs...21_616332.html
(used Chrome's built-in translator)
Some of this information is more important than the rest. For instance, it's not really that big of a deal of the positions of items in our bags don't carry over from machine to machine (we can hit sort to fix that). By contrast, the fact that gearsets don't carry over is a massive quality of life inconvenience. I am constantly having to update gearsets between machines.
It seems to me that storing this player data on an FFXIV server is being considered to be an all or nothing approach. It shouldn't be. Consider storing some of the more painful aspects of character data (gearsets first, hotbars a close second) first, and don't worry about doing the things that are just tangential improvements. You could give us 80% of the benefit here for 20% of the cost.
The thing that's the bulk of the information is what you're asking for, gear sets and hot bars.
The maximum size that they'd have to support(which is the problem) is 40 characters per account X 30 different gearsets (It can go higher it's just how many I know I have) X 14 different equips per gear set X 100 different hot bar skills(10 hotbars available with 10 skills per) meaning that 1 character takes 1.68 GB just for that information(assuming each piece of that information is 1 byte and its probably more than that) and since 60mil+ chars have been created so far that means to store that data just right now you'd need a min of 100.8 TB of storage.
Oh and before someone jumps on me for saying it's only 100 TB SE could afford that easily each of those things are probably 100 bytes minimum meaning the actual size would be closer to 10 PB.
Yeah.... SO?
Why a 10 hour maintenance on the 19th, IMMEDIATELY following a 3 hour maintenance on the 14th, to put in "support" for the PS4, for whom the version is not due to be released for yet another month?
Ridiculous I say!
It's not just a PlayStation 4 support they are adding it's also patch 2.16 and the addition of support makes sense since the beta starts on Saturday that week next week. Btw the update on the 14 is 2 hrs not 3 and might even be less then 2.
http://cdn.dualshockers.com/wp-conte...4-13_21_18.jpg
Yes
Only PS4 support in 2.16
I wish they would not put retainer bells in Revenant's Toll. There would be now more people. Gridania is only 5 minutes away with chocobo.
That's not how it works. I work in a datacenter. Compression is impossible, a file compressed can be used unless the data your compressing needs to be referenced or updated(each time it did would require an un-compress then re-compress meaning you need to save space for the files expansion). so compression is a no go. plus the additional IO and transfer of data to read all this data that updates if you move any icon, switch any item and so on would be bad practice. for example. websites cache stuff locally to a browser to stop the front end from having to constantly query the backend database.
so to list a few flaws in storing the data on a server in a data center.
-additional monthly cost from data center to "store" data.
-additional IO that would require additional monthly fees to provide from data center.
-new design to support the amount of database queries to all clients simultaneously
#Data centers charge by the GB of space. getting 10PB would likely cost more per month then most of you make in a year.
Data center storage is not cheap... this is not paying 30 dollars for a 1TB drive. Server storage is on a whole different level and is not cheap.
Not saying its not possible. just this is done by design and not later. it could call for recoded server structure. the easiest way would be to limit what is saved. Like TERA who keep a small config file that gets pulled down locally and updated when modified and sent to server. though what they save is very limited.
Not saying that you are wrong - quite the opposite - but there are a few ways to mitigate the storage space dilemma. They could store a diff file, for instance. If I were to make a gross guess, very few users actually make many changes to their macros or have many gear sets. As such, if you store only the users' alterations, rather than the individual data itself, you could drastically reduce the overhead. Depending on the format of the diff file, you could quickly and efficiently load macro and setting changes without permuting TBs of data. That's a pretty superficial improvement though.
On a a more abstract level, you could use a flyweight to enumerate commonalities between gear sets. If two people have the same gear set, you can use 16 bytes instead of 28, if 3 people use the same gear set, that goes to 17:42. Hotbars are the real sticking point, there's only so many ways to visualize that data. The issue is that hotbars are too general-purpose, abilities would be easy enough to map, but macros, gear sets, and emotes greatly increase the range of data that needs to be available. Best case scenario is the number of hotbar items * 2 bytes + 4 bytes (for region markers so that you can overload bits).
Bottom line, with a few clever data permutations, in the end, you're going to end up with ~6kB (assuming 2 bytes per item) per character for hotbars and 1.7kB (assuming 4 bytes per item) per character for gearsets. Of course, since you're assuming macros are static resources, you'll have to make those available as well, that's another 40 bytes (4 byte command * number of lines) per macro, so plop on another 4kB on the front. So call it a cool 22kB per character.
To use the number (which I am not sure where it comes from, but I'll keep things consistent) stated above, if there are 60 million accounts - active and inactive - you would spend ~1.32TB of space storing the data server side. Please by all means check my math, I do have a bad habit of loosing orders of magnitude form time to time, but I have gone over these numbers quite few times now, and I'm fairly confident in them.
It's worth noting that you could substantially reduce the bandwidth strain as well by only downloading and uploading the file on session creation and session deletion. It would cause occasional funkiness, such as when you crash after writing a new macro, but it would not effect the discussion at hand, which is transferring data to a new device. You could also mitigate the above by making downloads only constructive, while uploads are both constructive and destructive. That way you wouldn't lose new macros on a crash, but they wouldn't appear on new machines until you correctly shut down.
Your math is quite far off the mark, first because you multiplied by the maximum number of characters someone could have and then gave the result as "per character", and secondly because you multiplied the gearset information times the number of hotbar slots.
So instead of: 40 * 30 * 14 * 100 * 60mil = 100.8 TB
it would be: ((30 * 14) + 100) * 60mil = 31.2 GB
Now, as you said, some of that info may have more than one byte, so the real amount could be significantly higher than 31.2 GB, but it wouldn't be anywhere near 100 TB, nor even 1 TB for that matter.
The hotbar slots would each hold the ID number of either a skill, an item, or a macro slot. Even if the ID numbers they use are 64 bit, that's only 8 bytes, and they're more likely to be 32 bits, or 4 bytes each, since that would still provide more than enough unique ID numbers for the number of skills and items likely to ever be in the game.
The gear set slots hold an item ID and a dye color ID. (They don't store the rest of the details about an item. If you have two items of the same type and color, switching to the gear set will take whichever is currently stored first in your armoury chest.) That's only two numbers, probably 4 or at most 8 bytes for the item ID and one byte for the color.
So assuming the most likely 5 bytes per gearset item and 4 bytes per hotbar slot, along with your numbers from earlier we get:
((30 gearsets * 14 items * 5 bytes) + (100 hotbar slots * 4 bytes)) * 60mil characters = 150 GB total
or if the ID numbers are 64 bit, it would be:
((30 gearsets * 14 items * 9 bytes) + (100 hotbar slots * 8 bytes)) * 60mil characters = 274.8 GB total
You're assuming the pieces would be updated individually in real-time. That would be one option, but a far more cost effective one would be to update the entire structure just once at logout.
We're way off topic at this point, but I just wanted to point out that you forgot that the new system coming out next update prioritizes by the correct materia, so it need materia info as well, so append another 5 bytes on there. Also, remember that each gear set has its own hotbar sets, so it's not ((30 * 14) + 100) * 60mil = 31.2 GB, but (30 * (14 + 100)) * 60 mil = 205.2 GB.Quote:
Originally Posted by Niwashi
Ah, I didn't know about that. Nice.
That's partially right (and closer to right than I was in my previous post). Gear sets don't have their own hotbar slots, but classes and jobs do, so with 19 classes and 9 jobs it would be
((30 * 14) + (28 * 100)) * 60mil = 193.2 GB
and with reasonable sizes added (including that extra 5 bytes for materia you mentioned for the next update) it comes to:
((30 gearsets * 14 items * 10 bytes) + (28 classes&jobs * 100 hotbar slots * 4 bytes)) * 60mil characters = 924 GB total
So it could be getting near the 1 TB level if every character ever created has all 19 classes, all 9 jobs, and all possible hotbars enabled and class/job specific. If they only store the parts that are actually in use, though, they'd probably save most of that space due to characters without all the classes and jobs, or who only use a couple hotbars for some of their classes. That pattern just needs a small overhead for marking which pieces are in use and which aren't.
dat meteor wipe on king behemoth lol