![]() If I add a RenderingErrorListener to VirtualUniverse, do you know what errorCode, errorMessage and/or other attributes I should get in the RenderingError that will be returned? I don't have any computer at my disposal with this issue, so it's difficult for me to guess. I want to propose to users to run legacy-igpu-圆4.zip but only if it will be helpful. Thanks for your answer At the moment, when this problem arises, Sweet Home 3D runs with Java 8 64 bit and Java 3D 1.6. I know that it's not pleasant, I'd prefer to have a clear situation, either OpenGL is supported or it isn't, not what Intel does, i.e it's supported only to migrate and it intentionally leaves a broken driver after the migration. ![]() However, sometimes you'll have to advise them to buy "better" hardware or to use an operating system not encouraging planned obsolescence. I appreciate your effort to satisfy your end users. If your installer runs with enough privileges, it could suggest the end user to download and install the shim, it's not ideal but it's better than nothing. You'll have to drop Java3D 1.5.2 in order to use JOGL 2 without any risk of conflict. Yes it's possible to detect the family of graphics card by using JOGL but if you use Java3D 1.5.2, you'll face some unfixed bugs in the context creation. ![]() Note that it makes Minecraft work anew ) This problem affects all Windows 10 compliant OpenGL softwares, not only Java3D. Some machines are allowed to migrate to Windows 10 whereas Intel plans to drop the support of their chipsets, the driver is available but just crashes with a software detected as Windows 10 compliant (which is the case of the most recent updates of Java 1.8). Still an issue for me on 7.I know this problem, we already mentioned it several times in this forum. However Puybaret, who is the Sweet Home 3D Developer, has found a workaround and has implemented the workaround in the code that was released in Sweet Home 3D 7.1. It *is* a driver problem and has been acknowledged as a bug by AMD who will issue a fix in due course (it is not yet fixed in latest Adrenaline 23.3.1). Half of their users are experimenting this problem because de render 3d doesn't work with the new graphic cards tecnologies and software. ![]() > The issue must be correct by the Sweet Home 3D developers, is not a driver problem because it happends only with this soft. The issue must be correct by the Sweet Home 3D developers, is not a driver problem because it happends only with this soft. anyway, many thanks for your help and patience, sorry for double post. Run the installer again and select 64 bit architecture.ĭamn it must be exhausting to say the same thing over and over but i was sure i ran the 64 bits. ![]() Here are some details + screen of the glitch : As soon as i try to use any object/furniture from the library, textures goes crazy. I downloaded the latest version on the website and i started working. It's been a while since I used SweetHome 3D and today i wanted get back to it. Thanks Emmanuel !īy the way, I've also tested Furniture Library Editor 1.31 : the artifacts (that were present in 1.30 version) are gone. SH3D 7.1 is working fine on my computer (Win 11 with Adrenalin 23.2.1). The 64 bit version of Sweet Home 3D 7.1 released today should fix this issue.įor the 32 bit version, see previous posts or wait for AMD Adrenalin driver update which should be hopefully published in the coming weeks.Įmmanuel Puybaret, Sweet Home 3D developer ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |