Comments (12)
@Spahbed I'm unclear if your issue is solved or not. Please do not start describing different unrelated bugs here in this issue as that will cause confusion and make it less likely for anything to be fixed. Once this bug is resolved if you have a different bug please open a new issue.
You didn't say if you did as asked previously and ran with the most recent nightly build. Is that how you are now able to capture? If so it is most likely that your device is broken and the workaround in the recent nightly build has avoided it.
@Henry-Suen Please do not try to get involved in bug diagnosis and suggest things for users to try when we are trying to investigate a bug. Trying to narrow down the cause of bugs especially on a platform as fundamentally broken and awful as Android is difficult enough with only RenderDoc developers so adding in additional confusion with other instructions and people who may not understand how RenderDoc works or what is wrong is very likely to cause problems.
from renderdoc.
I just happened to have the same issue hours ago.
The key to my problem is the AndriodManifest.xml > android:debuggable="false"(should be true) even in development build.
I managed to capture frames of my program in the morning but an updated version later , a colleague overrode the debuggable flag, made me suffer the issue you are having.
And I changed the flag back and it works again.
It might sound dumb that there's a clear warning showing "Android application not set up for RenderDoc capture"
but the warning is glitchy itself. It'll show that whether it's true or not, so it became a "cry wolf" to users like me.
I still got that warning even when it's working.
from renderdoc.
Please can you check if you can capture and replay these APKs on your device jake-kart-vk.apk, jake-runner-gles3.apk.
These APKs are known to work and help to identify if there is a device issue.
from renderdoc.
I just happened to have the same issue hours ago. The key to my problem is the AndriodManifest.xml > android:debuggable="false"(should be true) even in development build.
I managed to capture frames of my program in the morning but an updated version later , a colleague overrode the debuggable flag, made me suffer the issue you are having. And I changed the flag back and it works again.
It might sound dumb that there's a clear warning showing "Android application not set up for RenderDoc capture" but the warning is glitchy itself. It'll show that whether it's true or not, so it became a "cry wolf" to users like me. I still got that warning even when it's working.
Where are you changing that setting
from renderdoc.
Please can you check if you can capture and replay these APKs on your device jake-kart-vk.apk, jake-runner-gles3.apk.
These APKs are known to work and help to identify if there is a device issue.
Can confirm it also gets the same error with both of these; timeout; app runs though
from renderdoc.
I just happened to have the same issue hours ago. The key to my problem is the AndriodManifest.xml > android:debuggable="false"(should be true) even in development build.
I managed to capture frames of my program in the morning but an updated version later , a colleague overrode the debuggable flag, made me suffer the issue you are having. And I changed the flag back and it works again.
It might sound dumb that there's a clear warning showing "Android application not set up for RenderDoc capture" but the warning is glitchy itself. It'll show that whether it's true or not, so it became a "cry wolf" to users like me. I still got that warning even when it's working.Where are you changing that setting
Assets/Plugins/Android/AndroidManifest.xml
It appears that your issue is not related to this, since Zorro666 provided you with APKs that are possibly debuggable.
Try to uninstall the render doc apps on your phone and link the PC again?
from renderdoc.
If those APKs also fail can you please check with the latest RenderDoc nightly build? It includes some workarounds for broken devices that don't work properly, and this may fix the problem you're seeing.
from renderdoc.
I just happened to have the same issue hours ago. The key to my problem is the AndriodManifest.xml > android:debuggable="false"(should be true) even in development build.
I managed to capture frames of my program in the morning but an updated version later , a colleague overrode the debuggable flag, made me suffer the issue you are having. And I changed the flag back and it works again.
It might sound dumb that there's a clear warning showing "Android application not set up for RenderDoc capture" but the warning is glitchy itself. It'll show that whether it's true or not, so it became a "cry wolf" to users like me. I still got that warning even when it's working.Where are you changing that setting
Assets/Plugins/Android/AndroidManifest.xml
It appears that your issue is not related to this, since Zorro666 provided you with APKs that are possibly debuggable.
Try to uninstall the render doc apps on your phone and link the PC again?
This worked. IT still isntalls two render docs, I dont know why; both different sizes
ISsue im having now is; ITs capturing stuff but doesnt display any duration for the events; that part was working when captured straight from Unity
Tested that on kart and my apk both dont show duration of anything
from renderdoc.
Try to click this button to refresh the duration.
from renderdoc.
Yep tried that; just says 0 for everything
Also get this error showing up at the bottom, not sure if relevant
from renderdoc.
@Spahbed I'm unclear if your issue is solved or not. Please do not start describing different unrelated bugs here in this issue as that will cause confusion and make it less likely for anything to be fixed. Once this bug is resolved if you have a different bug please open a new issue.
You didn't say if you did as asked previously and ran with the most recent nightly build. Is that how you are now able to capture? If so it is most likely that your device is broken and the workaround in the recent nightly build has avoided it.
@Henry-Suen Please do not try to get involved in bug diagnosis and suggest things for users to try when we are trying to investigate a bug. Trying to narrow down the cause of bugs especially on a platform as fundamentally broken and awful as Android is difficult enough with only RenderDoc developers so adding in additional confusion with other instructions and people who may not understand how RenderDoc works or what is wrong is very likely to cause problems.
That's rude for commuty member who trys to help others. If you read the the words properly, he solved it by uninstalled the render doc apps and reinstalled them by linking again.
You have my respect for your contributions and skills But i don't need your lecturing.
I can't believe you have patience with harassing issues but not with an enthusiast.
from renderdoc.
oc works or what is wrong is very l
The timeout issue was fixed yes; Ill open another for the capture issue
from renderdoc.
Related Issues (20)
- Android - Can't attach to application HOT 2
- Resource Usages context menu and panel doesn't show resources accessed via ResourceDescriptorHeap indexing (bindless) HOT 1
- OpenGL: Wrong zoom level with texture generated via glTextureView() HOT 1
- RenderDoc is unable to connect and debug on Samsung S23 Ultra HOT 22
- Smoothly capture several sequential frame HOT 1
- [Vulkan] Pipeline state only shows one declaration per aliased binding HOT 2
- Renderdoc Support for embedded systems HOT 1
- [Vulkan] Renderdoc layer changing image memory requirements affects programs relying on external memory HOT 8
- Vulkan dynamic uniform buffer offsets are interpreted incorrectly HOT 2
- (OpenGL) HDR corrupts textures and freezes the software after a capture HOT 8
- [Bug][OpenGLES] Sample mip1 and render into mip2 of same texture on mobile, renderdoc can not display texture result correctly HOT 5
- Cannot capture frame with AMD properitary driver HOT 1
- GLFW and Vulkan does not work together HOT 7
- Vulkan App enabling renderdoc layer causes ERROR_INITIALIZATION_FAILED HOT 3
- Error with RenderDoc HOT 1
- Mesh shader payload causes crashes, GPU resets and system freezes HOT 6
- Resource inspector should show pipeline usage in frame
- Android UI is completely black in v1.33 development builds HOT 4
- Texture Viewer cannot distinguish image binding from same texture but in different mipmap level HOT 5
- python API can't take a capture from local machine HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from renderdoc.