The terminal window on vscodium looks so pixelated that its not practical to work on it (see screenshot).
I am using windows 10 pro 22h2 os build 19045.2604 feature pack Windows Feature Experience Pack 120.2212.4190.0. I am using Intel(R) Core(TM) i7-2630QM CPU # 2.00GHz 2.00 GHz with 8 gb ram.
I used chocolatey to install vscodium using powershell opened in administrator mode.
Would appreciate any suggestions on how to solve it. I am relatively inexperienced.
enter image description here
I have no idea what to try to solve it.
Try the two solutions below:
In Settings->Features, change the Terminal>Integrated>Renderer to canvas or dom.
In Properties, Under the Compatibility tab, click on Change high DPI settings and check the Override high DPI scaling behavior option.
Good luck.
Related
I'm trying to emulate a high resolution screen for development purposes; however, from looking around, it looks like the VS emulator will only work with Store Apps / UWP. Is there a way to trick / configure VS into using the emulator for a WPF desktop application?
Alternatively, has anyone found any other, imaginative solution to this kind of issue?
My fallback is to set-up a Hyper-V VM for this, but this feels like overkill for what I need (I'm also not sure I'll be able to set this to the screen ratio that I need).
EDIT:
Having looked into Hyper-V, I can't see any way to configure the display to the desired (portrait) resolution of 2160x3840.
You don't want the emulators for this. You want the simulator.
The Windows Simulator creates an RDP session back to the current machine. It simulates the input and output to the session, but it does not emulate the actual code: that's still running on the same machine.
While VS only launches the simulator for you for UWP apps, once it's running you can run other apps such as your WPF app, Visual Studio, remote debugger hosts, etc.
You can also run the simulator explicitly. It should be installed somewhere like C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Simulator\15.0\Microsoft.Windows.Simulator.exe
The emulators are Hyper-V images of the target OS (e.g. Windows 10 Mobile) and won't run your WPF app.
If getting a 4k monitor is not an option you need to use something like this.
http://www.hdtvsupply.com/display-emulator.html
I'm a newbie to Direct3D technology. And was trying out D3D shared surface code found at Direct3D10, 11 and D2D in WPF - Round 2 DEMO! by Jeremiah morrill Interop.D3DImage.rename2zp. I was able to compile the code without any issues but when I run it I see a blank screen Output window
I'm using VS2013, DirectX SDK(June 2010) and windows 7 OS.
D3D is often pretty good at telling you what the problem is. If you go into the project properties, and enable native debugging, you might see messages in the output window which which will give you a clue - as long as you're running the debug version of the app of course.
There are many reasons it might be failing though - it could be that your graphics card doesn't support what the demo is doing, or that it's starting up with the wrong device settings.
I would like to test my WPF applications using Windows Virtual PC under Windows 7. In my C# code, I'm checking the WPF tier and if it's less than 2, I disable a DirectX call. In order to test on Windows XP, I'd like to use Windows Virtual PC but it seems to only run in software mode. Thus, the tier is always <2.
Any ideas on how to enable DirectX to work in Virtual PC?
Virtual PC 2007
It seems that 3D acceleration is not supported by Virtual PC 2007 but I just found a blog's article where the author found a solution to enable 3D acceleration on Windows 7 client. The trick should work only with both host and client running Windows 7.
Here is the link. Hope it helps.
VirtualBox
VirtualBox, since version 3.0, provide support for 3D acceleration with DirectX 8/9.
Unfortunately it is not very stable and in addition Visual Studio crashes when developing WPF applications and 3D acceleration is enabled.
A ticket has been opened and it says that they are working on a fix
VMware Workstation
Also VMware Workstation provided experimental DirectX support since release 5.5. But reading through their forum topics it seems that WPF development works with 3D acceleration enabled only with VMare Workstation 7 and later.
I didn't try myself but it seems promising. On the product page you can see Aero 3D working on Windows 7 and a screen shows also Half-Life!
From this page:
VMware Workstation was the first to
support 3D graphics in virtualized
environments and is now the first to
support Windows Aero in Windows Vista
and Windows 7 virtual machines. Run
even more 3D applications with support
for DirectX 9.0c Shader Model 3 and
OpenGL 2.13D graphics in Windows
virtual machines.
Evaluate the trial and let us know...
Sorry, even latest Virtual PC doesn't support hardware DirectX redirection.
You can try VMWare Workstation 7.1. They claim to support DirectX up to 9.0c, which is enough to get you to tier 2.
VMWare 7.1.3 does support DirectX but only if you are using the 8 subset rather than a full 9.0c implementation. As a result, while the dxdiag will run properly, actually using a tool that requires a full 9.0 implementation is hit or miss - i.e., you have to run it to see if it works. I have tried various games and development tools which state the exact same requirements and run properly on a system with 9.0 installed, but under VMware - some of them work, and others die immediately - so it seems they are correct and only the 8 subset is working at present - so if you don't need 9.0 you're good to go, but if you do, you're DOA.
So the support isn't fully stable - but it's worth a try if you have no other option.
Visual Studio 2010 moved to using WPF for rendering the editor. This is leading to slowdowns while I am editing code, especially if I'm running something else that uses other video capabilities.
How can I speed this up? A new video card? New drivers? Settings?
What technologies does WPF use to render and what video card would complement it?
WPF uses DirectX for rendering, so a new top of the line video card would certainly help you out here. Any solid ATI or Nvidia card nowadays supports the latest and greatest DirectX.
The answer from #Charlie is absolutely spot on; and I thought about saying this on a comment but then figured I should put it as an answer.
Under certain circumstances (certainly on my desktop at work, which uses a workstation NVidia card), which are listed in the installation issues (connected with Hyper-V in particular), VS2010 fails to enable video acceleration even if it is available.
Open up Tools->Options, and on the very first options panel you'll see a group in the middle 'Visual Experience'. Just make sure that everything is checked in there and that it says 'Visual Studio is currently using hardware-accelerated rendering...'.
I don't think the hardware requirements for VS2010 are particularly heavy - but your card certainly must be DX capable.
I'm using VS 2010 on Windows Server 2003, running on a Dell Inspiron 9400 laptop. VS 2010 runs fine, except for persistent and random screen re-drawing issues. Samples of these are here.
These artifacts occur as the mouse moves over items that highlight on a mouse-over event, while scrolling, and when switching tabs. VS 2008 has non of these issues, so I assume that it is related to VS 2010's use of WPF. Could it be that my video card or driver is not up to the task of rendering WPF? Some other WPF applications (not Silverlight) also have some of these screen repainting problems.
I have tried a variety of settings in System Properties-->Advanced-->Performance Options-->Visual Effects, and in the related "Advanced" tab, Processor Scheduling is adjusted for best performance of programs.
Many thanks for any suggestions!
This has been answered for a while but I just fixed a similar issue with screen artifacting I was receiving in editor views of a MVC3 application. I'm running on a Core i7 3960X 6 core processor, the graphics card is a Radeon HD 6950 2GB. Needless to say, I shouldn't be getting these issues. It looked to be something related to my graphics card because going to Tools > Options and then unselecting "Use hardware graphics acceleration if available" caused the issue to stop occurring -
Visual Studio uses WPF which used the video card alot more than traditional GDI applications, I'd check your card drivers and make sure they're up to date.