first of all, I will go back to the free version because there everything works probably
I never got the Steam version because of DRM. The GOG version is for me a failure as the terrains don't reflect any of the trailers shown features.

My System is a RYZEN 5 with latest drivers 22.11.2
16 GB RAM
3 SSD drives each 1 TB space

I ask what causes this problem?
For now all I want is understand the problem not a fix because I already asked for a refund.

20,- are way too high for this in development version, especially that the free version works and this one doesn't

AMD and SE devs are working on a fix, latest AMD drivers had OpenGL support completely rebuilt from scratch and something doesn't work. SE is not the first, nor it will be the last program having similar issues.

Why 22.5.1 exactly, what about older, where did AMD's drift towards bugs in Space Engine started, how well was it tested with Space Engine, was it pre-tested by a big sample? The changelog mentions this does not overcome all the issues. Not all AMD GPUs work well with some driver versions, to generally recommend just one may be a bit of a mistake not taking into the account the entire range, like recommending one shoe size to all of humanity. Interesting. Harbingerdawn, sure, AMD did mess up big time. but, if the free 0.9.8.0 version works good, then, well, why instead of outting Windows 7 people, for example, you don't advertise the free version nor put it as a "demo experience" for the people to decide if they want to buy this product? Not everyone is eager to dig the depths of the Internet to know the free version exists. Some put better compatible as "classic" into patches, i.g. GOG's own "The Witcher 3" does, "GOTY" works on Windows 7, "Complete" does not. Radical changes like on rendering or features may cause the same. "Metro Exodus" offers both the classic version and RTX; "Little Nightmares II" does the same way, two versions; "Emperor of the Fading Suns" too; "Bioshock;" "Doom;" Many others, that's how it is on GOG usually, offering options when necessary.

If the older version has lower system requirements (does it not?), this is all another reason to do offer it explicitly on GOG as a visible option. Let's remember not everyone is born with thousands of dollars in the pocket for a beasty PC.

A wise decision, as it turns out. Why? Nobody guarantees the developer will not decide to demand the latest and screw you over when your OS/GPU would come to the end of support. This is not like with a typical GOG product, it's a risky investment at best, and a shipwreck at worst. Then remove the newly added odd popup from the product now! Quote from it (the oddity is that it's not an error but a warning): Is the popup made for pirates? How nice, so much care for piracy, thank you! Legal users can always see the reqs from a store page. As I said, this is not the norm in the industry to do what you've done, only 4 GOG products do this sort of things with a popup in general.

Instead of treating customers like idiots, you could inform which OpenGL features exactly are not present when it's really necessary. A very simple comparison to do since the game's requirements are known, a driver is capable to report the information: That's the smart approach to the problem that is objective and is actually helpful. The current appears to be dumb checking the OS version, the code is made in at best minutes. If all what it does is just not showing some effects, I don't see a "critical" problem in any way. Besides, you product is the only one (!) on the whole store being so incedibly weird in this regard, no other does this exact popup. I repeat: No product on the whole store does this kind of thing that you have pulled off in the latest product version for some ridiculous reasons without any real testing. How can you say if that's "critical" if you never tested? It doesn't cause anything critical.

If you baselessly claim my current driver to have no "criticial" updates, well, I have a sprinkle of reality: It is not "critical" to have it updated, the engine displayed stuff correctly and did not bug out badly on a version of the AMD driver from 2 years ago; Critical comes from the updated drivers for my GPU, is where all the Hell is roaring right now and I will not switch nor plan to switch because 1 single developer out of all the GOG products wants for a user to be on the latest drivers, potentially screwing up anyone who brought this product and is in a similar situation somehow where the latest drivers are suicidal to use. If you want to code so badly, why couldn't you code the support back or fallback to something when an OpenGL feature is not found? This is how everybody does. Yes it is convoluted, yes, it is not too easy, I do wish to not offer compatibility too but we have the responsibility when we created something, that's what being a developer is all about.

