Testing the new client version via beta mode in RyZtart

#1 Added by Tamarea 1 year ago Report | Quote Multilingual

An update of Ryzom has been made by applying the recent Ryzom Core changes.
These changes include many fixes, but may also bring bugs.Although we have already tested many of these changes, it is very difficult to test the whole game under the same conditions as on Atys.

This is why RyZtart has now a BETA-TEST option, a simple checkbox that allows you to get the new client patch before everyone else. So you can test and report any bugs.
To come back to the stable version of Ryzom, you just have to uncheck the beta test box.

For MacOS players, as RyZtart is not yet available,, you can contact Ulukyn (https://chat.ryzom.com/direct/Ulukyn) who will tell you how to proceed.

You can report any bug concerning this update either by ticket to Support or by replying below.
Topic in forum

Edited 7 times | Last edited by Maupas (1 year ago) | Reason: Titles' typos

---

Tamarea
Ryzom Team Manager
(FR / EN / ES)
tamarea@ryzom.com

#2 Added by Ulukyn 1 year ago Report | Quote [fr]

Bugs reported

- FMod driver crash the client
- Classic titles can be applied, but encoding issues happens
- Special titles can't be applied

Bugs fixed

- A bug with teleport loading screens (texture are missing)
- A bug reset the whole interface if you talked to a player with a title containing non-ascii characters

Edited 8 times | Last edited by Ulukyn (1 year ago)

#3 Added by Yovung 1 year ago Report | Quote [en]

Beta 889

Hello,

* when I launched my client today all settings where reset (open windows on desktops, date in compass, timestamps in chats...)

* on gubani wheel when the reward choice is displayed (tokens or rewards), the left half displays a red rectangle background - screen capture available.

thanks,
Yovung.

Going on with my small bugs report^^
Beta 891 now - linux x64 through ryztart on linux mint 20.1, en interface

* Still have to reconfigure my desktops at client start
* Impossible to change my daily missions settings. changes don't apply, even after using "preview and save preferences"

Last edited by Yovung (1 year ago)

#4 Added by Ulukyn 1 year ago Report | Quote [en]

Enabling Fmod drivers in windows crashes the client.

Fmod driver is deprecated and will probably be removed in a future release. Same for DSound (https://github.com/ryzom/ryzomcore/issues/65)

If you get issues with Xaudio2 or OpenAL, please open a ticket in https://github.com/ryzom/ryzomcore/issues/

Edited 5 times | Last edited by Tamarea (1 year ago)

#5 Added by Kaetemi 1 year ago Report | Quote [en]

Ulukyn

Fmod driver is deprecated and will probably be removed in a future release. Same for DSound (https://github.com/ryzom/ryzomcore/issues/65)

We cannot support the FMod backend from the open source end, since the version of FMod is no longer available, and thus cannot be licensed anymore. It also misses some features.

DSound should be kept as reference implementation, even if incomplete, since it's what the sound artists originally used. Specifically the 'EAX' reverb effects are not yet fine tuned to sound the same across all drivers. No need to ship DSound to players, though, since it's not useful there.

(The EAX effects were never implemented in FMod at all, by the way, the setting does nothing there. They do work in XAudio2 and OpenAL, but don't match the reference exactly.)

Last edited by Kaetemi (1 year ago)

---

Kaetemi

#6 Added by Ulukyn 1 year ago Report | Quote [en]

A bug reset the whole interface if you talked to a player with a title containing non-ascii characters

It is now fixed

#7 Added by Ulukyn 1 year ago Report | Quote [en]

Update:
- Classic titles can be applied, but encoding issues happens
- Special titles can't be applied

Encoding issues can happen since it's a big change in core4

#8 Added by Kaetemi 1 year ago Report | Quote [en]

As noted before, to fully merge the encoding changes:
- Remove `#define RYZOM_LUA_UCSTRING` to completely eliminate ucstring support from lua & ui expressions.
- Then remove all ucstring, toUtf8(), and uc_ prefixes from your lua & xml scripts.
- Add `localize="false"` to the `npc_web_browser` container title.

That should eliminate all encoding issues, since everything will be UTF-8.

But it may be tricky with two different client versions, since you also have scripts server-side...
For most cases you should be able to eliminate the ucstring from the scripts first, after the client is patched for everyone, since regular string will be UTF-8 already. Then disable the macro afterwards.

Edited 4 times | Last edited by Kaetemi (1 year ago)

---

Kaetemi

#9 Added by Kaetemi 1 year ago Report | Quote [en]

You may want to put some breakpoints in the `ucstring` operators, since those do take std::string without converting for some reason... Maybe just make those use `fromUtf8` as well, I don't see the use case for bypassing the encoding there.

---

Kaetemi

#10 Added by Giselher 1 year ago Report | Quote [de]

The Tribe called "Kuilde" from the Nexus region is missing on my fame-list... :-)

#11 Added by Erenkyl 1 year ago Report | Quote [fr]

je constate qu'il y a une différence dans les fenêtres d'info du Bêta, les descriptions sont plus espacées.

Les renommées des tribus ne sont plus par ordre alphabétique, mais bien mélangés, complique l'affaire pour voir rapidement si on peut entrer dans leur camps.

Edited 3 times | Last edited by Erenkyl (1 year ago)

#12 Added by Erenkyl 1 year ago Report | Quote [en]

Pour les briques acquises depuis que je suis sur le bêta
la petite fenêtre de description au passage sur la brique, sont écrit - DÂ@gâtt au lieu de - dégâts d'acide par exemple.

dans info pour les équipements et armes , le lignes sont très espacées pour les armes les charges de sève et points de vie les détails sont l'un sous l'autre au lieu d'être l'un a coté de l''autre, c'est plutôt illisible.
et Compétence les mots un sous l'autre.
l'espacement enlève la vue d'ensemble.

je ne sais pas si c'est ce genre d'info qu'il vous faut,

#13 Added by Jorgensen 1 year ago Report | Quote [en]

Minor bug found in beta 893

Action Progression Window Skills Tree View not behaving as expected.

https://imgur.com/a/3lenPuJ

Notice how when the Heavy Pants node is expanded, it causes all the other heavy armor parts to disappear from the child list of Heavy Armor in the Tree View.

#14 Added by Kaetemi 1 year ago Report | Quote [en]

Jorgensen

Notice how when the Heavy Pants node is expanded, it causes all the other heavy armor parts to disappear from the child list of Heavy Armor in the Tree View.

Disable the Auto-Fold checkbox.

---

Kaetemi