

pointer
Members-
Content count
46 -
Joined
-
Last visited
-
Days Won
1
pointer last won the day on November 7 2014
pointer had the most liked content!
About pointer
-
Rank
Advanced Member
Profile Information
-
Gender
Not Telling
-
Location
Midlands, UK
-
An addition to my post above. I have spent a solid day using above build and VRay. I am getting a crash if I have two model windows open and click on the rear window. This is happening quite a lot.
-
I'm having issues with 8.6.2 (build 10099). If I navigate to a palette after working on some modelling elements, I cannot scroll up or down within the palette dock, sometimes even after clicking with the left mouse button. To get around this I have to click with the palette dock with a scroll wheel click. Is anyone else having this issue?
-
Resolved. Thanks to Jaakko on the other thread as follows: I had same "Could not obtain VRay license" error. What I did was 1. I uninstalled both V-Ray and License Server 2. downloaded latest "vrlservice", link from Chaosgroup email, and installed 3. installed V-Ray After this it worked fine. I think it has something to do with earlier installs which get messed up. Hope this helps.
-
^ Thanks Jaakko - this worked for me too. All up and running now.
-
^ I am referring to purchased versions, not the beta!
-
^ I am experiencing exactly the same issue. I've posted the below in another thread: Great to see the releases today. I've followed the install to the letter but within FormZ I am getting the following warning 'Could not obtain VRay license'. I've logged into the Chaos Group License server and I can see that our two licenses are checked but not engaged. If I check the notifications section I have two entries, 1) vrlservice stopped and 2) dongle subsystem unavailable (connect ECONNREFUSED) Can anyone help out? I have tried restarting and also uninstalling and reinstalling the V-Ray license server too. Thanks
-
Hi All, Great to see the releases today. I've followed the install to the letter but within FormZ I am getting the following warning 'Could not obtain VRay license'. I've logged into the Chaos Group License server and I can see that our two licenses are checked but not engaged. If I check the notifications section I have two entries, 1) vrlservice stopped and 2) dongle subsystem unavailable (connect ECONNREFUSED) Can anyone help out? I have tried restarting and also uninstalling and reinstalling the V-Ray license server too. Thanks
-
-
Setting off multiple renders to reach the same SL level
pointer replied to pointer's topic in Maxwell Render Plugin
What would be the best way to render out multiple images sequentially? -
Setting off multiple renders to reach the same SL level
pointer replied to pointer's topic in Maxwell Render Plugin
Thanks Pylon, I think the issue here is as you say Maxwell is stopping due to time running out alongside running out of RAM. I need to read up sequential rendering as I admit I run multiple images on my own PC.. Thanks -
-
Setting off multiple renders to reach the same SL level
pointer posted a topic in Maxwell Render Plugin
I've had this issue happening to me for a while now (on V4 and V4.1) and I cannot work out if it's a setting or something I am doing wrong. I set off multiple renders one after the other, leave them for the same amount of time, same settings etc and I end up with some of them reaching a good standard (e.g SL 17) and some still on SL6 etc. Is this my PC prioritising certain renders over others? Certian view points requiring longer to reach the same SL, Or am I just doing something wrong? I don't seem to recall this happening before, but maybe I'm wrong. Thanks -
HI Tech, I have already sent Pylon my regular template model this morning, (based in UK so just waiting for Pylon to pick it up). I'm back working on V3 which is running fine, I have a lot to get through today. Thanks.
-
To add to above. I am now back on FormZ 8.5.6 Pro with Maxwell V3 3.2.1.5 and Maxwell Plug in 3.1.1.6. This set up works absolutely fine. If I add Maxwell plug in version 3.2.1.7 back in, FormZ will freeze on start up unless I rename the app date file etc and then it will only run for a limited time before I get another crash. Surely there must be a conflict between the two? I really need to solve this, especially as I have just purchased a seat of Maxwell V4 which I cannot use!, your help is very much appreciated Pylon.
-
Hi Pylon, I don't have another workstation to switch to at the moment. So I am going to jump back to V3 and the earlier plug in so that I can continue to work ( I will have to reload these on my machine). Yesterday afternoon I completed a fresh installation of FormZ 8.5.6 Pro and Maxwell V4 on my machine. This worked for a couple of hours and this morning I cannot open any model, or indeed a blank 'new' model. FormZ hangs up on start up and freezes again. Again, I remove Maxwell from the plug in folder and it starts up fine. I will send you my old template file, which I have been using for years. I don't have a particular project to send to you, the issue is happening on every project and each time I try an open FormZ! Not great.
-
I've been having the same issue as Andyb above using: FormZ 8.5.6 Pro with Maxwell V3 3.2.1.5. I also have the Maxwell Plug in 3.2.1.7 And now with: FormZ 8.5.6 Pro Maxwell V4 FormZ on startup and also whilst switching between open projects 'freezes up' and I have to force quit. Nothing functions and it appears as per Andy's screen shot above (some of the palettes are ghosted). I have been posting in the Maxwell thread because when I remove the maxwell folder from the FormZ plug in folder it opens fine, the problem first appeared when I updated the Maxwell v3 plug in to the latest one so that I could use the Maxwell resources again. I have upgraded to V4 and have just had the same issue. It ran OK for 30mins or so and then I switched between two projects and it froze again. The only way I can get FormZ to be stable is by 1) removing the Maxwell Plug In folder or 2) Renaming the app data file as you describe (a temporary fix it appears).
-
^update to above. I have reset to factory default preferences again, which is annoying but fixes the issue. Something somewhere is breaking down though, I will report back if I get the same problems in another week.