Host machine: Debian 10 running NoMachine 7.2.3
Settings:
Specified H264
User Hardware Encoding enabled
Use Specific Frame Rate enabled (60FPS)
Use Acceleration enabled
Client: Windows 10 running NoMachine 7.2.3
Both machines have monitors attached.
Using NX protocol for connection.
FullScreen / Scale to Window / Desktop is currently 2560x1440 (reduced from native while testing this issue)
Specific issue:
I do a ton of work in the terminal and when viewing desktop via nomachine, the terminal caret is randomly not visible. The same issue is less noticeable with right click menus and other areas of "visual updates in small screen space." If this were another remote desktop vendor I would try to find the "don't update just regions" setting to force the entire display to update regularly, but I can't find similar settings for nomachine. I have a dedicated gigabit connection between the two machines with no other traffic on that line, so bandwidth is not an issue.
To recreate:
I disabled caret blink (using universal access / accessibility settings) so the caret is a solid block in terminal / vi. If I edit a text file in vi and move up and down, the caret will only update visually every other line or so (verified on the physical screen it is moving correctly). Same if I highlight or insert, etc. You inevitably miss a character or so or lose your place).
I have tried changing speed vs quality slider, resolutions, swapping from h264 to VP8, etc.
I have disabled:
multi-pass display encoding
frame buffering on decoding
client side image post-processing
Nothing seems to change this specific issue. Yes I can make dragging a quarter-screen-sized terminal window smoother, but that doesn't help me follow the caret in vi/vim. Both machines are nicely spec'd (client has 16G / RTX2080, server has 32G / GTX1080)
Is there a way to get nomachine to update all the screen all the time, or at least better refresh small areas like a terminal caret?
(OP): Based on a night of troubleshooting, the issue seemed to be either:
An issue with the Debian install of the nvidia drivers
The server machine is a laptop with a broken main screen (but with an HDMI external monitor plugged in). The Debian X-server may have been confused as to whether it was headless or not and caused issues with nomachine (which tries to detect headless and start a virtual session).
The solution to this exact problem would be to disable the GUI and force a virtual session, per https://www.nomachine.com/AR03P00973 (dummy dongles won't work because the laptop's main display is not a standard plug).
In my specific case, I needed GUI access on the server at times so I couldn't use the above methods, and I could not remedy the problem with Debian, so I wiped the system and installed Ubuntu 20.04, which is more forgiving with graphics drivers and monitors. After setting up the Ubuntu system as similarly as possible to the Debian system and letting the proprietary nvidia drivers auto install, nomachine connected at the same resolution and worked perfectly, without the lag in small screen areas.
Related
I am using Abaqus and performing a simulation in a cube with some particles inside. I ran a the simulation using a Python script, for which results look fine. So I saved some images from the Visualization module showing the strain distribution in the cube. A day later, I ran the same Python script but changed one parameter (maximum displacement applied). But now, when I see the results in the Visualization module, the cube looks like a rectangular prism. So I guess there is some sort of scaling applied to the axes. Also, this scaling is applied globally. If I go to Part or Assembly or Mesh, I will see a rectangular prism instead of a cube. I don't know how this happened if my simulation is done using the script and I did not set any changes in how the results are displayed nor I did this when exporting the images.
I have tried to look for options that are related to the scaling of the axis within Abaqus without success. I also tried to open and close Abacus in case it was something particular of the simulation, but I still see the scaling in the axes. Even if I open the odb file from which I got the images that actually show the cube, now show a rectangular prism.
Something that gave me some hope is that in the visualization "Common Plot Option", in the tab Other, in the tab Scaling, there is an uncheck box with the option "Scale coordinates". If I check the box ans set all coordinates to 1, there are no changes. If I know what the scaling factor is, I could just set the sclaing to cancel out that scaling factor. But again I don't know how it was applied.
UPDATE: I think the issue solved by itself. I have been working remotely and connecting to a Windows machie with Abaqus via the Microsoft Remote Desktop (from a Mac mini). It seems the issue appears when I use Abaqus from the remote desktop. After closing Abaqus in that Windows machine, then using it in a second Windows machine, then back again in the first Windows machine now I see the cube as a cube. I guess the cause is the remote desktop because some software behaves differently and the visualization software Paraview just won't open.
UPDATE 2: I confirmed the issue indeed happens when connecting remotely with Microsoft Remote Desktop from my Mac computer. The issue happens even when using a Python script for generating the figures to avoid opening the user interface. When running the script directly on the computer figures are fine (i.e., the cube looks like a cube). Not sure if when connecting remotely with Microsoft Remote Desktop from a Windows computer the issue will be present.
I've flashed the MicroPython into the NodeMSU board based on 12E chip and have used the screen command in the terminal on OS X to run the REPL. It works a few seconds and the REPL resets.
I have no idea where is the problem ( I can write a few commands when the all my work clears and I see the MicroPython console from scratch.
without more information, this is a difficult issue to diagnose. basically, there are 4 possible causes of this behaviour:
power fluctuation causes the board to reset.
the board resets because the reset pin is physically set to gnd
the board resets because the reset pin is logically set to gnd
the function machine.reset() is called
steps to diagnose:
try a powered hub, separate power supply, different usb cable, different usb port to power your device and observe if the reset happens
inspect the board. see if there is a solder bridge between the reset pin and gnd (next to each other as seen on this image or between the pins on the reset button
and 4) here you need to look at the code in boot.py and main.py; both located on the internal filesystem on your board. You can get those files using webrepl of using the following code:
print(open('boot.py').read())
print(open('main.py').read())
If you print the content here we can inspect it with you.
alternatively, try reflashing micropython using the latest .bin from micropython.org and see if the clean version of micropython corrects the issue.
I have a problem with Windows Phone emulator in VS13, I am developing a quiz game.
When I run my program, virtual machine turns on, everything goes fine, after that it builds my program and finally it works, but only for several seconds.
I can do whatever I want during these seconds, I've even managed to start the game, but after 7-8 seconds the emulated phone screen turns gray.
I've checked what happens with the virtual machine in Hyper-V manager, it seems to stop due to lack of memory, am I right with this conclusion?
And if I'm right, what can I do to solve this problem with memory apart from upgrading my PC? :)
I'm using Windows 8 installed as a virtual machine via VMWare Workstation.
Here are two screenshots of my gray screen - one is WF emulator and the second one is the same screen, but opened via Hyper-V manager (it says "not enough memory" in the bottom line).
I am running into hardware issues that perhaps someone here knows a workaround. I am using a PC and windows.
For several years I have been making interactive installations using video tracking: the Jmyron library in Processing, which has functioned marvelously for me. I use this set up: cctv type microcameras to a multiplexer, the I digitize this signal via a firewire cable to a pci card. Then Processing reads these quads (sometimes more) as a single window, and it has always worked (from windows xp all the way to 7). Then comes windows 8: Processing seems to prefer the built-in webcam to the firewire bus. On previous version of windows, the firewire bus would naturally override the webcam, provided I had first opened a video capture in Windows Maker, and then shut it down before running the Processing sketch. In Windows 7, which had no native video capture software, I used this great open source video editor called Capture Flux. The webcam never interfered. With Windows 8, no matter what I try, Processing defaults to the webcam, which for my purposes is useless. I have an exhibition coming up real soon, and there is no way I am going to have the time to rewrite all that code for Open CV or other newer libraries.
I am curious if anyone has had similar problems, found a work around? Is there a way of disabling the webcam in Windows 8 (temporarily of course, because I need it to be operational for other applications), or some other solution?
Thank you!
Try this:
type "windows icon+x" choose device manager (or use run/command line: "mmc devmgmt.msc")
look for imaganing devices, find your integrated webcamera
right click on it and choose disable - now processing should skip the device.
Repeat the steps to reenable the device.
Other solution would be using commands in processing:
println (Capture.list()); (google it on processing.org) this way you will get all avaliable devices and you can choose the particular one based on its name.
Hope this helps.
I'm in an unusual spot. The built in screen on the laptop I'm using right now is broken so bad I can barely see anything besides random flickering lights on it. Because of that, I got and plugged in a monitor to my laptop. This moniter works fine once Windows 7 has already loaded.
The issue is: I'm trying to open the BIOS/boot menu to live boot off of my USB, but I can't see anything. How do I make it so that I get visual output on my monitor early enough to open the BIOS/boot menu?
If it's a Dell laptop, try FN&F1 or F1
Dell Forum