Repository navigation
"--disable_direct_composition=1" stop working for the chrome version 137.0.7151.56 #361
Description
Activity
I have exactly the same problem. I had no problem using it a month or so ago and have successfully imported a number of files into Blender.
Now, everytime I run the adapted Chrome code including "--disable_direct_composition=1", a new PID code is generated, and I am unable to capture the Google 3D data.
I had the same problem. For now I download a previous version of chrome using this link: https://vikyd.github.io/download-chromium-history-version/#/. Hopefully I'll work for you guys too
Bump. Any fix for this? It hasn't worked for a few months. New PID every time you click OK and inject it in RenderDoc.
The only fix I had was to use an old laptop, install an old version of Chrome (make sure to disable updates) and then it worked fine. Newer versions of chrome still don't work - something has changed!
I had the same problem. For now I download a previous version of chrome using this link: https://vikyd.github.io/download-chromium-history-version/#/. Hopefully I'll work for you guys too
Which version and what to download then? All i see is files with "MAC" in the name. Not Windows
EDIT: I found now a download to a older chrome version 104.0.5112.81 and now i was able to capture. But again i have now the issue that i can't import the capture into Blender. I downloaded Blender 4.1 specifically and RenderDoc1.31 as recommended.
C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe^" --disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition"
Hi all,
Working setup confirmed on Chrome version 137.0.7151.120:If you're having trouble with RenderDoc injection due to Chrome restarting or changing PID, this setup worked for me:
set RENDERDOC_HOOK_EGL=0
"C:\Users\YOURNAME\AppData\Local\Google\Chrome\Application\chrome.exe" ^
--disable-gpu-sandbox ^
--gpu-startup-dialog ^
--disable-software-rasterizer ^
--disable-direct-composition ^
--disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositorHi all, Working setup confirmed on Chrome version 137.0.7151.120:
If you're having trouble with RenderDoc injection due to Chrome restarting or changing PID, this setup worked for me:
set RENDERDOC_HOOK_EGL=0 "C:\Users\YOURNAME\AppData\Local\Google\Chrome\Application\chrome.exe" ^ --disable-gpu-sandbox ^ --gpu-startup-dialog ^ --disable-software-rasterizer ^ --disable-direct-composition ^ --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor
Mutliple row shortcut parameter? This is too long. I can't insert everything. Also your text misses the CMD execution.
I tried to do what @MrGTAmodsgerman said but it didn't work. Here is his command without the newlines.
C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe^" --disable-gpu-sandbox --gpu-startup-dialog --disable_software_rasterizer --disable_direct_composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor"His suggestion did not work for the newest version of Chrome.
I tried to do what @MrGTAmodsgerman said but it didn't work. Here is his command without the newlines.
C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe^" --disable-gpu-sandbox --gpu-startup-dialog --disable_software_rasterizer --disable_direct_composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor"His suggestion did not work for the newest version of Chrome.
I haven't suggested anything here. I think you pinged the wrong person. But thanks for the line clean up. Now i can capture but still can't import into Blender 4.1.0 with RenderDoc 1.31 x64 on Chrome 104.0.5112.81:
Also i had to reinstall that chrome version because somehow after PC restart, Chrome was crashing on opening, no matter if just opening it normally or through CMD
Reacted by BenfrastructureFOUND THE PROBLEM! 🙌🙌
- Install Chrome 104.0.5112.81
- Install RenderDoc_1.31_64
- Install Blender 4.1
- Install MapsModelsImporter 0.7.0
- Open CMD
- Type in:
C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe^" --disable-gpu-sandbox --gpu-startup-dialog --disable_software_rasterizer --disable_direct_composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor" - PID ID pops up
- Open RenderDoc
- Go to Tools>Settings>General section>Check "Enable Process Injection"
- Hit ok and restart RenderDoc (to be sure)
- Now go to File>Inject into Process
- Type in your ID from Chrome and select your chrome process
- Inject. If Chrome crashes now, try reinstalling it or try to run RenderDoc and CMD as administrator.
- Now DONT USE GOOGLE EARTH. This was my problem why i couldn't import the capture. Only Google Maps 3d works.
- Go to your desired location.
- Go to Chrome settings and set the zoom to 25% (This allows to capture more data)
- Set your delay for capture to 5 seconds so you can be sure you capture the scene.
- Capture and move your mouse in circles. If it stutters, you know it's captureing.
- Double click on your capture
- Save as to your desired folder
- In Blender import and wait if it's hanging. It maybe a large scene.
- Done.
Hi all,
Thanks for all the comments. Managed to get it working on the latest version of Chrome (Windows 11).
Chrome: 138.0.7204.50
RenderDoc: v1.39 (latest version)
Blender: 4.1Before, I simply used a modified Chrome shortcut to get the PID and then captured the view however as was stated, the parameters are too long for a shortcut. This is what I did:
- Closed all instances of Chrome
- Opened CMD
- Typed in C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe" --disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor"
This started Chrome with the PID process number screen.
- Opened Renderdoc.
- Injected into the PID process number
- Closed the PID window
- Chrome then opened as it used to and I was able to take a screen capture off Google Maps (3D Satellite image)
- After saving the .rdc file, I was then able to import it into Blender and it was like this nightmare had never happened :)
Thanks again for everyone's input. Hopefully it works for you.
Reacted by robingarrett1, enrico3 and MatthewReacted by Charles Lang Follain, MrGTAmodsgerman and MatthewI tried to do what @MrGTAmodsgerman said but it didn't work. Here is his command without the newlines.
C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe^" --disable-gpu-sandbox --gpu-startup-dialog --disable_software_rasterizer --disable_direct_composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor"
His suggestion did not work for the newest version of Chrome.I haven't suggested anything here. I think you pinged the wrong person. But thanks for the line clean up. Now i can capture but still can't import into Blender 4.1.0 with RenderDoc 1.31 x64 on Chrome 104.0.5112.81:
Also i had to reinstall that chrome version because somehow after PC restart, Chrome was crashing on opening, no matter if just opening it normally or through CMD
Yes, sorry about that, I meant the poster above you.
Hi all,
Thanks for all the comments. Managed to get it working on the latest version of Chrome (Windows 11).
Chrome: 138.0.7204.50 RenderDoc: v1.39 (latest version) Blender: 4.1
Before, I simply used a modified Chrome shortcut to get the PID and then captured the view however as was stated, the parameters are too long for a shortcut. This is what I did:
- Closed all instances of Chrome
- Opened CMD
- Typed in C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe" --disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor"
This started Chrome with the PID process number screen.
- Opened Renderdoc.
- Injected into the PID process number
- Closed the PID window
- Chrome then opened as it used to and I was able to take a screen capture off Google Maps (3D Satellite image)
- After saving the .rdc file, I was then able to import it into Blender and it was like this nightmare had never happened :)
Thanks again for everyone's input. Hopefully it works for you.
This one works! But I had to make the commands separate for some reason.
Open up cmd.exe:
C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START
In the new cmd box, run:"C:\Program Files\Google\Chrome\Application\chrome.exe" --disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositorYou may have to change the file path if your Chrome is installed elsewhere.
Also, this one worked in Google Maps for me. Go to Google Maps, change it to satellite view, turn off labels, tilt-shift the camera using
shift + left_clickand drag.Also, this isnt explained well in the docs, you have to HOLD the
prt scPrint Screen key while moving the camera around. On Windows 11, by default, this is mapped to the terrible Windows Snipping Tool. You can disable this by doing:Settings --> Accessibility --> Keyboard --> "Use the Print Screen key to open screen capture" --> disable.Thank you everybody!!!
Hi all,
Thanks for all the comments. Managed to get it working on the latest version of Chrome (Windows 11).
Chrome: 138.0.7204.50 RenderDoc: v1.39 (latest version) Blender: 4.1
Before, I simply used a modified Chrome shortcut to get the PID and then captured the view however as was stated, the parameters are too long for a shortcut. This is what I did:
* Closed all instances of Chrome * Opened CMD * Typed in C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe" --disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition --disable-features=UseSkiaRenderer,CanvasOopRasterization,VizDisplayCompositor"This started Chrome with the PID process number screen.
* Opened Renderdoc. * Injected into the PID process number * Closed the PID window * Chrome then opened as it used to and I was able to take a screen capture off Google Maps (3D Satellite image) * After saving the .rdc file, I was then able to import it into Blender and it was like this nightmare had never happened :)Thanks again for everyone's input. Hopefully it works for you.
This no longer works with Chrome 138.0.7204.158, RenderDoc v1.39. I've attempted all of the above methods, but Chrome continues to generate a new PID each time an injection occurs. I had this working just 1 month ago, but none of the methods above are sufficient to successfully process inject, anymore.
Hi rascheln,
Not sure what is happening in your case. I have just tried with Chrome 138.0.7204.158 using my previous instructions and it still works for me. Are you making sure all instances of Chrome are closed and after a full reboot? If so, I don't know why your system is acting differently.
Hi rascheln,
Not sure what is happening in your case. I have just tried with Chrome 138.0.7204.158 using my previous instructions and it still works for me. Are you making sure all instances of Chrome are closed and after a full reboot? If so, I don't know why your system is acting differently.
Yes, all instances of chrome are closed. Renderdoc v1.39. Chrome 138.0.7204.158. Full system restart. I am running a RTX 3090 as the graphics card, and a Ryzen 9 4900x. Running CMD as administrator, running renderdoc as administrator. (I've also tried every combination of admin/non admin credentials using these, just in case).
I followed all of your instructions. Where things behaved differently was the step:
- Closed the PID window
Once the PID window was closed, a brand new one with a new PID opened, instead of "Chrome then opened as it used to." This definitely does not occur for me. I get perpetually refreshing PID's the moment I attempt to inject into a process.
Are you using WIndows 10 or 11? I'm just throwing out guesses at this point. This used to work perfectly fine for me, even on 11.
For me @aaronmcnabb1974 's description works with
- Windows 10 Pro 22H2, Build 19045.6093
- Chrome 138.0.7204.184
- RenderDoc 1.39
- Blender 4.1.0
Hi all,
I've had the same issue with Chome Version 139.0.7258.155. I've found some discussion on the Chromium issue tracker about the
--disable-direct-compositionflag or specifically, that it was changed from--disable_direct_composition, hyphens instead of underscores. Here's a link to the thread and the specific comment.In the project readme.md, under step 2 of the usage section, the old flag is used still.
After I changed the flag to
--disable-direct-composition, it started working reliably. Also, I believe @aaronmcnabb1974's guide works because they had replaced the old flag with the new one, but not sure.Please let me know if this was helpful (or if I am absolutely mistaken on this one!)
Reacted by SioGabx, th3redmage and Johanness777so simple @csroland This resolved my problem of having to try and inject multiple times to get Chrome to work and also get Globe view to work in Google Maps to bring up the geometry again for capture. Thank you!!
Reacted by csrolandFinally worked for me. 2025-10-10
RenderDoc 1.31
Blender 4.1
google map. used : https://earth.google.com/web/ . (google map in 3D mode neverwork for me. No 3D option. even if do all manip recommanded https://blenderartists.org/t/google-maps-models-importer/1153561/176.C:\Windows\System32\cmd.exe /c "SET RENDERDOC_HOOK_EGL=0 && START "" ^"C:\Program Files\Google\Chrome\Application\chrome.exe^" --disable-gpu-sandbox --gpu-startup-dialog --disable-direct-composition"
Solution to my problem: Hold print screen key while print screening make the difference for me. thanks @bcornw2
Also, this isnt explained well in the docs, you have to HOLD the
prt scPrint Screen key while moving the camera around.CC
Reacted by André Moreira and Dylan Roscover
My chrome got updated to 137.0.7151.56 and now even with adding "--disable_direct_composition=1" by the end, everytime when injected into the code, chrome will keep refreshing the code... Not sure what to do next...