Like, do not take me very wrong, I perfectly understand why you are trying to "defend" the project by saying like it's not the project's fault in anything, why you despise all but specific setups like own system or why you love to not offer compatibility. What I go from is a customer's standpoint of view, not yours, I am not here to please you in any way. All what I initially wanted is to warn other users of the system, made an error, then you misread my error and have passed some crazy popups seemingly based on that. "Outting Windows 7" is: Treating Windows 7 people like ash on a rooftop, not testing on the system, putting spam popups, not caring about the customers, being against supporting the system in the product that from 2011 (!) while its modern Russian site still lists Windows 7 (did you forgot to update the site?). This is how you outted it, literally, it's put out into the darkness with zero respect or honour. Space Engine started with Windows XP as the minimum, Windows 7 as recommended. then it ditched Windows XP, then murdered Windows 7... What's next, slauthering Windows 10 for Windows 11, 12, etc? Can the customers be sure you'll not do that again? Very likely to be repeated for the same reason of "we have limited resources, let's support only one thing, the customers do not matter, compatibility does not matter, all what matters is to break things." The only way you could confirm you wouldn't is by returning what you've taken away and sticking with it like a responsible reliable gaming developer. The majority of other developers on the planet do that thing quite well, despite the hurdles. 0.9.8.0 is not as "far" from the current as you love to think; Your eyes got clouded, do not perceive the project like an outsider. I took a swift look on your latest version, doesn't make much difference against this one, the core thing is the same, void-eaten. For example, "Hello Neighbour" in Alpha is basically not cooler than it is in the final, the core is the same (it offers Alpha as a demo). If the bug in 0.9.8.0 bugs you so badly, why wasn't it taken care of? Let me guess, not interested to spend coding time on adjusting the free product to the Nvidia drivers beyond 436.02. Tells a ton about the approach to own product's history or to accessibility for people to try it out in its past form; Making me sure you'll not care about Windows 10 customers when their time comes too. This shatters around a simple fact: The world doesn't circle around the US, the majority of humanity is in poorer developing countries to whom this is no peanuts and a lot of people use shockingly old hardware for one reason or another. Trying to shrink the amount of customers that can buy a game is quite a nightmare business plan.

All what this year's interaction told me about you as a developer is:
A lazy developer who despises all the systems but their own-likes, who will happily break compatibility moving on, who is riddled with excuses on everything, unable to perceive the project without a clouded in-dev vision, who will put the kind of popups in the product that no other GOG product does (no other specifically refers drivers, the 4 only are OS blocking), who is out of touch with their customers and is thinking everyone is living in a developed wealthy country, is imagining to afford a PC or two is a no-brainer-easy-peasy, who will not do anything or help a customer with an integrated GPU, a new Intel GPU or a GPU that differs from their own too much (see Steam, folks, see it), even though its the developer who wrote the graphics rendering of the engine. In short, one word: Negligence. Who would dare to invest in you or your project after all of that?

I am afraid this is only the peak of an iceberg. Likely uglier beneath ("made in Russia"), more uglier deeper in.

lol apparently this program will cause the decline of western civilization too. OK.

I don't see what's "funny" in the unprofessional behavior of the developer of the made-in-Russia game. There is 0.000% funny in. Compatibility must be taken care of, plain and simple, like all the other developers do, with no shortcuts and no laziness in place.

Eliciting some reaction by ignoring developer answers and doubling down with less than polite judgements because you don't like them, on several threads too instead of choosing only one, it is a bit funny.

"Funny?" Are you a troll, Mosfet32? Please find better things to do than being a nuisance.

The developer blatantly ignores the fact of own support track record being horrible (always abandoning every single Windows except the latest in the current year), tried to deliberately misinform, to mislead customers on not being in Russia, so on, breaking any bit of trust, then purposely ignores addressing the facts of history that do spill the beans. What could be done to partly repair this? Assure all the customers that their system will not be suddenly abandoned like the previous ones and add Windows 7 as the sign of backwards compatibility support, manage to relocate Vladimir Romanyuk, the founder, out of Russia as soon as possible, afterwards repeat what CD Projekt Red did in that regard (make a statement, donate some income). The incorrect way is to keep silence, not addressing the huge mistakes that were made.

It appears to me harbingerdawn chose the 2nd way, the way of ignorance, unfortunately.

Unfortunately this thread has been hijacked as the OP called for a very different topic.