Slow object recognition

If Ranorex Studio is recognizing elements slowly, there are a few options you can try.

1. Whitelisting your application, click View > Whitelist
   
2. Add your application to the Whitelist.
   
3. Check resource allocation for the machine.
   Verify that your machine meets the required system specifications System requirements
4. To verify plugin settings, go to Settings, and select the Plugins tab.
   • Based on the AUT’s technology, search for the Plugin that you use to track elements(ex. Win32, WPF, etc..)
   • Change settings that impact performance, such as showing all elements:
     

Note: If unsure which Plugin is used, track an element and open it in Spy.
Then, go to Advanced Settings and search for FlavorName

Slow Object recognition (.NET 5+ applications)

If you are experiencing slow object recognition with .NET 6+ applications using any of the WPF plugins, find the solution below:

1. Update Ranorex Studio to 11.6.1+
2. Verify that the WPF Plugin is being used and that the WPF.Core plugin is enabled
   Settings > Plugins > WPF and WPF.Core
3. Run your tests and notice the improvements.
   

If you are experiencing issues running the test, or getting any random exceptions during runtime, you can follow these instructions:

1. Go to Settings > Plugins > WPF.Core
2. Set the Use a legacy serialization mechanism setting to True and click OK
   
3. Restart the Application Under Test (AUT).
4. Run the tests again

In case you are still encountering issues, you can contact our Support team and provide the new Tracing Logs that were introduced with 11.6.1+.

To do that, please follow these steps:

1. Go to Settings > Plugins > WPF.Core
2. Set the Enable tracing logs for the new serialization setting to True and click OK.
   
3. Restart the Application Under Test (AUT)
4. Run the test again
5. The logs are collected in 2 of the following locations:
   C:\Temp\Ranorex\RanorexLogs_Server.txt and C:\Temp\Ranorex\RanorexLogs_Client.txt.
6. Compress the files and send them to our Support team

These logs help us understand more details about any exception or error that is happening while running the tests.