I see browsing Nostromo, maybe he can give an answer?pixelrush wrote:ok thanks I see the happy people seem to be those with 64 bit so maybe 32 bit has a bug (or 2 or 3.. )?
so I'll wait on radiance to reappear and maybe fix something for us
Octane Live Platform Testing Release (pre-23) [obsolete]
Forum rules
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
NOTE: The software in this forum is not %100 reliable, they are development builds and are meant for testing by experienced octane users. If you are a new octane user, we recommend to use the current stable release from the 'Commercial Product News & Releases' forum.
Intel 2x dualcore | 4 Gb Ram | XP 32| GTX470 | Driver 258.96
Look at it with a packet sniffer. I had some spare time because I could not use the 2.3 release today (license could not be released from machine because Octane would not start) looks like it calls home twice, as far as I can tell firstly to a server in NZ then to the states. Maybe the NZ server forwards it on to the actual "live" redundant servers as they are added.
Ip addys that popped up are 206.217.134.154:443 and 203.97.78.43:53.
Of course, proably best to get the actual IP address and ports from Refractive, in case they are not finalised. EG, don't go adding any addresses to a firewall that I have listed!!!
Ip addys that popped up are 206.217.134.154:443 and 203.97.78.43:53.
Of course, proably best to get the actual IP address and ports from Refractive, in case they are not finalised. EG, don't go adding any addresses to a firewall that I have listed!!!
Win 10. Threadripper 1920X 32gb Ram GTX 1080Ti GTX 980Ti 2xGTX 780
http://ajdesignstudio.co.nz/
http://ajdesignstudio.co.nz/
Hi,
Please give us time now to go through all the posts done during our short night sleep, sort them out and then we'll get back to you on specific points. Some of them are going to be easier to treat than others but we'll get through all of them for sure.
We highly appreciate your entousiam and will work now on fixing all the issues.
Cheers,
/M
Please give us time now to go through all the posts done during our short night sleep, sort them out and then we'll get back to you on specific points. Some of them are going to be easier to treat than others but we'll get through all of them for sure.
We highly appreciate your entousiam and will work now on fixing all the issues.
Cheers,
/M
Thank you, that's what I (we?) wanted to read.Nostromo wrote:Hi,
Please give us time now to go through all the posts done during our short night sleep, sort them out and then we'll get back to you on specific points. Some of them are going to be easier to treat than others but we'll get through all of them for sure.
We highly appreciate your entousiam and will work now on fixing all the issues.
Cheers,
/M
Intel 2x dualcore | 4 Gb Ram | XP 32| GTX470 | Driver 258.96
I've been in plenty of beta programs over the years, and I'm glad you're not letting the bugs bug you (ahhh ha ha ha ha, sorry I just couldn't resist).
I hope everyone here remembers that we are all beta testing still, and treat this release as just that.
Have a good morning/day guys
I hope everyone here remembers that we are all beta testing still, and treat this release as just that.
Have a good morning/day guys
CPU - i7-950 3.06 Ghz, 24GB Ram, Win7 x64, 2 display monitors, GeForce GTX 580 3GB Classified. I'm glad to say I LOVE OCTANE!
hi
i also have done some tests with supersampling..
1. if you change the supersampling to 2 and than to 4 and back to 2... the memory in the gpu will go up.. but it should go down
-> if you repeat it.. the memory overrun...
2. the supersampling icons in the viewport don't work..
3. on sharp edges with sunlight the supersampling value 2 looks great but with 4 or 6 the edges looks bad!!
i also have done some tests with supersampling..
1. if you change the supersampling to 2 and than to 4 and back to 2... the memory in the gpu will go up.. but it should go down
-> if you repeat it.. the memory overrun...
2. the supersampling icons in the viewport don't work..
3. on sharp edges with sunlight the supersampling value 2 looks great but with 4 or 6 the edges looks bad!!
Win7 64 | Geforce 470GTX 1280MB | Q9550 2.83GHz | 8GB Ram | NVidia 306.23 , Cuda 5.0.1
Hi guys,
Some facts:
* Octane connects to live1.octanerender.com on port 443 (HTTPS)
It does'nt connect to any other servers except offcourse the DNS lookup for the name as gristle pointed out (port 53 is a DNS server port)
The DNS port is a port on your ISP's DNS server, we don't have one.
* The workload is tiny aswell as the data sent/received. The server has been doing practically nothing the whole night since the release.
It's in a west coast datacenter in the US and can hadle easily 10000 octane live users.
* Octane pings the server every 10 seconds to be able to show you that it's still connected or not.
* Octane doesn't crash if it can't connect to the server, it will just display 'disconnected' and you can continue to work without making use of the octane live features (eg preferences, livedb, etc..., as long as the engine is started)
* The crashes are likely due to the many changes we made, or drivers. (i suggest installing the latest ones from the main nvidia site)
Or some other workflow, or simply a bug that was introduced when we added supersampling (which was a lot of infrastructural change, it's quite difficult on CUDA)
* Don't complain that supersampling is'nt working please, we specifically explained it in the release post that it's not finished yet.
Before i started doing graphics i was a unix sys admin for Sun Microsystems Belgium and installed many redundant large systems at banks etc, so i know how to install secure redundant backend servers, you should not blame any of the problems reported here on the backend server, it's been running fine all night.
Hope this answers some things,
Radiance
Some facts:
* Octane connects to live1.octanerender.com on port 443 (HTTPS)
It does'nt connect to any other servers except offcourse the DNS lookup for the name as gristle pointed out (port 53 is a DNS server port)
The DNS port is a port on your ISP's DNS server, we don't have one.
* The workload is tiny aswell as the data sent/received. The server has been doing practically nothing the whole night since the release.
It's in a west coast datacenter in the US and can hadle easily 10000 octane live users.
* Octane pings the server every 10 seconds to be able to show you that it's still connected or not.
* Octane doesn't crash if it can't connect to the server, it will just display 'disconnected' and you can continue to work without making use of the octane live features (eg preferences, livedb, etc..., as long as the engine is started)
* The crashes are likely due to the many changes we made, or drivers. (i suggest installing the latest ones from the main nvidia site)
Or some other workflow, or simply a bug that was introduced when we added supersampling (which was a lot of infrastructural change, it's quite difficult on CUDA)
* Don't complain that supersampling is'nt working please, we specifically explained it in the release post that it's not finished yet.
Before i started doing graphics i was a unix sys admin for Sun Microsystems Belgium and installed many redundant large systems at banks etc, so i know how to install secure redundant backend servers, you should not blame any of the problems reported here on the backend server, it's been running fine all night.
Hope this answers some things,
Radiance
Win 7 x64 & ubuntu | 2x GTX480 | Quad 2.66GHz | 8GB
ok thanks radiance,
well assuming its not the server and stuff there seems to be a serious problem introduced elsewhere.
Perhaps it is mostly an issue on 32 bit?? I am not sure. People are not reporting good detail.
I cant really do anything useful with it like this - its that bad - I mean crash! crash! crash! - probably I havent managed to run it more than 45s at most and usually about 10s so I cant really assess any new features and find trivial bugs.
Mostly I am just opening Octane, trying to do stuff and immediately looking at a 'needs to close message'....
For the record I am using Quadro driver 197.03 here atm.
I think this release is not cuda 3.1 yet, right??
well assuming its not the server and stuff there seems to be a serious problem introduced elsewhere.
Perhaps it is mostly an issue on 32 bit?? I am not sure. People are not reporting good detail.
I cant really do anything useful with it like this - its that bad - I mean crash! crash! crash! - probably I havent managed to run it more than 45s at most and usually about 10s so I cant really assess any new features and find trivial bugs.
Mostly I am just opening Octane, trying to do stuff and immediately looking at a 'needs to close message'....
For the record I am using Quadro driver 197.03 here atm.
I think this release is not cuda 3.1 yet, right??
Last edited by pixelrush on Fri Aug 13, 2010 9:27 am, edited 5 times in total.
i7-3820 @4.3Ghz | 24gb | Win7pro-64
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55
GTS 250 display + 2 x GTX 780 cuda| driver 331.65
Octane v1.55