DX10 skip?

Greetings,

I am a user is LOTRO.

InnerSpace b5333 tried to update.
There was good news that DX11 support.
So? DX10 and will skip?

I can only support DX10 ATI HD4890 has.
b5333 include LOTRO client get errors.
LOTRO client is set to DX9 when running, innerspace can not detect the LOTRO client.

There is another problem.
Understandably mmorpg users right click to adjust the camera angle.
In previous versions of the mouse cursor was hidden.
In the current version(b5326) is located in the center of an uncomfortable shaking.

If we can not solve these problems there is no desire for the latest version.
However, some versions of the past did not have any discomfort to the version used to open the way to want you.

Thanks to have a keen interest in Multiboxing, but some problems have more. Well, I will inquire about the problem.

[lax]

InnerSpace b5333 tried to update.
There was good news that DX11 support.
So? DX10 and will skip?

I can only support DX10 ATI HD4890 has.
b5333 include LOTRO client get errors.
LOTRO client is set to DX9 when running, innerspace can not detect the LOTRO client.

I am debating whether or not to add DX10 support. After implementing DX11 support it would not be a massive undertaking, however it would only really be useful in DDO and LOTRO, and any other game that supports DirectX11 but refuses to allow it on down-level hardware. You can use DX11 with your HD4890, LOTRO just doesn't want to. I'm not sure that particular behavior will ever extend beyond LOTRO and DDO, and certainly no new games will actually use DX10. So I'd be doing a bunch of work just to support an outdated version of DirectX specifically for DDO and LOTRO and only because they don't want to use DX10 feature level with DX11. From where I'm sitting that's not a win when it will work fine with DX9... and from where you're sitting it would clearly be better to run in DX10 or DX11 (preferably DX11, and in case I wasn't clear I blame Turbine for this one).

As far as the crash issue, I will make sure that goes away before the dev build goes live.

There is another problem.
Understandably mmorpg users right click to adjust the camera angle.
In previous versions of the mouse cursor was hidden.
In the current version(b5326) is located in the center of an uncomfortable shaking.

The mouse cursor should still be hidden during mouselook. I will have to try to reproduce this, thanks for reporting that you're having an issue with the cursor being visible during mouselook

If you find build 5318 preferable for now, you can get it from the archives here: http://www.lavishsoft.com/account/is-archives.php

Okay, DX10 debating the word a little bit hopeful, but you'll need some more time until the decision.

I'm not a developer perspective, developers of the plan is difficult to agree with all my heart.
Simply from the standpoint of the user, DX10 skips does not understand that.

WOW is a game from everybody you have only the user's environment does not only support DX11.

Now my case, ATI HD4890, HD3850 and I am using,
HD3850 upgrade in the near future, but, HD4890 is not a plan.
Both do not support DX11.

Additionally, DX9 -> DX10 is a very big change.
Relatively DX10 -> DX11 a little change.
Of course, DX9 -> DX11 is a big change of being right is not as normal.
Either the user satisfaction in the DX9, DX11 support a change to the graphics card?

Anyway, we received only supports DX9 for older graphics cards to users, although the development version of the detection problem is I want you to solve.

Even without touching any settings, b5326 (Stable) -> b5333 (Dev) to update the client does not detect.
B5326 again return to the mouse cursor problem, but no other specific details.

I downloaded, and is used to b5318.

[lax]

What I'm saying is they could replace their DX10 engine with their DX11 engine (assuming they would force Vista users to install it). Me adding DX10 support would be a dead-end. The only games it will ever be useful for are DDO and LOTRO, and only if Turbine's decision is to keep all of this group of customers on DX10 instead of DX11. The right decision for me, according to my cost-benefit analysis, is to continue recommending DX9 for those stuck in this particular situation on these particular games...

And I will be fixing the issue with the dev build before it goes live.

First, I do not have much knowledge about Directx.
I'm sorry if my hasty words.

After reading your article, DX10 and DX10.1, DX11 and looked for information.

I say what I know now ...
Turbine for the LOTRO DX11 support.
Like me, DX10 and DX10.1 support only the user who owns a graphics card too, just because of DX11, your graphics card, there is no reason to sell in the market.

From what I hear, DX9 and DX10, but different than, DX10 or DX10.1 and DX11 is only a small difference.

Therefore, Lax is 'The right decision for me, according to my cost-benefit analysis' is right said.
At this point, I must apologize ignorance.

If so, b5333 based on the LOTRO client's settings, DX9 -> DX10 reactivated when a change, no one should have no problem.

But stopped with an error code as shown below, the client will terminate.

----------------------------------------------------
Problem Event Name : APPCRASH
Application Program Name : lotroclient.exe
Application Program Version : 3.2.4.8005
Application Program Timestamp : 4c980a30
Error Module Name : IS-D3D11.dll
Error Module Version : 0.0.0.0
Error Module Timestamp : 4cd78fea
Exception Code : c0000005
Exception Offset : 00002121
OS Version: 6.0.6002.2.2.0.274.10
----------------------------------------------------

But, DX9 is not in the normal.
innerspace that, DX9 setting it to the LOTRO client can not detect.
I put to this situation, I had misunderstood.

I you do not know the dev version of this issue, stable version releases may have thought that.

B5318, I have now satisfied.
However, dev version of the client crash in dx10 mode and, dx9 problem of detection of the client just wanted to say that.

And to finish ...
Is sorry I could not speak English very well.
But I do hope you understand that you are talking about.

[lax]

The crash issue with DX10 in the dev build of Inner Space should now be fixed, as of build 5338

Recently, 'Windows 2008 R2 SP1 64bit English' was installed.
Until now, 'WIndows 2008 SP2 64bit Korean & Windows7 64bit Korean' and was used to, so in the future.

'Win2008 & win7' each other in the DX9 and DX10 is an error.
b5338 DX9 as well, the client has detected a problem.
DX10 is a crash. This is ... Was the same in two of the other PC.

But one thing is something else.
In Windows 2008 R2, DX9 client without a problem is detected is well.
But, still ... DX10 is the Crash occurred.

I am soon to install WIndows7 64bit English is scheduled to test.

Personally, I think Windows 2008, MultiBoxing is determined that the most efficient.

Now, the most commonly used 'Windows7' and I will test.
Please, Win7 64bit English I hope that does not have DX10 crash.


Add ... The same is true in Win7.

but, b5338 detect the problem did not occur in DX9.