{"id":30338,"date":"2022-03-31T16:18:24","date_gmt":"2022-03-31T16:18:24","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/cppblog\/?p=30338"},"modified":"2023-02-02T19:09:54","modified_gmt":"2023-02-02T19:09:54","slug":"enhancing-game-developer-productivity","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/cppblog\/enhancing-game-developer-productivity\/","title":{"rendered":"Enhancing Game Developer Productivity with Visual Studio 2022"},"content":{"rendered":"

Introduction<\/h2>\n

Since the launch of Visual Studio 2022, we have been continuously making performance improvements to enhance game developer productivity. In my Microsoft Game Dev talk for GDC<\/a>, I shared why Visual Studio is the ultimate IDE for game developers. I also partnered with the folks at Double Fine Productions to demonstrate their most loved features when developing the Award-winning Psychonauts 2.<\/a> Next, I shared features that Double Fine is most excited for in VS2022. Lastly, Microsoft Game Dev announced<\/a> that a set of GitHub Actions for Perforce Helix Core on Azure, authored directly by Perforce, is now available.<\/p>\n

In this blog, I will show you some amazing speed improvements when searching and getting to code by discussing our measurements from large codebases such as Unreal Engine and Chromium. See how much faster you can get to code with speedier C++ IntelliSense ready and opening a file. Search faster with C++ Find All References and indexed Find in Files.<\/p>\n

While game developers and developers with large codebases will benefit from these improvements the most, all C++ developers will gain increased productivity with these changes.<\/p>\n

Testing Methodology<\/h2>\n

We tested using an Unreal Engine 4 sample project on a desktop with an Intel Core i7-9700 @ 3Ghz, 64GB RAM, and an SSD. The tests took place on Visual Studio 2019 16.11 and Visual Studio 2022 17.1. The results were averaged over 3 runs. For Find in Files, we benchmarked using the Chromium repo, with more than 300,000 files.<\/p>\n

Results<\/h2>\n

Getting to Code<\/h2>\n

\"Image<\/a><\/p>\n

When opening a file on Visual Studio 2019, it took 2.02 seconds for code to show up. In Visual Studio 2022, you can see the same action completing in only 0.82 seconds, resulting in a 2.44X speed up. In Visual Studio 2019, the time it took for semantic colorization to show up after opening a file was 12.9 seconds. You will experience that the same action is 2.22X faster in VS2022, taking 5.8 seconds.<\/p>\n

For Unreal Engine projects, you will experience additional speed up for IntelliSense readiness. Learn more in this blog post.<\/a><\/p>\n

Code Search<\/h2>\n

\"Image<\/a><\/p>\n

In Visual Studio 2022, you will see a speed up of 1.74X when using C++ Find All References (Shift + F12). The action was completed in 17.36 seconds; compared to Visual Studio 2019, the action took a little over half a minute.\nFor Find in Files in Visual Studio 2019, searching through 300,000 files in the Chromium repo took 30 seconds. In Visual Studio 2022, you will notice that the same action will take 1.5 seconds, a 20X improvement!<\/p>\n

Analysis<\/h2>\n

You will notice several optimizations to the IntelliSense engine that created more efficiency in getting to code scenarios. Find All References was also enhanced by eliminating inefficiencies during search.<\/p>\n

For Find in Files, you can now take advantage of indexed search. To enable indexed searching, go to Tools > Options > Environment > Preview Features<\/em> and ensure \u201cEnable indexing for faster find experience\u201d is checked. For more details, please see this blog post.<\/a><\/p>\n

Feedback Wanted!<\/h2>\n

Your feedback through Developer Community<\/a>, surveys, and social media channels has made these improvements possible. We thank you for your valuable comments.\nThese enhancements are a continuation of our focus on improving productivity for game developers. Throughout the Visual Studio 2022 development cycle, we will continue to make improvements like ones detailed in this blogpost. If you are a game developer, let us know your thoughts in our 2022 Visual Studio Game Developer Survey<\/a>.<\/p>\n

In addition, please continue to help shape the development of Visual Studio by talking to us in the comments below, on Twitter (@VisualC<\/a>), or via email at visualcpp@microsoft.com<\/a><\/p>\n

Upgrade to Visual Studio 2022<\/h2>\n

Download the latest version of Visual Studio 2022<\/a> to take advantage of these productivity benefits today!<\/p>\n","protected":false},"excerpt":{"rendered":"

In this blog, we will discuss how much faster you can get to code with speedier C++ IntelliSense ready and opening a file. Learn how search improved with faster with C++ Find All References and indexed Find in Files.<\/p>\n","protected":false},"author":39811,"featured_media":29661,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1,3927],"tags":[3918,3919,3901],"class_list":["post-30338","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cplusplus","category-game-development","tag-game-dev","tag-productivity","tag-unreal-engine"],"acf":[],"blog_post_summary":"

In this blog, we will discuss how much faster you can get to code with speedier C++ IntelliSense ready and opening a file. Learn how search improved with faster with C++ Find All References and indexed Find in Files.<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/30338","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/users\/39811"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/comments?post=30338"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/posts\/30338\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media\/29661"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/media?parent=30338"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/categories?post=30338"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/cppblog\/wp-json\/wp\/v2\/tags?post=30338"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}