New beta

[Support]

@Okwa

Can you open a command prompt and enter...

tracert raylectron.com

and wait till it's done, this will tell us exactly where the problem is.

[Okwa]

Okay, I'll hold back a bit from now on.

NOOOOOOOOO! That's not what I meant

[Okwa]

@Okwa

Can you open a command prompt and enter...

tracert raylectron.com

and wait till it's done, this will tell us exactly where the problem is.

The same depressing result as when we measured it a few months ago. But this time I managed to take a screenshot. I'll send it to you as a PM. Short version: at the fourth IP the times are 10/9/17 ms, at the following IPs the display shows ‘Request timeout’. Up to the eleventh IP. At this IP the times are 107/107/105 ms. The display closes at the thirteenth IP.

[Support]

The same depressing result as when we measured it a few months ago. But this time I managed to take a screenshot. I'll send it to you as a PM. Short version: at the fourth IP the times are 10/9/17 ms, at the following IPs the display shows ‘Request timeout’. Up to the eleventh IP. At this IP the times are 107/107/105 ms. The display closes at the thirteenth IP.

Got it, thanks, I'm going to send it to my provider (with your IP hidden) because this makes no sense. It's not just a once in a while thing now

[Okwa]

@Support Many Thanks, Michael.

[Support]

@Okwa

I have uploaded a new beta (same link). I refined the stars and nebula without the precomputed map. it's more detailed. I fixed other things too. But the major update is the GPU version, I've added the new stars and nebula to it as it didn't have the nebula before and was still using the old stars.

One thing I'd like to ask you, if you're able to test both and see if they work good for you, but the main thing is, the UI can use one of the 13 provided languages and I'd like to know if it looks good for your language? or is it all crazy and making no sense (I hope not lol)?

[Okwa]

@Okwa

I have uploaded a new beta (same link). I refined the stars and nebula without the precomputed map. it's more detailed. I fixed other things too. But the major update is the GPU version, I've added the new stars and nebula to it as it didn't have the nebula before and was still using the old stars.

One thing I'd like to ask you, if you're able to test both and see if they work good for you, but the main thing is, the UI can use one of the 13 provided languages and I'd like to know if it looks good for your language? or is it all crazy and making no sense (I hope not lol)?

I have never used the German version. Ok, let's get straight to the biggest problem, which I hope I can explain clearly: When I change the language from English to German (or any other language), the resolution is automatically set to 940x540. If I then want to change to 1920x1080 via ‘More’, Raylectron does not respond. However, if I click on options such as 75%, 100% etc., the corresponding resolution is adjusted. As soon as I have set it to 100%, for example, I can then switch to 1920x1080 without any problems and Raylectron will then carry out this change.

Regarding the German language, I will write you the English word and the, in my opinion, better translation:
Treads = Prozessoren
Illumination = Beleuchtung
Assets = I would leave it, as far as I know, "assets" are also used in German, as all German translations are too specific.
Enviroment = Umgebung
Reflecktion = Reflektion
God's Ray = The same applies here as with ‘assets’.

By the way, there are now fewer stars if you use stars and nebulae with the ‘’use precomputed map‘’ checkbox activated than in the previous beta version.

[Support]

I have never used the German version. Ok, let's get straight to the biggest problem, which I hope I can explain clearly: When I change the language from English to German (or any other language), the resolution is automatically set to 940x540. If I then want to change to 1920x1080 via ‘More’, Raylectron does not respond. However, if I click on options such as 75%, 100% etc., the corresponding resolution is adjusted. As soon as I have set it to 100%, for example, I can then switch to 1920x1080 without any problems and Raylectron will then carry out this change.

Thanks for testing it Chris. I've tried what you explained, and it works fine for me, even if I set my OS to German. The language setting only affect text, so I'm not sure why this happens!

Regarding the German language, I will write you the English word and the, in my opinion, better translation:
Treads = Prozessoren
Illumination = Beleuchtung
Assets = I would leave it, as far as I know, "assets" are also used in German, as all German translations are too specific.
Enviroment = Umgebung
Reflecktion = Reflektion
God's Ray = The same applies here as with ‘assets’.

ok, so it's not that bad then? Can I leave it like that because I use Google translate automatically on all the 13 language files and it'll be more work to keep updating that one file manually, and that's if I remember to do that!

By the way, there are now fewer stars if you use stars and nebulae with the ‘’use precomputed map‘’ checkbox activated than in the previous beta version.

ah, my mistake, it uses either or, not both! I fixed it.

[Okwa]

@Support
No problem, Michael.

I will continue to monitor the "problem" with the resolution after the language change. So far I have started Raylectron every time via the shortcut and have not tested whether the error also occurs when I open Raylectron via SketchUp, when I have loaded a model to Raylectron. It could also be due to an installation error - I will check both tomorrow.

I didn't notice anything else linguistically. Although the Google Translator is not as good as Google likes to pretend.

Ok, I'll try out the new beta tomorrow too.

[Support]

@Support
No problem, Michael.

I will continue to monitor the "problem" with the resolution after the language change. So far I have started Raylectron every time via the shortcut and have not tested whether the error also occurs when I open Raylectron via SketchUp, when I have loaded a model to Raylectron. It could also be due to an installation error - I will check both tomorrow.

I didn't notice anything else linguistically. Although the Google Translator is not as good as Google likes to pretend.

Ok, I'll try out the new beta tomorrow too.

Google is the only one that I can use to automate the translation. Doing 13 files by hand would take days!!!

I'll upload the new beta shortly which fix the star/nebula.

Thank Chris

[Okwa]

@Support Well, there's a reason why Google is the market leader in its field. I mean, strangely enough, the competition is still failing against Maps.

O man, 13 files? No way. Hooray and thanks Google!

[Mike]

@Support

I've downloaded the latest and tested both the CPU and GPU stars/nebula. They work perfect. Within 30 seconds, I was able to get the look I was looking for. Thank you for such great render

[Support]

@Support

I've downloaded the latest and tested both the CPU and GPU stars/nebula. They work perfect. Within 30 seconds, I was able to get the look I was looking for. Thank you for such great render

You are welcome Mike and thanks for testing it

It looks like you're zooming in the sky with a telescope, very nice.

[Mike]

That was the idea

[Okwa]

@Mike Brilliant idea! Inspiring.

@Support Oh, I forgot to let you know yesterday. Everything is going great for me too.

[Support]

@Support Oh, I forgot to let you know yesterday. Everything is going great for me too.

Great, thank you for letting me know. But now, a new bug reported by someone, when saving while it's rendering saves with grains so I have to fix this before the final release.

[TaylorBaird]

@Okwa

My God, I miss this thread, how did that happen?? Beautiful renders and models,

[Okwa]

@TaylorBaird

Many Thanks.

Once again, this was actually only about the technical aspects. So it's easy to understand why you missed it.