|
|
In 1.10.28 there have been changes concerning how the Windowed and Borderless modes are handled, unfortunately a couple of issues slipped through the net.
In both cases the "game area" will now expand to fill the (borderless) window while preserving the aspect ratio set on the game-side (4:3, 16:9, 21:9, 32:9). The excess boxing from varying prior situations is now gone. As far as Windowed mode goes specifically this has generated a few comments due to: 1 - If you have a 4:3 resolution set and you join a server (or create a single-player game) configured for Widescreen, the window will be resized to account for the "game/displayable area" in order to omit any visible boxing - this differential can be clarified by viewing the vid_currentmode command. 2 - Related to the above, if you then join a non-Widescreen server you'll notice that the "game area" area is scaled-down to maintain the aspect ratio within the limits of the current window dimensions. This case in particular has been highlighted; although it is being looked into, a workaround for now (if you want to quickly force the window to be resized) would be to create a bind similar to the following via the Console:
Upon joining a server with different display AR settings all you'd then need to do is press said key to instigate a window size reset. 3 - In Native Fullscreen mode if you're on a 4:3 server with a 16:9 resolution, you may find that the boxing control does NOT do anything until you press "Apply" under Video Modes; for now I'd recommend utilising the bind referenced above. |
Windows 10 -> 11 - ZDaemon Client has no sound (Re-published)
|
There have been at least a couple of reports concerning there being no sound in the ZDaemon Client after updating from Windows 10 to 11.
EDIT: In Windows 11 (and perhaps cases in 10 due to deprecation) there are unfortunately problems when it comes to DirectSound (there are various reports for other games as well). The in-client adjustment that will get around this problem is as follows: 1) Open the client 2) Bring down the console (Press ~) 3) Enter: snd_output "waveout" 4) Execute: snd_reset You will then see a number of notices concerning sound being initialised. Once that has been done, check to see whether there is any sound. Thanks go to Alc_136 for highlighting this case. A non-console function will be accounted for in ... |
ZSMulti 0.71 Released - Multi Server Launcher
|
A new version of the ZDaemon Multi Server Launcher has been released:
ZSMulti 0.71 Changes/Fixes: - Fixed an issue concerning configured WAD directories. - Updated the internal template to account for the latest preset variables.. - Added IP detection; it'll now list and store the detected IP addresses; those stored IP addresses can now be selected if a specific binding address needs to be set on one or more instances. |
Upcoming support for unknown gettable things - 1.10.20
|
In the next ZDaemon release - 1.10.20 - support will be added when it comes to the touching of unknown or unusual gettable things.
This to be quite blunt is down to two major bits of madness that go back to the days of Vanilla DeHackEd as a result of item effects being linked to their originating sprites within the engine, and being able to apply said behaviour based on the sprite to states on a given thing that isn't normally used for pickup purposes. An unusual gettable thing is a non-inventory actor with an Initial frame set to a state from an actor that is part of the Inventory hierarchy within the engine. In versions prior to 1.10.20 if you attempt to interact with such an item then the following will occur: 1. Nothing (... |
ZLauncher dialogues not appearing or displaying correctly - Windows 10
|
If for whatever reason this is being experienced, one cause has been narrowed down.
You'll want to do the following: 1) Open the Control Panel (View by Large Icons if necessary) 2) Click Region 3) Go to the "Administrative" tab 4) Click "Change system locale .." 5) Disable the following option: [ ] Beta: Use Unicode UTF-8 for worldwide language support A system restart will be required for the change to take effect. It must be stressed that this appears to be one of the common causes. If there are others they've yet to be discovered. Edit: In the case of some dialogues (and/or contained items) not being displayed correctly, this is down to a missing font in Windows 10 "MS Sans Serif" (Not "Microsoft San... |