-->
110dx Electronic Cash Register Instruction Manual 8 Departments 99 PLU’s (Price Look-Ups) 4 Clerks Automatic Tax Computation – with 4 Tax Tables (Including Add-on (USA), Canadian and VAT) Programmable Electronic Cash Register Easy Set-Up Instructions QUICK START GUIDE on Page 12. It's probably not there because DirectX didn't install properly. DirectX 10.0 comes with Vista and 10.1 comes with SP1 for Vista (there is also an enhancement in SP2). If you have Vista (any Version) you should already have DirectX 10.0 (at least) and 10.1 if you downloaded SP1.
This document lists the error codes used by Direct2D. The Direct2D Error Handling Policies topic has more info on handling errors like these.
Constant/value | Description |
---|---|
| The number is invalid. |
| You can't draw with a bitmap that is currently bound as the target bitmap. |
| You can't draw with a bitmap that has the D2D1_BITMAP_OPTIONS_CANNOT_DRAW option. |
| A cycle occurred in the graph. |
| The display format to render is not supported by the hardware device. |
| A valid display state could not be determined. |
| The class ID of the specified effect is not registered by the operating system. |
| The requested size is larger than the guaranteed supported texture size. |
| The brush types are incompatible for the call. |
| The supplied buffer is too small to accommodate the data. |
| The Direct3D device doesn't have sufficient capabilities to perform the requested action. |
| You can't render the graph with the context's current tiling settings. |
| The application should close this instance of Direct2D and restart it as a new process. |
| A call to this method is invalid. |
| A configuration error occurred in the graph. |
| An internal configuration error occurred in the graph. |
| The specified property doesn't exist. |
| You can't set the image as a target because it is either an effect or a bitmap that doesn't have the D2D1_BITMAP_OPTIONS_TARGET option. |
| The application attempted to reuse a layer resource that has not yet been popped off the stack. |
| The requested DX surface size exceeds the maximum texture size. |
| There is no hardware rendering device available for this operation. |
| The specified sub-property doesn't exist. |
| The object has not yet been initialized. |
| The operation failed because the original target isn't currently bound as a target. |
| The operation can't complete while you have outstanding references to the target bitmap. |
| The application attempted to pop a layer off the stack when a clip was at the top, or pop a clip off the stack when a layer was at the top. |
| This error occurs during print control creation (ID2D1Device::CreatePrintControl) to indicate that the Direct2D print control (ID2D1PrintControl) can't support any of the package target types that represent printer formats. |
| The application called ID2D1PrintControl::AddPage or ID2D1PrintControl::Close after the print job is already finished. |
| The application did not pop all clips and layers off the stack, or it attempted to pop too many clips or layers off the stack. |
| A presentation error has occurred that may be recoverable. The caller needs to re-create the render target then attempt to render the frame again. |
| The requested operation cannot be performed until all layers and clips have been popped off the stack. |
| The geometry scanner failed to process the data. |
| Direct2D could not access the screen. |
| Shader compilation failed. |
| The render target is not compatible with GDI. |
| A text client drawing effect object is of the wrong type. |
| An application is holding a reference to the IDWriteTextRenderer interface after the corresponding DrawTextor DrawTextLayout call has returned. |
| Shader construction failed because it was too complex. |
| An effect attempted to use a transform with too many inputs. |
| The requested operation is not supported. |
| The pixel format is not supported. |
| The requested Direct2D version is not supported. |
| An unknown Win32 failure occurred. |
| Objects used together were not all created from the same factory instance. |
| The resource used was created by a render target in a different resource domain. |
| The object was not in the correct state to process the method. |
| The supplied vector is zero. |
Requirements
Minimum supported client | Windows 7, Windows Vista with SP2 and Platform Update for Windows Vista [desktop apps only] |
Minimum supported server | Windows Server 2008 R2, Windows Server 2008 with SP2 and Platform Update for Windows Server 2008 [desktop apps only] |
Minimum supported phone | Windows Phone 8.1 [Windows Phone Silverlight 8.1 and Windows Runtime apps] |
Header |
|
Posted by4 years ago
Archived
Every other technical post I've made has been downvoted to oblivion and never seen the light of day, but here's hoping that someone sees this that actually needs it.
So here goes nothing.
It seems like the DX11 client is very sensitive to programs that run an overlay on your display. There are some exceptions to the rule. Steam overlay doesn't seem to be causing any issues, but it would probably be wise to disable it. However, programs like EVGA Precision, Display Fusion, and Google Hangouts desktop app seem to cause frequent crashes. (Edit: some users aren't having any issues with Display Fusion.)
It probably wouldn't hurt to also disable any windows aero effects as well.
Averaging about 54-65 fps depending by area with GTX 980 Win8.1 on custom near max settings.
https://www.reddit.com/r/ffxiv/comments/340z5w/psa_directx11_is_not_meant_to_bring_fps_gains/ is a nice little guide if you want to eek out a bit more fps.
'Use low-detail models on distant objects. (LOD)' in graphics settings seemed to make the game a lot more stable as well. However, It will drastically reduce the eye-candy of objects not in your immediate area. Makes flying look a lot less pretty.
Edit: Words & formatting.
Edit2: Post your GPU, and OS if you're experiencing the black screen crash. Seems like it might be an issue with the client and Win8. Update: People appear to be having it on Win7 as well. Just less frequently it seems.
Edit3: Linked a thread that helped with stability and got an extra ~10fps
Edit4:/u/bloobalooby had another possible fix.
- YMMV but I was having 2 issues and I've been messing around with them for days to try and fix them. While playing: 'Display driver stopped responding and has recovered' - Error present with 353.30 and 353.06, so after much trial and error I rolled back to 350.12 and changed the physx setting [setting physx to GPU instead of auto] which seems to have fixed it. Uninstalled with DDU and clean install each time.
- On exit: 'Final Fantasy XIV: A Realm Reborn has encountered an error and needs to close.' - resolved this with uninstalling the nvidia HD audio drivers, and setting ffxivboot.exe to 'run as administrator' and win7 compatibility.
Edit5: There is a thread on the official forums about this as well. Not really any new information on it.
No dev response yet either =(
UPDATE 7/30: After updating to Win10, with the Win10 Geforce driver (353.30WHQL) I have had 0 stability issues. Ran the DX11 client on full blast for 9 hrs. Not a single issue. (Update: 1 week later, still no crashes.)
108 comments