IME problem in StarCraft II (DirectX game)

Please post your problem description here

Moderator: Barb@Invincea

Post Reply
KomeijiKuroko
Posts: 2
Joined: Tue Aug 16, 2016 7:29 am

IME problem in StarCraft II (DirectX game)

Post by KomeijiKuroko » Sun Apr 08, 2018 8:54 am

Hello, I have problem with IME in StarCraft II.

Image

When you switch to IME at any textbox, IME candidate box is shown. But when you try to press any number key to apply any candidate word, for example 1 for "hello", then nothing happend and it doesn't apply to textbox.

My IME is Windows 10 Microsoft Chinese Pinyin.

Image

also Microsoft Windows 10 Japanese IME faces to same problem.

All above IME work well in normal WIndows application, and I think it failed because it is DirectX game and hooked IME Handles.


This is Windows DirectX Game IME Dev Manual from MSDN:
https://msdn.microsoft.com/en-us/librar ... s.85).aspx

I tried to add * to OpenIpcPath, OpenWinClass or OpenClsid, but all failed.

Attachment is my Resource Access Monitor log.
Attachments
Reslog.zip
resource access monitor log
(2.78 KiB) Downloaded 8 times

Barb@Invincea
Sandboxie Support
Sandboxie Support
Posts: 2337
Joined: Mon Nov 07, 2016 3:10 pm

Re: IME problem in StarCraft II (DirectX game)

Post by Barb@Invincea » Mon Apr 09, 2018 10:51 am

Hello KomeijiKuroko ,

I haven't tested the game yet (not sure if there's a free demo out there, I'll have to search) , but I suggest you try the following:

Create a new Sandbox with default settings.
Right-click on your Sandbox --> Sandbox settings ---> Resource Access --> COM Access
Hit Add
Copy paste:
{A38F3677-32FC-4DAC-99B3-D804B193D2C4}
Apply and Ok your way out
Configure --> Reload configuration
Try the game

There also a few more COM classes listed that may be relevant, you want to test adding one a time per the steps above and see if it makes a difference:

{41445657-4118-4689-B300-E7F1EB61FF7B}
{6FFA842B-FD90-4A0E-9315-21C52B2457AA}
{88C524CA-551B-4C01-9A42-CDB16B745291}
{DA7E4657-8FA8-4B76-9A14-9BF380FA3738
{FFE8C349-2BB1-411F-93CE-0364C5F9FD9F}

Keep in mind you are punching holes in the Sandbox, so proceed with caution. If adding a particular COM Class does not fix the problem, remove it, then add another one and so on.

I'll update this thread if new info becomes available.

Regards,
Barb.-

Post Reply

Who is online

Users browsing this forum: No registered users and 0 guests