Open ajay9634 opened 2 months ago
This is log of error
-
I tested with vc redist installer and painkiller launched successfully. Didn't close vc redist window.
I think @longjunyu2 can patch Wfm with child window rendering patch so game will be launched without any problem.
-
Lol, I finally found out perfect but slow file manager for this problem
https://download.explorerplusplus.com/stable/1.4.0/explorerpp_x86.zip
Here is my video
https://github.com/user-attachments/assets/ee49ff4a-3b53-4098-ae95-ad2be2505e3d
Now no more child window rendering problem.🔥
-
-
Yes, I opened many apps from wine such winecfg, Run , winefile etc but not fixed.
It's fixed when I opened vc redist ,Gog installer and Explorer++.exe
Also It's not related to keyboard input.
Well I am not expert in coding so I can't find the cause. I am a simple modder with some experience who add simple stuff to winlator.
Don't worry.
Thank you so much for your valuable contribution :)
Device Information
Application Configuration Information
Description of the Issue I tested "painkiller black" game. It was launched first time but it didn't work then after. The showing error is "vulkan:X11DRV_vulkan_surface_create Application requires child window rendering, which is not implemented yet!"
I don't know it's related to winlator or wine but I found the workaround.
I launched any gog installer but I didn't install that game then I launched painkiller black main exe and game ran without any error. So problem is game exe couldn't make child window rendering but after after running a gog installer it worked properly.
Here is my video of workaround.
https://github.com/user-attachments/assets/bdf08bd9-c66b-4531-a58b-0fe4f0f3de80
Steps to Reproduce Please describe the steps to reproduce the issue:
Expected Behavior There should be no problem in child window rendering.
Screenshots If applicable, add screenshots to help explain your problem. You can attach screenshots here.
Additional Information Please provide any other relevant information or context. For example, "This issue started happening after updating to version 1.2.3."