Nota
Thank you to everyone who donated︎!
We have raised over 600€ in addition to our usual budget. Check out the results in our progress report.
Acerca de
Overte es un software de código abierto de mundos virtuales y realidad virtual que te permite crear y compartir mundos virtuales como experiencias de realidad virtual (VR) y de escritorio. Puedes crear y alojar tu propio mundo virtual, explorar otros mundos, conocer y conectar con otros usuarios, asistir u organizar eventos de realidad virtual en directo y mucho más.
Overte provee las siguientes funcionalidades clave:
Creación y edición colaborativa de mundos
Soporte de VR, incluyendo seguimiento corporal
Escalabilidad de hasta 500 usuarios en un solo mundo
Programación en JavaScript, que permite la creación de juegos, elementos interactivos, elementos de interfaz de usuario y aplicaciones personalizadas
Audio espacial de alta calidad y baja latencia
Física potente gracias al motor de física Bullet
Completamente de código abierto bajo la licencia permisiva Apache 2.0
Sin autoridad central. Puedes gestionar tu propio servidor desde casa.
No requiere cuenta de usuario
Soportado por una organización democrática sin fines de lucro
Obtenga Overte o hecha un vistazo a nuestra Galería
.
Únete a nuestro espacio de Matrix en overte:overte.org 🔗. Nuestro espacio de Matrix también está conectado a
Discord 🔗.
Reunión de desarrollo en la oficina de Overte
Noticias
2025-12-17 Monthly progress report
This month, I decided to change it up a bit and report on the progress to date, instead of only to the end of last month.
Overte e.V. general assembly 2025
We held our annual assembly on the 6th of December. The highlights include: - 2024 and 2025 both our income and our expenses were way higher than expected. - Our financial prospect for 2026 is good. We should be okay, even if we were to not complete any grant work. (Though donations are always appreciated, since my this assumes my work contract running out at the end of July 2026.) - Our accounting auditor found no issues. As in previous years, they extended their audit into governance and administration and found no issues or new recommendations. - We got a new honorary member within our ranks. - The board can now arbitrarily set the membership fee of non-natural persons (e.g. companies). A detailed protocol was sent to all Overte e.V. members via email today.
Progress
74hc595 spent way too much time working on way too much stuff again 😉. Taking a break from Qt6, they have resumed work on getting Vulkan merged. (I literally got almost 70 email notification just from the Vulkan Pull Request.) They diagnosed and fixed performance issues which were stalling our upgrade to libnode 22. Of course, they also did their usual spree of general contributions like reviewing and testing Pull Requests, in addition to some smaller PRs.
Ada continued work on their UI overhaul, while also continuing to improve OpenXR support, adding better OSC support, and working on adding local lights to the forward renderer. As always, Ada also did a huge amount of other miscellaneous stuff.
HifiExperiments has been helping with all the graphics related changes and fixed OpenGL ES support.
RTUnreal spent a lot of time bumping their head against more or less random build system issues again.
I (Julian Groß) spent my time with small things as they popped up, including working on the next stable release.
We got a new contributor this month: Zedwick has been helping out with updating the documentation and fixing issues with both the chat and the Nametags app.
Part of the team went on holiday in Warszawa during the first week of December.
2025-11-22 Invitation to the Overte e.V. general assembly 2025
Saturday, December 6th at 19:00 UTC we will hold our annual general assembly for the Overte e.V. in Overte. While only active Overte e.V. members are allowed to vote, non-Overte-e.V.-members are also welcome to attend.
The planned agenda is as follows:
Decide on assembly leader.
Decide on assembly secretary. The secretary will fill out the protocol during the assembly.
Accounting report for 2024 and 2025.
Budgeting for 2026.
Accounting auditor report (Steve Pruneau).
Do we have someone that would like to become the accounting auditor? The accounting auditor cannot be a board member.
Board report.
Board member elections.
Vote on allowing the board to set membership fees for non-individuals at their discretion. [1]
Vote on hiring Julian Groß as done through board decision on 8th of July 2025. [2]
Vote on by-law change to specifically mention “approval voting” as the used board election system [3]
Protocol gets signed by the assembly secretary and assembly leader.
[1]: Currently, non-individuals (e.g. companies, universities) pay the same 60€ yearly membership fee as everyone else. Some bodies may be willing to pay more but cannot donate due to legal reasons.
[2]: The board already hired Julian Groß in accordance with § 6 The Board (3) Duties ( https://satzung.overte.org/en/#aufgaben ). The assembly should still vote on it to back the board in its decision (or fire me).
2025-11-05 October progress report
Progress
74hc595 again spent most of their time working on upgrading to Qt6. While chasing down crashes on Qt6, they uncovered and fixed multiple old memory safety issues, which have probably been causing issues for years now. Of course, they also did their usual general contributions like reviewing and testing Pull Requests.
Ada spent a lot of time working on their new UI overhaul, which is part of the upgrade to Qt6. Here are some work-in-progress screenshots:

HifiExperiments has been working on a fix for the FBX texture coordinate regression 🔗.
RTUnreal has been fixing C++ build issues, both for Qt6 and our move to C++20. Without him, a lot of maintenance work would be stuck waiting for Qt6 to be finished.
I (Julian Groß) spent most of my time with small bits and bobs, including the stable release, support, finishing the GitHub Actions refactor, and fixing smaller regressions, which were introduced by all the large changes which were merged recently.
Release!
We made another release. Version 2025.10.1 (and 2025.10.1.1 hotfix), which includes only bugfixes; Most importantly, a fix for AppImages crashing on Arch Linux, and a fix for OpenXR support not working on NixOS. It is available here 🔗. After the hotfix, we noticed a packaging issue which caused Fcitx support to not work. This has also be resolved, so get the "Fcitx_support" AppImage if you are having issues with using your IME in Overte.
2025-10-13 September progress report
Organizational
"AI Cryptocurrency Investment" scammers
Too long; didn't read: We fell victim to scammers and lost >190 €.
September has been a very busy month for me as the accountant. Our organization fell victim to a group of "AI Cryptocurrency Investment" scammers, who try to use our identity to build trust with their targets.
On the 12th of September, we started receiving multiple payments of around 250€ each on our bank account, which were seemed not intended for us. I (Julian Groß) didn't notice these payments initially, as I had already done the monthly accounting and didn't check our bank account. On the 15th of September, we started receiving payments on Stripe, which is our credit card payment provider, as well. Since I got an email notification about those, I knew of them pretty much immediately. Nothing seemed weird there at first; The transactions were using our donation form, so they were clearly labelled as donations. What was odd was that we would suddenly get such large amount of donations in the first place. And, looking closer at them, multiple people were supposedly sharing email addresses. At this point, I started reading through Stripe's documentation and contacted Stripe. Unfortunately, they were very unhelpful. Their documentation suggested this being a card testing scam, and that we should immediately refund everything. Their support was extremely slow, AI translated, and never had anything helpful to say. This is where the first mistake happens as well: I follow Stripe's advice and press the refund button on all the transactions. What I didn't notice at the time, was that Stripe keeps their fees. Meaning that on every refund I make, the Overte e.V. pays a hefty credit card fee. Multiple Euros per transaction. In total, we lost 163,50 € in Stripe fees. Once I noticed this the next day, I started returning only what was left after Stripe's fee. While that saved us from another losing another >100 € in Stripe fees, it ended up incurring a chargeback from one person who really wanted their 1,86 € back. As it turns out, Stripe (and credit card companies) charge 20 € per chargeback. Not to mention the bank responsible for the chargeback graciously rounded up the sum to 1,95 €. Contesting chargebacks incurs another 20 € fee. So I decided to just pay up.
In the meantime, I noticed transactions also going straight to our bank account. This felt way less problematic, since the fees are way lower than for credit card stuff, and we have rule of law there, rather than credit card companies and payment providers just offloading everything onto us. At this point, I got in contact with the Police, since the victims suddenly had names and identities, and as opposed to our Stripe account, I wasn't willing to just close it off. The local Policeman knew immediately what was going on and asked me to inform the victims by sending them messages via SEPA bank transfers. Turns out, instant bank transfers are faster than the police. At least as long as the victims check their bank accounts regularly.
Apparently, this is a very common scam: - The scammers rope their victims in with promises of high-return investment opportunities. - They then have their victims pay a smaller sum to a place that feels trustworthy; In this case, a German bank account. Since it is a German bank account, at least the German victims have little to worry about. If it is a scam, they have someone they can hold accountable. None of this money actually makes it to the scammers. - The scammers then show their victims how much money their investments are allegedly making, and are offering them to invest larger sums. At this point, they have their victims pay money to a channel they have control over. In this latest case published by Eurojust it was mainly Lithuanian bank accounts.
While our bank was slow to respond, they were extremely helpful. They immediately knew what was going on, and offered to screen the transactions for us, meaning I didn't have to return the money manually anymore and didn't have to account for them in our books either, since they never actually make it onto our bank account.
The scam is still going on, but has slowed down considerably. Only one of the scammers appears to remain, and I now know what to do with any fraudulent transactions we receive.
So what did we learn from this? - The saying "Never look a gifted horse in the mouth" doesn't always apply. - We are legally required to pay back any money that wasn't intended for us. (See BGB § 812) - Credit card is an awful way of receiving donations, because it leaves you vulnerable to chargeback and contesting fees, and generally costs way more than even international and inter-currency transfers.
What are the next steps? I am still considering to completely stop accepting donations via Stripe. While the 163,50 € of fees was my fault to some degree, the chargeback fees are something we cannot do anything about with our current setup. Some donators already switched over to donating via bank transfer instead. Meaning that we receive so little money via Stripe now, that just two chargebacks per month are enough to completely negate the money received from there. At that point, I would need to shut that channel down. We could still decide to accept credit card payments via email then; Or maybe we can find some other payment provider who takes over such fees.
If you have any suggestions, questions, or input on this, feel free to reach out via our usual channels.
Infrastructure
Our Weblate translation instance has been slow or inaccessible for most of September due to crappy Chinese AI scraping bots. While this is probably not a deliberate attack, it manifests the same as a distributed denial-of-service attack on our infrastructure.
Anubis has been deployed to our Weblate instance, but unfortunately the low percentage of scrapers that do get through are still occasionally enough to overwhelm the server and flood us with error messages. Due to this, I had to shut down the server for multiple days. While it has been running without issues again for a couple of days now, it might get overwhelmed again until a solution is found.
Weblate added the option to back up individual projects, instead of the entire server, so we are currently looking into moving to a public Weblate instance. So far, this has been a slow process though: - hosted.weblate.org allows creating said backups, but it currently doesn't allow actually restoring them. - translate.codeberg.org doesn't currently support pushing to GitHub and still hasn't made a formal decision if they want to. We also haven't been able to reach their admin yet.
We are not aware of any other public Weblate instances.
There are some other open-source organizations hosting their own Weblate instances, so we might try to join with one of them.
Alternatively, we will just have to upgrade our server and/or pay for something that lets fewer bots through, like Anubis' "Thoth" service.
Progress
74hc595 spent most of their time working on upgrading to Qt6. Apparently, the Qt6 branch already works, even if it is still very unstable. Of course, they also did their usual general contributions like reviewing and testing a lot of Pull Requests.
Ada has been helping with the Qt6 upgrade, focusing on QML related fixes. They also committed some smaller fixes like fixing OpenXR trigger click reliability, in addition to reviewing, testing and reporting bugs, and prototyping their upcoming UI theming support.
HifiExperiments helped with a lot of triage, advice, and code review.
RTUnreal worked up upgrading dependencies and has generally been helping with build system maintenance.
I was mostly busy with handling the recent scam and the flood of broken Chinese AI scrapers. In addition, I worked on refactoring our GitHub Actions workflow files (shoutout to RTUnreal for the code review), fixed some smaller build system bugs and troubleshot regressions. I also started initial work on an itch.io release: Finding regressions introduced multiple releases ago isn't fun and showcases that there just isn't enough testing happening. This suggests that it is about time to try to get more users in. When this release will happen isn't entirely clear yet; We have an upcoming protocol changing release which will undoubtedly introduce more not-yet-known regressions, as well as require all servers and clients to be updated.
We also received bug reports and help from Alezia, Dale, and Krzeszny. Big shoutout also to KawaneRio for organizing Sunday's "Overte warmup" event.
Release!
We made our first release since switching from VCPKG to Conan. Version 2025.09.1 and its changelog are available here 🔗 and come with a huge list of bug fixes, improvements, additions, and changes. It does come with a regression that causes it to crash on many on some Linux distributions when opening a web view, like the Places app. A fix will be included in the next release. For now, affected users can get the CI testing build from GitHub or keep using version 2025.05.1.
2025-09-07 August progress report
Organizational
Employment
Last post we asked for donations in case unforeseen costs come up with my (Julian Groß) employment. As it turns out, the employment does indeed cost a little bit more (~30€) than I anticipated, costing around 1000€ per month, roughly 710€ of which actually end up on my bank account. (I say “around” and “roughly” because most months cannot be cleanly divided by 4 weeks.)
I want to personally thank everyone who donated. Most of the people who donated appear to be new people who had never even tried Overte before donating. I also want to specially thank our regular donators and paying Overte e.V. members, who keep Overte running. You know who you are, and you rock!
Next time, I should have the donation banner count all money paid towards the Overte e.V., instead of just extra funds on top of the regular donations minus transaction fees. I did it this way for accounting purposes and that was probably just a bad idea.
NLnet grant
In other news, the NLnet Foundation has accepted another grant (amendment) proposal from us. After having been successfully working with them for over 1 1/2 years now, it feels great to still be among all the amazing open source projects supported by them.
We want to thank NLnet and the European Commission for fostering software freedom with their Next Generation Internet programme.
Plan del Proyecto
The funding will be used to pay developers to work on the areas listed below.
Características
Multi-packet avatar updates
linear interpolation for avatar updates
Finish multi-packet entity properties
Gráficos
Vulkan frame transfer to VR plugin
Mantenimiento
Switch to using a package lock file on Conan and updating it semi-automatically using something like Renovate
Try getting NSIS more foolproof (boolean checks are unreliable as they only check for one possible boolean naming scheme)
Document networking code
Corregir errores
Fix networking congestion control ( https://github.com/overte-org/overte/issues/572#issuecomment-2799907780 )
Fix retransmissions ignoring congestion control ( https://github.com/overte-org/overte/issues/572#issuecomment-2799907780 )
Entity Transition Shader (Fade)
We have a special shader that makes user appear as if they were "beaming in" or "beaming out" when connecting or disconnecting. Apparently, there is unfinished support for doing this to other entities as well, which we would like to fix/finish and polish. This can be used for multiple purposes, but playing similar animations when people edit worlds, for example by deleting entities, is what got us to look into this.
Add/fix entity transition shader
Expose avatar and entity transition shader as zone properties
Expose entity transition shader to Entities.addEntity and Entities.deleteEntity (overriding zone properties)
macOS support
With the Vulkan PR almost merged into master, Apple getting rid of OpenGL isn't a blocker to our macOS support anymore. However, macOS support was broken for multiple years, always was on the back burner, and we moved build systems in-between, so this is a bit of a larger job. We have a good amount of macOS users who are willing to test, and even some people who are still running our last macOS version, eagerly waiting for a new one.
Get macOS development machine
Build with MoltenVK
Get all of our Conan packages to build on macOS
Fix the server software crashing on macOS
Set up automatic macOS CI builds
Android support
With the new Conan dependency manager, overhauled build system, and experience with Conan, CMake, and our build system, I now feel comfortable tackling Android support. We used to have experimental Android support, but Google changed so much of their build system API for C++ that that part needs to be completely rewritten.
Get all of our required Conan packages to build for Android
Add Android support to our build system
Set up automatic Android CI builds
Add initial OpenXR support to our Android client
Depot.dev
Overte got its first corporate sponsor: Depot.dev 🔗 is graciously providing us with their Continuous Integration services for free.
With us needing to build Qt from source on Windows, the free GitHub hosted Runners were timing out because our builds would take over 6 hours any time there was a Qt package cache miss. So we needed a solution which didn't involve constant babysitting of the CI pipeline, which would have defeated the point of having a CI pipeline in the first place. Getting faster Runners from GitHub would have costed us upwards of 2000€ extra per year, which frankly would have broken the bank.
This is where Depot.dev comes in. Not only are they way cheaper than GitHub hosted Runners and provide a lot more cache space, but they also offer discounts for non-profits and open-source projects.
Interesting enough, even the same spec runners on Depot.dev are actually quite a lot faster at building Overte than the ones on GitHub already.
Progress
Frankly speaking, so much stuff got done this month that I am having a hard time deciding what to mention.
On my side, I have spent most of my time with fixing up our Qt package for Windows and doing more build system improvements. Big thanks to 74hc595 for finding lots of additional issues in my Qt package. 😅 Together, we found out that release builds were actually building with Qt asserts enabled. Asserts are basically deliberate crashes, which exist to make us developers aware of something unexpected happening. They shouldn't be enabled in a release build, as the application often continues to function even when something we didn't expect happens. It's quite frustrating working on something that takes three hours to build any time there is a change on an operating system you aren't usually developing on, but I am quite happy with the results.
Thanks to NLnet, I also started working on macOS support. For now, I got all the required dependencies to build and am waiting for Vulkan to be merged and our update to libnode 22 to be finished.
74hc595 did a lot of work as usual. They fixed multiple audio issues, helped a lot with getting Pull Requests finished, tested and merged, fixed that weird bug with people starting floating while having their camera zoomed into the back of their heads, fixed multiple crashes on Windows, … you get the idea.
Ada also did a lot of miscellaneous bug fixes, but also upstreamed their Context menu, fixed a lot of issues with VR and OpenXR, added OpenXR body tracking support, added multiple new JavaScript APIs, et cetera. We keep merging Pull Requests and Ada keeps opening new ones.
HifiExperiments added initial VRM file format support, fixed remaining issues with his new multi-layered materials, and helped Ada and 74hc595 with graphics work as usual.
Alezia worked on improving the Snap app, added bookmarks and per-Place user counts to the Places app, and cleaned up the Places app's code.
We also got a new contributor this month: RTUnreal started work on packaging Overte for NixOS. To that end, they already added support for our build system to use only system libraries, uncovered and fixed some bugs, and have been a huge help with the libnode 22 upgrade. Considering how many people already dabbled with trying to build Overte using Nix and gave up once they realized how much work it is going to be, it is especially great to see RTUnreal get changes merged into Overte.
Release candidate!
On the topic of progress: We tagged our first release candidate since switching from VCPKG to Conan. Version 2025.09.1-rc1 and its changelog are available here 🔗 and come with a huge list of bug fixes, improvements, additions, and changes. So far, this release candidate has been rock solid, so it might turn into a full release already next week without any additional changes necessary.
2025-06-07 ¡Ayúdanos a contratar a un miembro del equipo!
Estamos en proceso de contratar a nuestro colaborador Julian Groß, lo que le permitirá dedicar más tiempo a Overte y sacar adelante los proyectos.
La propuesta actual consiste en un contrato de un año por 13 horas semanales con el salario mínimo alemán. Aunque no es mucho, es suficiente para que Julian sobreviva y haga de su trabajo en Overte su profesión principal.
Sin embargo, aunque Overte e.V. puede permitírselo, técnicamente estamos al límite. Por eso pedimos tu apoyo!
Necesitamos mantener un colchón financiero en caso de costos imprevistos, por lo que estamos realizando nuestra primera recaudación de fondos para alcanzar nuestra meta de 3000 € de fondos adicionales en los próximos meses.
2025-04-04 ¡Hemos obtenido otra subvención de NLnet!
Tras el éxito de nuestra anterior subvención, que permitió realizar innumerables correcciones, mejoras y nuevas funciones, nos complace anunciar que hemos obtenido una segunda subvención de NLnet!
La Fundación NLnet continúa apoyando muchos proyectos sorprendentes de código abierto y nos sentimos honrados de seguir colaborando con ellos.
Al igual que con la subvención anterior, nos comprometemos a mantener a los usuarios y desarrolladores al tanto de los avances realizados en estos aspectos, tanto durante nuestras reuniones habituales de desarrollo los sábados como en GitHub, para que todos puedan seguir el progreso.
Plan del Proyecto
Los fondos se utilizarán para pagar a los desarrolladores para que trabajen en las áreas enumeradas a continuación, con posibilidad de extensiones y trabajos adicionales.
La fecha límite acordada para la finalización es el 1 de diciembre de 2025.
Características
Nos gustaría permitir a los usuarios menos técnicos utilizar con mayor comodidad todas las funciones que ofrece el motor de scripting. Para ello, nos gustaría añadir un sistema de scripting visual.
Scripting visual (https://github.com/overte-org/overte/issues/982)
Mensajes de chat en espacio 3D (https://github.com/overte-org/overte/issues/1147)
Agregar los botones de cortar y pegar al teclado VR (https://github.com/overte-org/overte/issues/130)
Soportar el seguimiento de dedos de OpenXR (https://github.com/overte-org/overte/issues/224)
Funciones de criptografía en la API de scripting (https://github.com/overte-org/overte/tree/feature/cryptography)
Agregar traducciones en tiempo real al chat
Gráficos
Nuestro motor utiliza su propia API gráfica interna, que en gran parte no está documentada. Documentar esta API supone mucho trabajo y es importante para el mantenimiento futuro del proyecto. Además, nos gustaría dedicar más tiempo a la optimización de Vulkan, especialmente a la resolución de problemas de rendimiento en las tarjetas gráficas Intel Arc.
Optimización de Vukan
Documentación de la API de gráficos
Luces locales en materiales MToon (https://github.com/overte-org/overte/issues/1131)
Exponer la distancia de atenuación del mapa como propiedad de zona (https://github.com/overte-org/overte/issues/1139)
Utiliza el renderizado estándar basado en propiedades físicas para los vóxeles (https://github.com/overte-org/overte/issues/749)
Permitir cambiar entre API de gráficos a través de la opción de línea de comandos
Añadir la funcionalidad de splat mappin (https://github.com/overte-org/overte/issues/1163)
Añadir un modo de filtrado de texturas sin filtro (https://github.com/overte-org/overte/issues/145)
Localización QML
Dado que Overte es utilizado por usuarios de todo el mundo, queremos añadir compatibilidad con la localización. Esta tarea tiene como objetivo permitir la traducción de todas las interfaces de usuario internas creadas con QML. (La mayoría de nuestras interfaces de usuario, aunque no todas, utilizan QML.)
Marcar cadenas como traducibles
Generar archivos de traducción automáticamente
Conectarse al sistema de traducción Weblate
Construir con traducciones
Verificar si incluimos los tipos de letra requeridos
Agregar traducción al alemán (como caso de prueba)
Mantenimiento
CMake 4.0 está a la vuelta de la esquina y dejará de ser compatible con algunas versiones anteriores, lo que parece afectar a casi todas nuestras dependencias. Libnode también ha recibido actualizaciones, incluyendo cambios importantes.
Actualizar Overte para compatibilidad con CMake 4.0
Corregir dependencias de compilación sobre CMake 4.0
Actualizar libnode a la próxima versión LTS
Mejorar las instrucciones de compilación para KDevelop y CLion
Agregar compilaciones en contenedores Docker de manera automática
Finalizar el despliegue de Overte en Flathub
Actualizar a Qt 6 (https://github.com/overte-org/overte/issues/1243)
Empaquetar las dependencias de Qt 6 para Windows
Empaquetar las dependencias de Qt 6 para Linux
Empaquetar webrtc-audio-processing
Migrar a libdatachannel
Corregir errores
Corregir el problema por el que los materiales MToon no se muestran en el Inspector de materiales (https://github.com/overte-org/overte/issues/1028)
Entidades de texto: mostrar el carácter tofu en el carácter faltante (https://github.com/overte-org/overte/issues/1133)
Añadir una "lista de bloqueados" con controladores gráficos defectuosos conocidos
Arreglar en que la consola del servidor intente conectarse a highfidelity.com (https://github.com/overte-org/overte/issues/578)
Corregir el spam de mensajes de advertencia QML en Windows (https://github.com/overte-org/overte/issues/593)
Corregir los problemas con HifiControlsUit.SpinBox (https://github.com/overte-org/overte/issues/921)
Solucionar el problema de la desinstalación de Overte que no elimina el caché de AppDataLocal (https://github.com/overte-org/overte/issues/952)
Corregir los marcadores de avatar que fallan silenciosamente debido a una sintaxis incorrecta (https://github.com/overte-org/overte/issues/192)
Rediseño de la UI
Nuestra interfaz de usuario actual combina diferentes temas, filosofías de diseño y lenguajes de programación (https://github.com/orgs/overte-org/projects/8). En concreto, nuestra aplicación Create podría mejorarse (https://github.com/overte-org/overte/issues/1145).
Marco para aplicaciones QML predeterminadas
Rediseño de la app Avatar
Añadir sombreador de cuadrícula a Create
Permitir que se pueda cambiar entre ventanas externas e integradas en Create
Rediseñar el navegador de activos
Rediseñar el modo de edición del voxel
Permitir entidades padre mediante arrastrar y soltar en la lista de entidades
Agregar vista de árbol a la lista de entidades
Agregar un modo de cámara libre en Create
Mejorar la gestión de materiales en Create
Agregar escalamiento centrado en Create
Rediseñar la app More
Rediseñar configuración
Rediseñar la app Pal (Lista de personas)
Rediseñar el visor de logs
Rediseñar la app Snapshot
Rediseñar la app Emote
Rediseñar la ventana de scripts en ejecución
Rediseñar la app Places
Rediseñar notificaciones
Agregar soporte para temas
Definir el uso de la ventana de selección de archivos del sistema
Agregar un dashboard a la interfaz de usuario
Integrar los resultados de la revisión de la experiencia del usuario y la auditoría de seguridad
Revisar la experiencia de usuario (UX)
Realizar una auditoría de seguridad
Agradecimientos
NLnet, por al apoyo continuo a Overte.
Julian Groß, por negociar este acuerdo.
A todos los desarrolladores que han aceptado asumir este trabajo.
A la comunidad Overte por hacer esto posible.
2024-04-16 ¡La subvención de NLnet se extiende nuevamente!
Hemos obtenido otra prórroga de la subvención de NLnet, con los siguientes elementos adicionales:
Mantenimiento
Corregir advertencias y permitir activar la opción de tratar advertencias como errores (https://github.com/overte-org/overte/issues/930)
Limpiar Application.cpp para que no tenga 10,000 líneas (https://github.com/overte-org/overte/issues/931)
Corregir el establecimiento de datos de articulaciones por nombre (https://github.com/overte-org/overte/issues/613)
Reemplazar el antiguo sistema de wearables con entidades de avatar. (https://github.com/overte-org/overte/issues/932)
Entidades de texto
Nuestras entidades de texto necesitan atención. Son poco prácticas y, lo más importante, utilizan un formato personalizado que no está documentado en ningún lugar; esto impide agregar nuevas fuentes, lo cual es especialmente grave porque las actuales solo admiten caracteres ASCII.
Recortar en los bordes en lugar de desaparecer completamente (https://github.com/overte-org/overte/issues/583)
Cambiar a un formato de fuente estándar (https://github.com/overte-org/overte/issues/126)
Mejoras gráficas II
Añadir color de luz ambiental (https://github.com/overte-org/overte/issues/6)
Cargar materiales MToon directamente desde glTF (https://github.com/overte-org/overte/issues/933)
Recorte de cámara opcional (https://github.com/overte-org/overte/issues/618)
Mecanismo de respaldo para sombreadores personalizados (https://github.com/overte-org/overte/issues/640): uno si un sombreador falla al cargarse/compilar, y otro si el usuario tiene deshabilitados los sombreadores procedimentales
Exponer más ajustes gráficos (mapeo de tonos, bloom, sombreadores procedimentales, AO) (https://github.com/overte-org/overte/issues/740, https://github.com/overte-org/overte/issues/741, https://github.com/overte-org/overte/issues/14)
Añadir propiedades de mapeo de tonos y oclusión ambiental a las entidades de zona (https://github.com/overte-org/overte/issues/934)
Mejoras varias II
Añadir suavizado láser VR, que será especialmente útil para personas con manos temblorosas (https://github.com/overte-org/overte/issues/883)
Mejorar el sistema actual de prioridad de entidades tipo avatar (https://github.com/overte-org/overte/issues/834)
Añadir la opción de no mostrar el avatar hasta que se carguen sus entidades (https://github.com/overte-org/overte/issues/834)
Mejorar el sistema actual de prioridad de carga (https://github.com/overte-org/overte/issues/834)
Añadir una propiedad para influir en la prioridad de carga de las entidades (https://github.com/overte-org/overte/issues/834)
2024-04-02 ¡Subvención de NLnet extendida!
Hemos obtenido una extensión de la subvención de NLnet, con los siguientes elementos adicionales:
Soporte para FHS en Linux
El estándar Linux Filesystem Hierarchy (FHS) define la estructura adecuada de archivos para una aplicación. Este trabajo implicaría adoptarlo y además implementar algunas mejoras importantes.
Esto permitirá:
Facilitar la creación de paquetes e inclusión en distribuciones.
Facilitar la integración con SELinux.
Permitir instanciación sencilla desde el inicio.
Facilitar el empaquetado para Mac.
Tareas:
Implementación del servidor de dominio/cliente de asignación (https://github.com/overte-org/overte/issues/903)
Implementación de la interfaz (https://github.com/overte-org/overte/issues/904)
Soporte LDAP
LDAP es un mecanismo de autenticación común, ampliamente utilizado en las organizaciones. Active Directory también es compatible.
Esto ayudará a que Overte se integre mucho mejor en estructuras corporativas y universitarias. Podrían usar su propio sistema interno para controlar la autenticación. Nos ahorraríamos tener que escribir ese código nosotros mismos, el cual tiene poco interés y ya ha sido implementado mejor por otros proyectos.
Tareas:
Soporte básico en la interfaz de usuario web del dominio para permitir la autenticación de múltiples usuarios. (https://github.com/overte-org/overte/issues/905)
Soporte básico como alternativa al servidor de directorio: cuentas de usuario, directorio de dominio. (https://github.com/overte-org/overte/issues/906)
Alternativa completa al servidor de directorios. Soporte a relaciones entre usuarios, almacenamiento de datos y metadatos de perfiles. (https://github.com/overte-org/overte/issues/907)
Soporte para IPv6
La adopción de IPv6 ha alcanzado niveles buenos recientemente, y es especialmente importante en entornos con escasez de direcciones IPv4, como empresas, universidades, nubes y despliegues a gran escala. Algunos proveedores ya cobran extra por direcciones IPv4, por lo que soportar IPv6 ayuda a reducir los costos de alojamiento de dominios.
Tareas:
Soporte básico en la interfaz web del dominio. (https://github.com/overte-org/overte/issues/908)
Soporte para la descarga de recursos mediante IPv6 en la interfaz. (https://github.com/overte-org/overte/issues/909)
Soporte para dominios que operan sobre IPv6. (https://github.com/overte-org/overte/issues/910)
SELinux
SELinux es un sistema de seguridad que permite ejecutar aplicaciones y demonios en entornos aislados (sandbox).
SELinux aislaría el servidor de dominio y, opcionalmente, la interfaz, para garantizar que cualquier exploit no pueda afectar el resto del sistema. Por ejemplo, una vulnerabilidad en el dominio podría afectar al dominio, pero no permitiría usar el servidor para atacar otros equipos ni exponer los datos privados del usuario.
Tareas:
Restringir el servidor de dominio mediante SELinux. (https://github.com/overte-org/overte/issues/911)
Restringir los clientes de asignación. (https://github.com/overte-org/overte/issues/912)
Intentar soportar múltiples instancias con aislamiento. (https://github.com/overte-org/overte/issues/913)
Aislar varios servidores Overte en la misma máquina. (https://github.com/overte-org/overte/issues/914)
Restringir la interfaz. (https://github.com/overte-org/overte/issues/915)
Textura de lienzo (canvas)
Esto implementaría un nuevo concepto de textura de lienzo definida por software. Los scripts pueden dibujar sobre ella y los clientes recibirán actualizaciones.
Esto tiene un amplio potencial de funcionalidades útiles:
Texturas definidas por software
Etiquetas de nombre, pancartas, paneles de estado generados por scripts, etc.
Compartir pantalla sin dependencias externas
Pizarra digital
Entidad web sincronizada
Entidad web renderizada del lado del servidor. Esto facilitaría la implementación de Quest.
Tareas:
Implementación básica. Objeto de textura, operaciones sencillas como pintar píxeles y bloques. (https://github.com/overte-org/overte/issues/916)
Mejorar la API de lienzo. Soporte para tipos de letra, primitivas gráficas como rectángulos, círculos, curvas, etc. (https://github.com/overte-org/overte/issues/917)
Compartir pantalla (https://github.com/overte-org/overte/issues/918)
Superficie web sincronizada. (https://github.com/overte-org/overte/issues/919)
2024-02-24 ¡Hemos obtenido una subvención de NLnet!
La Fundación NLnet es una organización que apoya muchos proyectos sorprendentes de código abierto, ¡y estamos encantados de anunciar que también hemos sido incluidos en la lista!
Como parte del acuerdo, nos comprometemos a mantener a los usuarios y desarrolladores al día sobre los avances realizados en estos aspectos al menos cada dos meses. Para ello, realizaremos un seguimiento durante nuestras reuniones habituales de desarrollo de los sábados y utilizaremos etiquetas, proyectos y otras funciones de GitHub para que cualquier persona interesada pueda seguir fácilmente los avances.
Plan del Proyecto
Los fondos se utilizarán para pagar a desarrolladores que trabajarán en las áreas enumeradas a continuación. Existe la posibilidad de acordar más trabajos entre nosotros y NLnet.
La fecha límite acordada para la finalización es el 17 de febrero de 2025.
Parte del trabajo ya ha comenzado y se puede ver en GitHub: https://github.com/overte-org/overte
Reestructuración del audio
Mover las zonas de audio a propiedades de zona (https://github.com/overte-org/overte/issues/69)
Añadir entidades de audio (https://github.com/overte-org/overte/issues/69)
Mejoras varias
Añadir una propiedad wantsKeyboardFocus para entidades web (https://github.com/overte-org/overte/issues/6)
Añadir interpolación en las animaciones de modelos (https://github.com/overte-org/overte/issues/317)
Mejoras gráficas
Corregir la eliminación de sombras en las caras traseras (https://github.com/overte-org/overte/issues/547)
Permitir partículas opacas (https://github.com/overte-org/overte/issues/776#issuecomment-1868203856)
Finalizar la reestructuración del TAA con velocity buffer (https://github.com/overte-org/overte/pull/501)
Añadir soporte para partículas por GPU
Vulkan
Actualmente estamos usando OpenGL para la renderización 3D. Pero, desafortunadamente, ha caído en desuso en los últimos años y algunas plataformas como Mac incluso lo están desaprobando completamente. AMD le presta muy poca atención y los errores en los controladores son una molestia frecuente.
Vulkan proporcionará un renderizador mucho más moderno, de mayor rendimiento y con mayor soporte, y debería solucionar nuestros problemas de compatibilidad con Mac.
Renderizado en modo alámbrico
Renderizador directo (para hardware de gama baja)
Renderizador diferido (completo)
Optimización
Transferencia de cuadros al complemento de VR
Mejoras al sistema de construcción
Esto hará que trabajar en Overte sea más agradable y que el proceso de construcción sea más sencillo. Esto es importante para facilitar el mantenimiento y hacer la vida más fácil a futuros colaboradores.
Migración a Conan
Actualización de la documentación
Mejora del proceso de construcción
Agradecimientos
NLnet, por brindarnos esta gran oportunidad.
Julian Groß, por negociar este acuerdo.
Sam Gondelman, Karol Suprynowicz y AnotherFoxGuy por apersonarse del trabajo.
A la comunidad Overte por hacer esto posible.
2023-04-01 Nuevo sitio web
Dado que nuestro antiguo sitio web basado en 11ty estaba sin mantenimiento y nadie sabía cómo editarlo, creamos un sitio web completamente nuevo usando Sphinx, el mismo sistema que hemos utilizado durante años para nuestra documentación principal. Esto también nos permite, entre otras cosas, traducir finalmente el sitio web a diferentes idiomas utilizando Weblate.
Si deseas ayudar a traducir este sitio web u otras partes de Overte, visita: weblate.overte.org 🔗.