I'm not taking sides here but easy fix or not, what if I like using my windows key? this should even be an issue to begin with.
Funny and true all rolled into one brilliant comment, you sir win my day /swoon.
Taken from a post on my LS site- you will enjoy the humor :)
Arcanist basically sounds like a WoW shaman only with the typical infuriating japanese UI hoops you gotta jump through.
Create Distaff
Are you sure you want to create a Distaff? Y/N
Animate Distaff
AoE Distaff? Y/N
Your target is too far below you
LOL! Best use of sarcasm ever.
It's reasons like this we shouldn't just be quiet and find 3rd party workarounds. How else is SE going to realize this isn't acceptable programming until we point it out? Obviously they have no idea, or else they would have improved upon these glaring issues leftover from FFXI.
Oh, wow, Griss, thanks! I'm embarrassed to admit I didn't know I could turn that feature off. It's been driving me nuts because I don't like computers telling me what they think I should do (hence why I'm a Mac hater). Now I can arrange my windows however I like, and not get them shoved downward!
This does make my FFXIV experience (and Windows experience) slightly better. Thanks. :D
P.S. However, still doesn't change the fact that SE needs to fix the DirectX issue so I can play in full screen again. >.<
The thing is what are you going to do next, disable alt-tab? Why don't you just advise everyone to disable all 3 or 4 systems in Windows 7 so they don't accidentally hit a button on the keyboard that CRASHES THE GAME. I'm good; as I have said. Newcomers can't be expected to go through all this technicality to get the game running. They wouldn't even think of coming onto the forums.
lol.. sad, but true.
lmao. Great post. Yeah doom and doom 2 had separate configs. I see SE has learned well. Excellent first post sir. Looking forward to more of your work in the future.
lol'd hard @ that.
Perhaps you are just unclear as to the purpose of this thread. I created a bug report because no other bug report had been submitted. Then a forum moderator moved it onto this forum for general discussion. It's reasonable to expect quality software that doesn't crash when you press a button on the keyboard.
you dont seem to understand, this was moved to the general topics specifically to garner this type of feedback,.
that moderator probably feels the same way but cant do much unless he presents threads like this to his bosses/developers.
i went to the FFXI convention in anaheim and the developers literally answered a few questions with "we just didnt think anyone cared about ____ so we never added it"
even more relovant, during beta the forums were open for feed back and feedback only, to report bugs and request other types of features and fixes. well anyone from beta should be able to remember Tanaka word for word telling the developers "just ignore them, they dont know what they are talking about, this is how the internet works. complete plans as normal"
im not exaggurating and if your from beta you should easily remember that AND when Tanaka literally blamed the western himisphere for ruining ..... damnit cant remember but it literally said its all westerners fault and it was a big ordeal on ZAM...
idk, my whole point is that i think some things actually need to be shoved in SEs face until they change it.
If that's your idea of an easy fix, I'm glad you never became a surgeon.
I believe the underlying problem stems from SE's console development methodology. One of the reasons Vista required DX10 is because the Aero stuff required use of Direct3D to render screen components, and prior to DX10, D3D only allowed one application to access the framebuffer via D3D at any time. Essentially, the game (or more likely Crystal Tools) has a poorly-constructed rendering engine which is trying to write frame data regardless of the state of the application. For example - a well-designed game shouldn't be trying to draw frames while minimized, as those frames are going to simply be discarded, but yet it does.
The error we're seeing here is not unlike a null pointer exception, actually. The previous device doesn't exist anymore and the engine is continuing to try to write updates to it.
Had Crystal Tools isolated the rendering engine from the game application itself, as would be desireable for having the ability to effect run-time graphics option changes, then I suspect this problem would be much easier for them to fix...but I think ultimately it shows a fundamental misunderstanding of how to do proper PC development.