Use new fallback config item #204
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I have tested it with Parsec 150-85c:
To continue using my VM I had to install another virtual display - usbmmidd_v2. |
|
The original setting should still work at this time.
Quit the Parsec app in the VM entirely (no tray icon, no parsecs.exe) and
add the config line.
After that, you can confirm it's applied by changing any UI setting in the
app; the added config line will stay. For troubleshooting's sake, also
manually change the bitrate or similar to something that can't be normally
set in the UI (e.g; 11Mbps). It will ALSO stay, and the UI will show an
incorrect value (11 is not in its list)
…On Tue, 20 Sept 2022, 10:30 Klemens Starybrat, ***@***.***> wrote:
I have tested it with Parsec 150-85c:
- host_virtual_monitors = 1 is ignored, as I understand this is
expected because free edition no longer respects this setting
- host_virtual_monitor_fallback = 1 does not work because there *always
is* another display present - Hyper-V display; in my case (Win 11
hypervisor and guest) disabling Hyper-V display in the guest, as the script
in this repo does, does not prevent the guest system from detecting a
connected virtual display. Uninstalling Hyper-V display in the guest does
not help either - it automatically readds itself.
To continue using my VM I had to install another virtual display -
usbmmidd_v2 <https://www.amyuni.com/forum/viewtopic.php?t=3030>.
—
Reply to this email directly, view it on GitHub
<#204 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD6U6B5SPFDUDGKHSIMN5E3V7F73XANCNFSM6AAAAAAQFXA5LY>
.
You are receiving this because you were assigned.Message ID:
***@***.***>
|
|
Thanks, that fixed the issue with |
|
This project relies on the virtual displays, so it will remain. If/When fallback works in the case of these VMs, it may change, but you'll have working fallback |
|
Closed until fallback works in cases where the available displays are not capturable |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Needs testing
In Parsec build 150-85, we added a feature to use our virtual display driver to create a fallback display, if the feature is enabled (disabled-by-default).
This is a better solution that what this project currently does to enable the virtual displays, but I don't have the time to test it myself.
This should reliably create a virtual display to capture, but only if there are no other displays present.