Just logged in fine on my 12 pro max, you sure?
Nvm, also it says Next Billing Due -19342 days and it also says “Renewal Almost Due”, is that an error or something?
@anon61048460 can check on the backend, I don’t think it should do that. Are you able to use your API key? (Update GitHub code)
Yeah, my API key works, it for some reason shows that for me.
Interesting. I think you’re activated forever so there’s a problem with the language itself that flips it to a negative number for some reason. Just to put your mind at rest, it shows that your activated forever on the backend.
I may be wrong, so don’t quote me on this, but when I checked @anon61048460 had activated beta testers for 3 months? The API key format is changed and whitelisting is required from now on though so all beta testers have to visit the payment center again. It’s pay as you go anyways so 3 months isn’t the end of the world, but again I don’t know what he did
StreamX v3.0.0 Release Notes
Hello developers,
I am here to provide you with the news that StreamX version 3 has been released to the public! You can now find the updated client scripts at GitHub - Roblox-StreamX/Client: StreamX Roblox Client. You can also find the new StreamX status page at StreamX.
Without further a-do, lets get into the changes we’ve made:
Backend Changes
+ Added MongoDB for Delivery Database
+ Added MongoDB for Payment Database
+ Added 8 Delivery Servers to the Network
+ Added 2 Payment Servers to the Network
+ Added 2 Part Database Servers to the Network
+ Added MongoDB replication between Payment Nodes
+ Added 2 Traefik load balancers to Delivery Servers (WV and MS datacenters)
+ Added 1 datacenter to the Network (FL)
+ Added security fixes for malicious requests
+ Added higher server reliability for less downtime of servers
+ Added game whitelisting
+ Rewrote Payment and Delivery Backends
- Removed Cloudflare load balancing (was money out the window)
- Removed old Delivery Part Database (yikes was it slow)
- Removed undeleted part information from old servers (we melted the disks)
Client changes:
+ Added BitBuffer Script
+ Added Serializer Script
+ Added Live Server Switching (in case of downtime)
+ Added Reliability and Performance Fixes
+ Added new upload functionality (doesn't need to upload parts every time a new server is made)
+ Added StreamX Folder (to replace assets folder)
- Removed old client script
These changes are now live! Although legacy script support will remain throughout the new year. However we recommend you switch to the new client script before then.
Special thanks to:
@pyxfluff - Payment Center Developer
@anon61048460 - Fullstack Developer
@Crcoli737 - Backend Server Developer
Thanks,
Crcoli737
StreamX Co-Founder & Developer
P.S. Moved back to Community Resources since the streaming scripts are now open-source.
Coming back to this, it’s improved quite a bit. However, I feel like this is still very limited in that the customer is able to add their own parameters to the loader. For example models, they are poorly loaded as shown in the image below.
I think a part that is being loaded should be checked if it’s a model or not and then loaded fully because it creates quite an unprofessional look to the game. However, to avoid this I recommend loading everything according to what the user sees instead of the user’s position, using WorldToScreenPoint.
I’ll gladly look into that, thanks for the suggestion.
What other “parameters” are you exactly looking for in terms of configuration?
Options to load textures, and materials because some clients might not be able to handle the game and it would be quite tedious to remove textures and materials after it’s loaded. A force load system would also be nice just in case the loading fails.
I think that would be a good idea although there currently are safeguards in place to prevent StreamX from killing the game if a usable delivery server isn’t found.
@pyxfluff I can’t login at the Payment Hub. It just keeps on playing the little loading animation
Interesting. There doesn’t seems to be a problem with the payment server right now, but I’ll look into it.
Again, this is a frontend bug for people who are activated forever.
There is nothing to worry about
I am not activated forever though…
Does your API key still work?
Were you a beta tester or did you purchase StreamX?
This is because I reset passwords a bit ago. Make a new one.
Are you guys still trying to work on the texture/mesh update?