Page 1 of 2

failed to write texture....... two year old bug

PostPosted: Thu Jul 14, 2016 9:03 am
by Jorgensen
so i happens again - i modeled a scene at home - and it rendered well.

now i try to open the same scene here at work and i get the "failed to write texture" error.

i'm quite sure that it has something to do with our user profiles being on our server, and it seems that octane is using a wrong path

THIS PATH DOES NOT WORK (the one octane uses)
////tmsrv1/users$/brj/octane/sketchup/temp/su_textures

THIS PATH WORKS
//tmsrv1/users$/brj/octane/sketchup/temp/su_textures

there seems to be this "//" to much in the path.

please fix this, as it prevents me for working.

just to clarify - the error has not alway exists, older version of the skechup plugin did work.

i hope there is a solution.

thanks
jorgensen

Re: failed to write texture....... two year old bug

PostPosted: Mon Jul 18, 2016 3:03 am
by CaptainCrowbar
Jorgensen,

The new release I posted today includes an attempt to fix this issue. Since I haven't been able to reproduce the problem, I can't be sure my attempted fix will work; please try it out and get back to use.

Also, please check your HOME and HOMEPATH environment variables. Open a Windows CMD shell and enter
Code: Select all
echo %HOME%
and
Code: Select all
echo %HOMEPATH%
, and let me know what the results are.

Re: failed to write texture....... two year old bug

PostPosted: Mon Jul 18, 2016 5:06 am
by Jorgensen
Hi captaincrowbar

Thank you for looking into this problem.

I will test the latest release as soon I'm back from holiday.

Jorgensen

Re: failed to write texture....... two year old bug

PostPosted: Mon Aug 08, 2016 8:00 am
by Jorgensen
hi CaptainCrowbar

i have now tried the new 3.03.2.0 version - but i still get the same error :-/

i then used cmd and entered the text you wrote.
when i enter %HOME% - it returns %HOME% ?
when i enter %HOMEPATH% - it returns '\' - which i find a strange, as our userprofiles are on our network drive "u". (tmsrv1)

i also tried echo %userprofile% - this returns the local path c:\users\brj\

jorgensen

Re: failed to write texture....... two year old bug

PostPosted: Mon Aug 08, 2016 9:55 pm
by azen
Hi,

It is possible that this issue originates in the Standalone, rather than the plugin. I will need to talk with core developers to confirm. There have been known issues of this nature in the past with the standalone.

Thank you for reporting this issue, we will get to the bottom of this as soon as we can.

Re: failed to write texture....... two year old bug

PostPosted: Tue Aug 09, 2016 6:53 pm
by Jorgensen
hi azen

this problem prevents me from using octane for sketchup at work - so i'm very glad that you look into this problem.

please let me know if there is anything needed information i should provide.

jorgensen

Re: failed to write texture....... two year old bug

PostPosted: Tue Aug 09, 2016 11:04 pm
by CaptainCrowbar
I've just posted a new build (3.03.2.2) with some further changes to the file path handling code. Please give this a try and let me know if it fixes your problem.

Re: failed to write texture....... two year old bug

PostPosted: Wed Aug 10, 2016 7:15 am
by Jorgensen
hi captaincrowbar

sadly the same error.

but i just tried to copy the octane plugin

from
C:\Users\brj\AppData\Roaming\SketchUp\SketchUp 2016\SketchUp\Plugins

to
C:\Users\brj\AppData\Roaming\SketchUp\SketchUp 2015\SketchUp\Plugins

and now i don't get the error when using skectup 2015??

jorgensen

Re: failed to write texture....... two year old bug

PostPosted: Wed Aug 10, 2016 9:33 am
by Jorgensen
hi captaincrowbar

sadly the same error.

but i just tried to copy the octane plugin

from
C:\Users\brj\AppData\Roaming\SketchUp\SketchUp 2016\SketchUp\Plugins

to
C:\Users\brj\AppData\Roaming\SketchUp\SketchUp 2015\SketchUp\Plugins

and now i don't get the error when using skectup 2015??

jorgensen

Re: failed to write texture....... two year old bug

PostPosted: Wed Aug 10, 2016 1:49 pm
by Jorgensen
I just insured that 2016 was running as administrator - it wasn't, changed to it runs as administrator - but that made no difference :-/