I connected an external monitor to my macbook. (HP 24w)
On some editors, including vsc, I can not work on the external monitor because the resolution and font rendering is not perfect.
I have attached the two photos below to show the problem.
Can you advise me something?
Thank you.
First photo: mb pro
Second photo: hp 24w external monitor
This fixed it for me.
defaults write com.microsoft.VSCode.helper CGFontRenderingFontSmoothingDisabled -bool NO
Related
I have a Retina screen MacBook Pro with a 15.6" 4K external monitor attached. I've discovered the resolution of the Citrix session is terrible unless I set the (MacOS) display resolution to 3840x2160, in which case the session resolution is perfect.
The trouble is at this setting, the resolution outside of the session, in MacOS is tiny - I usually have it set to scaled slightly larger. Without the external screen attached, the situation is the same with the default native display resolution resulting in very poor quality in the session.
Is there any solution where both the Citrix session and MacOS both look good?
defaults write com.citrix.receiver.nomas EnableHighDPI -bool YES
I have a Retina screen MacBook Pro with a 15.6" 4K external monitor attached.
According to Citrix they don't have a solution yet.
Prerequisites
To try out on individual MacBooks without enabling for the entire organization/store or if you do not want to whitelist LaunchDarkly on your internal network, you can run the following command in macOS Terminal
defaults write com.citrix.receiver.nomas EnableHighDPI -bool YES
Limitations
Supported devices: MacBook, MacBook Pro. Devices not supported: Mac mini, iMacs, Mac Pro.
No Multi monitor support. This feature will not work if you have connected a secondary monitor. Even if you don't use the secondary monitor with the Citrix Workspace app, simply connecting it will cause this feature to not be available. This feature works only when you use a single monitor for your device.
Source: https://support.citrix.com/article/CTX270704/citrix-workspace-app-for-macos-and-retina-displays
I tried it on my M1 Mac. After I disconnected the Thunderbolt dock with all peripherals the running session changed the resolution by itself to higher DPI. As soon as I connected an external monitor I was back to 1080p.
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.
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.
Here's the gist: we have an Air app that displays bitmaps at full screen, original size and scaled. On the Mac, these bitmaps look great (antialiased and smooth). On Windows (regardless of machine), they look pixelated and terrible.
We've updated Air and it still looks bad under the latest Air build. Is there something that we can do programmatically to fix this, or is there a platform issue that we don't know about?
Did you try to set the Smooth parameter as true?
var YOUR_BITMAP_OBJECT = Bitmap(YOUR_BITMAPDATA_OBJECT);
YOUR_BITMAP_OBJECT.smoothing = true;
Also be sure the export has the correct compression (recomendable more than 80%).
Check the resolution diference in Windows versus Mac, maybe in Windows it's higher.
What is your current render mode? i suggest to set render mode to CPU.
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.