I'm trying to profile our game using the latest version of GPA on a HD3000 laptop with Win10 x64. Game is running x32 and DX11 FL10. Running the game standalone works fine but the analyzer crashes when launching the game. Game is still present in task list but there is no window.
The gpasample.exe works fine although it seems to run with WARP drivers when using the /D3D11 switch.
I have a standalone example ready. Just need to know where I can upload it..
I apologize for the delayed response.
Could you please copy and paste your about dialog found in GPA monitor -> About here in the thread?
Also, getting a standalone example will drastically improve the velocity of the fix.
Feel free to private message me with a dropbox(or similar) link of the example and I can try to reproduce your issue on my platform.
Hopefully we can find a quick workaround for you!
I've sent you a PM with the build.
Here is the info from the about box:
Windows 10 build 10586, 64-bit DEP enabled
Num Processors: 4
System BIOS: Dell Inc. A11 (08/03/2012)
Video BIOS: Hardware Version 0.0 (12/22/20)
Device: Intel(R) HD Graphics 3000
Provider: Intel Corporation
Supports GPA Instrumentation
Install directory: C:\Program Files\IntelSWTools\GPA_16.1\
Current user is in Administrators group: YES
Current Graphics Performance Analyzers 2016 R1 (16.1.282401)
Secure Boot/Trusted Boot is Disabled
I have been able to reproduce the issue with the sample you provided.
I've filed a defect for you and will let you know when the engineering team has an ETA on the fix.
In the mean time, I'll look for a workaround.
So in our latest build we have two workarounds.
1. Run the application with "Global Injection" Enabled. Right click monitor -> Preference -> Auto Detect Launched applications (Check)
1a. Run application without "Analyze Application" menu and it should automatically attach.
2. Run the application with Tracing disabled. Right click monitor -> Preferences -> Disable Tracing
2a. Run application WITH Analyze Appliction
Let me know if this doesn't work with your current build and I can give you our latest internal build of the tool!
So this has been fixed in our most recent internal build. If you are interested in getting a pre-release build with the fix, please message me and I can provide it!
Sounds good Henning. We will be releasing a new version of GPA next week that will include your fix, so you should be able to just download the new version next week and it should fix the issue. :)