Low FPS when naming application explorer.exe - windows

I have an Unity application let's call it X it usually runs at about 60 FPS. But when I rename the executable to Explorer (the same as Windows Explorer) my FPS drops to 7-8.
This is a screenshot from the profiler when the app is named X when the FPS is about 60:
This is another screenshot from the profiler with the same app but named explorer.exe when the FPS is about 8:
This is a screenshot of the GPU usage when named X.exe:
The same app named explorer.exe:
I'm can and will rename the app to something else, but I'd like to know what causes this and how I can figure this out on my own.
Things I've tried:
Disabling my AV which is windows defender and restarting with no effect.
Trying to reproduce it on a colleagues PC, with no success.
This makes me things that it might be specific to my machine and that maybe some process is trying to make some API calls on the other Explorer.exe and somehow affects my app.
In case it's relevant
I'm using Unity 2019.3.5f1
It's happening in the built app both debug and release
OS Name: Microsoft Windows 10 Pro
OS Version: 10.0.18362 N/A Build 18362
System Model: Alienware 17 R4
System Type: x64-based PC

Disappointingly the issue was cause by the fact the my windows was using the CPU graphics card instead of the dedicated one when the app was named explorer.exe.
To change this, I had to:
Go to Settings > System > Display > Graphics Settings.
Browse and pick my app.
Select my app from the list.
Select Options.
Select High performance.
Select Save.
Original source
This made my app use dedicated GPU instead of the integrated one.

Related

OBS - black screen while capturing display

I have a problem with OBS. I'd like to make tutorials how to do programming, teach people basics & show them, for example, how to write neural network in Java (without any ML libraries) but in order to do so, it would be great to show them my presentation about it and other windows, so recording full screen is needed (I know I could keep switching windows but it's faster and easier to display full screen). When I added the source "capture screen" the captured screen is black but audio works. I've tried to solve this problem and I went through many tutorials (like 15 or smth) and nothing has helped. I've also added a new thread in OBS Official Forum but nobody has responded. My OBS version is 25.0.4. Here is what I've tried:
- I ran the program as an administrator
- I have reinstalled it (with deleting all files and settings ~ no leftovers)
- In Nvidia Control Panel in 3D Settings I've selected OBS Studio and changed graphic processor to an integrated graphic (also tried dedicated graphic and global choice - nothing worked)
- In GForce Experience I disabled sharing
- Couple times I've restarted the computer and OBS (after any change I've done)
- I ran the OBS in compatibility mode with Windows 8 (and I've tried Windows build-in troubleshooting option)
- I ran OBS with an integrated graphic from a desktop
What I've discovered is the capturing specific window works perfectly, the problem occurs only with capturing full screen.
I have no idea what to do, please help me.
Here is what I see:
It looks like OBS just "can't see" screen, I use only one screen by the way
Black screen
though single-window capturing works perfectly
5
OBS Settings vol.1
OBS Settings vol.2
Logs:
https://obsproject.com/logs/NMexpZp-b4nXDxLl
Specifications of my computer:
I use a laptop - MSI GF 63 8RC
- Intell Core i5 8300H
- GForce GTX 1050 (actualizations are installed) 4GB VRAM
- Windows 10 Home, 64bit (updated to version 1909)
- 16GB RAM
- FHD Screen (1920x1080)
You will need to change the Graphic for this app to integrated graphic
I had the same problem in the virtual machine And I solved it this way go to virtual machine setting
in display section uncheck Accelerate 3D graphics
The problem was solved and the recording was done correctly.

Windows 10 Mobile Error reporting not available [duplicate]

In Win 10 Mobile was setting for developers where I could set the count of crash dumps must be saved on a device. After installing Creators Update that setting disappeared and crash dumps are not saving anymore. Is it possibble to save crash dumps on a device with Creators Update ? It's necessary for me.
I know about app insights, but it's not variant - I need a full dump with native symbols.
Microsoft changed this since Windows 10 Mobile Creators update v1703. After activating Device Portal use your development PC and open the Device portal Url that is shown on the phone.
Now the updated device portal has an entry Crash data which you have to click
Now it takes around 30 seconds where the phone enumerates all sideloaded apps, lists them and offers you a checkbox to create dumps for each sideloaded app
So with the updated device portal you can now control the dump creation per sideloaded app instead of a global dump count. But I have no idea how many dumps are created, because I haven't got a crash.

Custom ROM Samsung SM-G53OT1

I've been using this phone a while, and I have been through tough times with it. Two bootloops, Google Play Services crashing infinitely, weird errors, everything. I'd say I've "bonded" with this Samsung and would like to take it up a notch.
I've been looking everywhere for ROMS for this phone and I haven't been able to find any, not figure out how. Maybe I'm just stupid but man it's aggregating.
I have a PC, Samsung driver's, Odin, and of course, my Samsung. I have everything I believe is necessary to flash a custom ROM.
I would appreciate ANY help to get a nice ROM for my phone.
At the minimum, I'd like it to have a theme changer.
Samsung Galaxy Grand Prime One
SM-G53OT1
You can install CM 13 on your SM G5series
CM 13 is a custom ROM used in android devices.
your warranty will be void if you install a custom rom.
careful that installing a custom ROM would sometimes injure your device
permanently.
Follow these steps to root your device to enjoy vast features
Download a recovery.img,USB driver and ADB tools for your corresponding device(extract and install them and keep the extracted file in one folder)
Download and Copy the zipped cm13 and gapps6(arm)to your device's internal or SD storage
Connect your device to a PC in USB debugging mode(just tap 7 times on the developer options in settings to enable USB debugging)
open program files,open minimal adb tools.Type CMD in location bar to open the command prompt in that folder)
type "adb devices" in the CMD without quotes.
"fastboot recovery.img"
Your device will be reboot and
Team win recovery is opened
wipe the system ,cache,dalvik cache
select INSTALL from the option
choose the zipped file cm13 and swipe it to flash the custom ROM.
choose the zipped file gaapps and flash it by swiping.
Your device will be updated to marshmallow after rebooting

blank window when installing visual studio on windows 10

I have a Windows 10 64-bit PC (fresh install, not an upgrade).
When I run the setup file (web or offline alike) in order to install Visual Studio (2013 or 2015, Community edition), all I get is a small black rectangle on the screen (which I later found out that this is actually the title of the setup popup window), without the actual window of the installation.
I have tried it also after a reboot, and with various "versions" of the installation files (web, iso, standalone), but it's always the same situation.
What can I do about it? VS is my main development tool and I really need it on this computer as soon as possible.
Similar problem here. Program install ok but display blank screen after launched.
Problem solved when I changed my Nvidia graphics's global 3D setting to integrated graphics.
Right click desktop
Select Nvidia Control Panel
Select Manage 3D Settings
Under preferred graphics processor, select integrated graphics.
Apply.
If you are using a laptop with an external monitor, try unplugging it and using your primary monitor to launch. This worked for me. Laptops often have dual graphics cards and I believe we're hitting some issue with the way the Installer for VS was written (likely WPF)
Once I launced it and started the installation, I could safely plug my monitor in and it kept working properly.
I'm using an AMD GPU, It was a blank white screen but when I hover the mouse over it, I can see the text events
By the way
I went to my AMD Radeon Settings and saw that vs_installershell.exe and vs_setup_bootstrapper.exe were added automatically to the Switchable Graphics list
they were with Not Assigned Option which usually is like High Performace Option
means It would run it with my ATI GPU.
So I clicked on them
Selected Power Saving Option (to work with my Intel GPU)
Which worked and I can see the window of visual studio installer back
after restarting visual studio installer for sure.
whether is your graphics card, just turn on power saving for it.
Had the same issue. Since this topic is not accept any answare, there is one from https://developercommunity.visualstudio.com/content/problem/150888/visual-studio-installer-shows-blank-screen.html
Try to open installer as Admin.
You will probably have blank screen. Do not close it!
Open installer once more.
Hope it help other people with same issue.
the same thing happened to me, i didn't do anything i just waited for it and it started showing it's status, i suggest you close other running programs to avoid conflicts and performance hindering, and try it again.
This seems like a very shoddy issue. I've run into this problem too, and I tested all solutions that I came across online. These all work:
Running the installer as administrator, which is a blank screen. Leave it open and run a second instance of the installer, which will not be blank (doesn't need to be run as administrator the second time.
Changing screen settings so that the laptop screen is not being used.
Downloading the AMD Settings application, and setting vs_installershell.exe to run on powersaving mode. Restart the installer after saving the settings.
Use a default graphics driver instead of the AMD one.
I had the the same problem in my laptop. The temporary solution is: start the installer only without the battery, if installer starts you can connect the cable, it works fine.
I had to run integrated graphics rather than my Nvdia. That solved it for me.
Remember to change it back when programming in OpenGL and DirectX otherwise you may get a list of messages staying that nothing works.
I had the the same problem in my laptop. The work around is, in device management, remove the amd graphics or start the installer only with battery.

Flash Player interface problem

I am facing an interface freeze issue with Flash Projector running a flex state based application. A Flash Projector exe was generated from a standalone flash player ver 10.2. The target machine on which the problem occuresd has 10.3.
Basically "screen freeze" means that the user interface is running as usual on Flash Player, but it's not responding to any user input (like button presses). But if we alt-tab to another application, the state changes in the Flash player. There is display with buttons on the screen, but touching the buttons or doing anything else - it did not respond. Rebooting the computer fixes the problem.
Can you suggest why this is happening? Is there any known bug in Flash Player.
The problem is this is being hard to reproduce on the developer workstation as it doesn't happen always. But it happens quite often on the target machine running an Intel Atom N270. What debugging steps can you suggest?
Problem : http://www.youtube.com/watch?v=z25oV9QWRyk
Have you tried publishing the projector in 10.1 or a version of Flash newer than 10.2? If you are able to publish it as a SWF first, you can use the stand-alone projector exe (downloadable here) to load and create a projector from it.
According to this Adobe bug issue (registration required), version 10.1 was supposed to have resolved this, but it sounds like it may have reappeared in 10.2.

Resources