Daz 3D is part of 
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.Daz 3D is part of
Connect
DAZ Productions, Inc.
224 S 200 W, Suite #250
Salt Lake City, UT 84101
Licensing Agreement | Terms of Service | Privacy Policy | EULA
© 2024 Daz Productions Inc. All Rights Reserved.
Comments
I apologize if I implied that I was volunteering myself to work on this alone. For me, this can only be a 100% team-effort. I'm happy to contribute when I have time and post my insights. I'm hoping very much that other people here are willing to do the same. I've tried to read through the Reailty source code a couple times since Paolo first open-sourced it, but have been limited by not being able to build the dependecy libraries. I think I need to step through with a source-code level debugger for my brain to fully understand what's going on. Thanks again for posting the full source-code. If I make progress on the build environment, I'll post it to Github. But it does seem like we are missing pre-compiled dependency libraries for Windows.
@pciccone: Thanks for posting the details on Reality and your offer to help. I will definitely contact you if I get stuck.
@nonesuchoo: Also, I would go ahead and install the Daz Store version of Reality. It's unlikely for it to cause issues with another version with the DRM-removed.
If you are able to launch and use Reality, then you probably do not have a problem related to OpenCL.DLL. The OpenCL.DLL error is related to version of the OpenCL 3.0 DLL that is somehow incompatible with Windows Kernel.dll's LoadLibrary( ) function. Attempting to load the library with this function results in an exception error within the kernel.dll and immediate "crash to desktop". But since Reality calls this function before any GUI pops up, it just looks like nothing happens when you try to run the EXE or launch Reailty from the Daz Studio plugin.
Anyway, if you or anyone else thinks they might have this problem, then you can diagnose and work-around it by doing the following steps:
FYI, the reason the fake "OpenCL.DLL" works is because Reality was designed to check for OpenCL, and if it doesn't exist or has an error, to continue functioning without it.
Feel free to post any feedback you might have on the yaluxplug thread: https://www.daz3d.com/forums/discussion/499531/open-source-release-daz-render-plugin-framework-with-yet-another-lux-plugin#latest ; But no worries if you that's not your thing: Somtimes I just want to review-bomb something without having to fill out long surveys as to why I it a 0/10. hehe
@OmniFlux: Thanks for volunteering to take over the domain and keep the server running!
The reason for this was because i had reinstalled my AMD card under my new Nvidia card with No drivers for the AMD installed.
For some reason i couldn't explain other then the default drivers for AMD that came with Windows 10 seems to allow Reality to open, which was the fix i ran with.
But of course having the card in the system (i think it had updated the video drivers at some point) I believe is causing System instability and want to take it out
Thanks for the instructions!
I had assume that's what the procedure was but i didn't want to pull out my card and attempt to do this fix and find out i did something wrong
(I had to run windows restore point to get the house of cards settings i have now to get reality back lol)
and if you don't mind, I will start documenting issues i am having with YaLux as a whole. I will have to compare it to my experience with Reality/Luxrender
if that isn't going to be an issue
I hope to migrate if Reality issue isn't resolved, seeing developing plug in for LuxCoreRender has me excited and i'd love to help with it in any way i can.
But i guess i just have a specific expectations of it that isn't being fulfilled is more of a me problem and don't want to make it yours, But if helps in the long run
I'd love be around to give feedback
OK, I changed my mind & decided to see if I can help as you & OmniFlux also seem ready to work on this. Also, TheMysteryIsThePoint will likely join in.
I will be working a few hours this week on on getting the code to compile on my computer. Not sure if I will get results but that's OK. Hopefully I won't blow the whole weekend on it as I do have a lot of other non-computer work to do too.
Just to let everyone know where I am on this and where I'm headed
I am hopefully only a few days out from this point.
Once that is done, here are the things I am aware of that need to be done
Not sure I'll have time for the QT and Python items in the near term.
Things I currently cannot do
If i may interject
Ther is one minor issue i have pointed out in fourms past in reality and it was never adressed
I do not know if this is something that can be looked at while this is going on, and its alil selfish for me to ask
But one nagging issue is how Reality seems to export geometry, seems to miss some vertices? normals? (i'm very amature when it comes to this 3d stuff on this level)
which results in errors in some large surfaces
i don't want to start requesting fixes if isn't going to be any kind of priorty after the fix of the Authentication to continue support for Reality
besides that, i really want to thank you guys for really stepping up for Reality/Luxrender/LuxCoreRender
you guys are awesome <3
LOL, super! Thanks, I could really use a reliable way to render on AMD (and maybe Intel GPUs). I guess I can now spend the weekend doing other things instead as there is no sense proceeding if you're going to finish 90% of it before I get back up to speed.
I'll have to install it but I can test for Poser 11.2 Windows which is the 1st version that Renderosity patched after buying it from Smith Micro. I won't have a Apple machine until Aug or Sep 2022 though sorry.
My test platform: AMD Ryzen 7 5700G (Radeon Vega 8 integrated), 32GB RAM, 2TB SSD, Windows 11 patch to current date. DAZ Studio 4.16.1.6 Publc Beta, DAZ Studio 4.16.0.3 Release, Poser 11.2
If it's possible when OmniFlux uploads the version of modern updated build environment version of Reality with the DRM stripped you should mention this bug again and upload 1 or more example scenes with this bug to test with. There is a decent chance I have all the products you've used, if they were purchased from DAZ 3D or Renderosity. If there is a bunch of freebies in the scene you'd need to upload the freebies too so the scene could be opened.
Thank you OmniFlux for taking on the server for Reality.
I can build for OSX. Really great stuff happening! Thanks!
Its less about products and just a general thing it seems to do
Sometimes you just notice it in some scenes and objects
But it will always export that way
even a simple primtive cube shows this behavior
i'll redocument my findings o 3 ob glad to hear you will be able to address bugs and issues once the DRM is stripped out
OK, yes. Just make a document illustrating the problem & how to reproduce it and upload it to this thread when it's ready.
https://docs.google.com/document/d/1xe7XM9E3XvYiBvmJKayjE6jvQGN9NSV9ekmD0s59b5o/edit?usp=sharing
I hope you don't mind, but I put it down in a Google Doc
if this format isn't sufficent, i can recreate it here as its own post
That's great as we can choose the format to save it as and I've bookmarked it in case you update it later. I'll refer to it when I test in Poser & DAZ Studio.
Hi, I just looked through your Google Doc. Thanks for being so thorough with your observations and data gathering! All the information and screenshots you posted there were extremely helpful and trying to figure out what is going on. I'll PM you my response so that we can keep this thread on the topic of Reality End (Extension) of Life.
Let me just take this opportunity to thank Paolo and his marvelous plug-in for teaching me so much about lighting. It has helped my photography as well as my rendering! I stopped using Reality some time back, but the lessons learned have transferred extremely well. Grazie!
Redacted
@cridgit Caustics, we want caustics .. that's where iray is not good and cycles totally sucks
If they were honest they would not be "turning to piracy" in the first place.
Tell you what: why don't you spend hunderds, if not thousands, of hours and thousands of dollars developing a piece of software and offer it for sale without any mechanism to enforce your IP rights or hinder unauthorized duplication or distribution, and see how long many copies you sell before it starts showing up on pirate sites?
Iray's actually pretty decent with caustics provided you turn on the caustics sampler. Lux is still the king though. and the glass just looks more solid
Caustics in cycles is definitely just sad.
Iray and Lux are oddly similar. They both are unbiased to a fault, even where cheats make life easier. Take how both use pure volumetrics for SSS, and won't make shadowless materials
Thank you j cade for the nice comparison, in your pictures it is clearly visible the difference in quality between iray and lux.
again off topic
but has anyone else's Reality stop selecting surfaces when using the surface tool on Daz?
This has been one of the largest features I need in for Reality consitering you have to know what you are selecting because of you having to edit every surface on a given scene because not everything is plug and play
this started happening after i pulled my AMD card out and uninstalled its video Drivers
Reality still opens for some reason, but this function broke
(edit: it seems to still work on some stuff, but not others, i'm not sure why now)
That's very nice of you to say. It's been my pleasure. When I started Reality it was because of my background in photography and cinematography. I wanted a renderer that behaved like real lights, which I use every day. Today I'm back to photography full time also because it was not possible to keep up by myself with all the improvements in the field. But I'm really happy to hear stories like yours, CMaks. Because of those I fell that Reality has accomplished its mission: to show to artists in general how to use a more natural way of lighting and rendering 3D scenes
Cheers
That's very nice of you to say. It's been my pleasure. When I started Reality it was because of my background in photography and cinematography. I wanted a renderer that behaved like real lights, which I use every day. Today I'm back to photography full time also because it was not possible to keep up by myself with all the improvements in the field. But I'm really happy to hear stories like yours, CMaks. Because of those I fell that Reality has accomplished its mission: to show to artists in general how to use a more natural way of lighting and rendering 3D scenes
Cheers
Hey cridgit, I remember you very well and I remember that great Buddha render. It did put a smile on my face! :)
Thank you so much for your kind words, they really mean a lot to me. Seeing the Studio/Poser community explore the features of LuxRender via Reality was a thrill and event seeing PBR being adopted by Studio and Poser with their own renderers gave me a sense of purpose that was quite a thrill. We did it. You all and my little contribution. Without your enthusiastic adoption, this could not have happened. When Reality came out in 2010 it was a gamble, but the Studio community said a resounding "YES!" and the rest is history. Among other things, it was because of the response from the Studio community that Poser acquired a new plugin API. Funny but true.
Initially, I had thought to create Reality for Poser but, when I looked at their API, I concluded that it was lacking the infrastructure that was needed for something like Reality to be integrated. So I looked at Studio, which I knew had a capable C++ API, and shifted development to that platform.
The response of the Studio community had been so great that when I re-contacted the Poser developers their answer was literally: "tell us what you need and we will make it happen." :)
From that, I co-designed the new plugin Poser API which allowed Reality to be integrated and, at the same time, helped other renderers like Octane.
Don't you love how things evolve? :)
BTW, does anybody know how to have the forums notify via email? I don't get any notification when people post here.
Cheers
AWESOME! Congratulations, that is a major milestone. Does it run?
BTW, if I remember well, the OpenCL library is loaded dynamically at run time. Given that OCL is all but defunct, I would simply strip that part of the code so that you will remove any incompatibility caused by the new drivers. It will probably make life much easier for everybody. Even Apple, who created OCL, has disowned it.
Cheers.
Yep, and that is for a $40 piece of software. I mean, who pirates stuff that cheap. I understand when they crack a software that costs thousands of $, but $30-$40??? Note of relevance, I actually ended up in the hospital because of the development of Reality.
I started writing it in 2009, in the middle of the economic depression. I had to sell my previous e-commerce business and had not been receiving a paycheck for 18 months. I mention this just to explain the climate of the time.
When I search for a way to make a living I turned to what I knew best: develop software. I also loved 3D and photography. And then I stumbled upon LuxRender. I could not believe that there was a physically-based renderer. It seemed like something out of science fiction. But it was true and, to my surprise, PBR was still quite unknown. So a plan emerged to write a program to interface Luxrender and bring PBR to the mainstream. That is you guys and gals :)
The issue was that I had never written 3D software. The math scared me and it was a big strain to learn it while I was writing the code. With the background of using my own saving to sponsor the project and the recession looming over, I became so stressed that I literally pulled my spine out of shape by sitting for 14 hours a day at the computer. I was just so stressed that my back muscles tensed up in all the wrong ways. On Halloween 2009 I had to go to the emergency room because I could not walk anymore, such was the pain in my back. It turned out that I had bent my spine so badly that I inflamed a disc, which ended up pushing on some rather sensitive nerves.
Mind over body in all the wrong ways :)
It took me months to recover and heal, all while I finished writing the first version of Reality. To make it happen I switched to an exercise ball in lieu of a chair. I still use that today.
With that background, and needing very much to make a living, it was simply unthinkable for me to distribute a software over the Internet without protection. When I saw that it was pirated even at an extremely low price, I simply felt vindicated. Since then I bought many programs for various uses. They all have some form of protection, and I never faulted the developer for doing that because I literally know how much pain there is in writing complex code and know that there are people out there that have no respect for that effort.
It saddens me that the paying customers might be inconvenienced but I experienced that as a consumer for years and I think that it's a low price to pay for the amazing products that we get to use every day.
Cheers
Wow, I am so envious of you. I could never get the Daz devs to even acknowledge that I exist in any way, shape, or fashion.
It was a matter of leverage. Poser had no iRay and no Lux. The old renderer was rather dated. Reality made a good splash, especially with version 2.x. At that point Studio had a lot of offering. It also helps that Smith Micro was in the same town I lived at that time, Santa Cruz, CA. When you can meet face to face it's so much better. Steve Cooper, manager of the project at that time, Larry Weinberg, the original creator of Poser, and I sat down at a coffee shop and discussed what would it take to integrate Reality and Lux with Poser. I gave them my two cents and they agreed. What can I say?
The stars were aligned :)
I have created a GitHub repository with a cleaned up copy of the files from @pciccone, updated CMake configuration and instructions for compiling on Windows.
I've thrown all the time at this I can for awhile, I hope to get back to it again next month (but it could be longer).
Awesome! Thanks very much for your hardwork! I have forked here. Your CMakeLists.txt is working well. Thanks for the links to precompiled Boost!!!!! That was my block before. I am using CMake GUI so I don't think the json preset files do anything for me. Instead, I click the "+ Add Entry" button and add the following definitions:
Here is my progress for building on Windows:
Creating the CMake Entries listed above will get you through the first part of the CMake. I haven't figured out how to get CMake to detect my precompiled Qt libraries. QTDIR doesn't seem to do anything. I enter the path for each one manually, it takes me about 10-15 minutes each time. I then disabled OpenCL requirement in CMakeLists.txt by commenting out line 44.
Then I am now stuck at CMake configuration of ZeroMQ:
I don't know why it can't find the winsock libraries. Maybe they are not part of Windows 10 SDK?
My progress for building on Mac:
@Omniflux You made comments about needing Mac-specific code for the json presets and CMakeLists.txt and FindDAZStudioSDK.cmake, but I don't think anything needs to be done. Users can use "cmake -G Xcode" to build Xcode project files. I don't know the equivalent json setting for that. The CMake gui will automatically preselect Xcode when using Mac, and users can change this selection when they first push the Configure button when setting up this project within the CMake gui. There are no hardcoded windows paths in the other two files.
For Mac build process, I tried using the precompiled dependency libraries supplied by @nonesuch00 (thanks again!) I copied the boost folder out of the original "reality-plugin-code/libs" folder, and used it with Omniflux's new source tree. I adjusted the manually created CMake Entries listed above with appropriate file paths to my mac folders. The relative path to the precompiled boost mac binaries is: "boost/stage/lib/mac/". Unfortunately, it's incomplete.... there are only 5 static built libraries in there: libboost_atomic.a, libboost_program_options.a, libboost_python.a, libboost_system.a and libboost_thread.a. CMake wants to find these additional libraries: chrono, date_time, regex. So that is where I am currently stuck on the Mac build.
I will try to spend more time this weekend working on building both Mac and Windows. If anyone has any suggestions, comments, corrections for me, please let me know! Thanks again to @pciccone, @Omniflux, @nonesuch00 and everyone else commenting, contributing and leaving feedback on this thread!