Enabling 64Bit Rendering
-
if there are issues with the UI in the demo, they will be present in the 2.0 build as well . From what I could see, the only thing wrong with the UI was that you are using a huge font for your system font, and you need the resize the options panel horizontally.. which apparently isn't something we allow for some reason. Please submit a bug report about this to vfswip@chaosroup.com to avoid it being in 3.0.
Not sure what issue you have with importing vismat materials in the 2.0 demo, we don't lock that down afaik, and it should work the same as it does in the full 2.0 version. Does the material not come in? Are there errors?
-
as far as the bundled tools go, those should work fine with the 2.0 version, if you want to just copy the 1.6 tools to a folder prior to uninstalling, and installing 2.0. I don't believe we bundle the tools with the demo, because with a resolution cap, you probably won't need to render out to a vrimg. It also keeps the installer size down a bit.
[edit] Looks like we include the tools with the demos for our other products, so we will update the demo installer in the future to correct this.
-
@dkendig said:
as far as the bundled tools go, those should work fine with the 2.0 version, if you want to just copy the 1.6 tools to a folder prior to uninstalling, and installing 2.0. I don't believe we bundle the tools with the demo, because with a resolution cap, you probably won't need to render out to a vrimg. It also keeps the installer size down a bit.
[edit] Looks like we include the tools with the demos for our other products, so we will update the demo installer in the future to correct this.
Wow... I would never of guessed it was the font that was to blame. Your right
I use 'Century Gothic' with and increased size of 10 on Win7 system because I am 46 now and by the end of the day I am squinting at the screen.The inability to import of Vismats in 2.0 Beta is well documented on the net. People seem to have the same problem... and people advise to load them first... but this is way too round about for me. Exporting directly onto Sketchup materials is the only way I want. The problem does not occur with the 2.0 (SP1)... you seem to have ironed out the bug.
BUT... I cannot export channels from my VSB Tab in 2.0(SP1). I get RGB and alpha... that's it. I spent days trying this and that.... but it works great in 1.6.... which has been a reliable friend in all the experimenting. Don't know why people beat it up so much. Beta or not... it's a great little performer.The Tools are not important now since I use ProEXR. But, again, it took days of trawling the net looking for ways to convert Vrimg to EXR... and all along it was in the Start Menu.... I really handy little tool.... you should make people aware of this with flashing lights cos it's very useful. I noticed there are other tools there too... don't know what they do yet.
Thanks
-
@maeglin1 said:
The inability to import of Vismats in 2.0 Beta is well documented on the net. People seem to have the same problem... and people advise to load them first... but this is way too round about for me.
Generally, the issues I've seen with vismats is that people are trying to import ones that are from many versions ago, and thus are written differently than the current vismat format. There's a very good set of vismats on the Chaosgroup website in the downloads section. It is advised to start with those, and then as you learn how they are put together, start making your own library of vismats.
-
@andybot said:
@maeglin1 said:
The inability to import of Vismats in 2.0 Beta is well documented on the net. People seem to have the same problem... and people advise to load them first... but this is way too round about for me.
Generally, the issues I've seen with vismats is that people are trying to import ones that are from many versions ago, and thus are written differently
People on the net say this too... but all my vismats load in 1.6 regardless of where they are from....and I have hundreds of them from Chaosgroup and other sites. None of my Vismats were able to be imported into 2.0 Beta, in fact, it sometimes crashed Sketchup.
But, like I said... this problem is not the case in 2.0 (SP1). So it does'nt matter. What concerns me is exporting channels from the VSB tab in the new 2.0 (SP1)Demo
Does it work for you?
If so, then 'case closed' and it's the demo that's at fault.
Is the demo the same as the full licensed copy? -
only RBG and Alpha channels are unlocked in the demo version, just confirmed this. Sorry for confusing the 2.0 and sr1 versions. I haven't used 2.0 since September, I'm always on a development build, and can't keep versions straight in my head.
-
@dkendig said:
only RBG and Alpha channels are unlocked in the demo version, just confirmed this. Sorry for confusing the 2.0 and sr1 versions. I haven't used 2.0 since September, I'm always on a development build, and can't keep versions straight in my head.
Thankyou Devin. I have spent a week trying to get to the bottom of this question... at least I now know that it's the Demo and not me that's at fault. Great
-
yeah, sorry, I didn't know the answer until today. Been busy working towards the next release
-
Does this trick also work on OS X? Using the DR spawner on the local machine?
@dkendig, busy updating to 3.0? -
@peerman said:
Does this trick also work on OS X? Using the DR spawner on the local machine?
You can try using a 64bit spawner that is running on windows, but there is no 64bit spawner for OSX at the moment.
@peerman said:
@dkendig, busy updating to 3.0
?
heading in that direction, yes. Had to wait until this service release was out the door before we moved on to some of the bigger changes
Advertisement