Ok, first I should say that once I deactivate the OVP camera and re-activate, I can navigate the scene as usual.
face_off wrote:Hendrik - I think that there is some old Octane 1.20 settings in the RVT file causing this. Perhaps it is the sun vector at 0, 0, 0 (which would throw an error such as this). Could you pls reload the RVT file, and check the sun settings in the Settings tab.
Yes, the Sundir was stuck at 0,0,0. Even changing the Revit sun position did not change it. But once the OVP is toggled as described above, the Sundir parameter seems to update with Revit changes.
face_off wrote:EDIT: Could also be the aperture or scale being out. If we can identify the cause, I can code the latest version to ensure this does not happen.
Aperture at 0.10167 - seems ok (I still struggle with 5 decimals on these parameters! Simplicity plea!)
face_off wrote:EDIT2: It might also be a 0, 0, 0 camera up vector.
I wanted to check this but got my third Revit / plugin crash before I could. EDIT: Up starts at 0,1,0, which seems to be what it always is when the OVP camera is active.
CRASHES:
I got 3 so far, when running the plugin in Revit. Screen flashes black intermittently. Can't control anything. Task manager difficult to access / click on anything once it opens. Had 3 different escapes. a) Had to do hard reboot; b) clicked profusely on the 'end task' button in Task Manager and finally got a hit, which closed both Revit and, of course, the plugin; c) same action as b but this time only the plugin closed and Revit returned to normal. I am not exactly sure what initiated this behaviour but I am fairly certain it was when I was navigating in the Revit viewport (definitely so with the last crash)
I'm pretty sure it could be driver related but the fact that only the plugin closed on one Task Manager closure (of Revit), is a bit strange. I turned off hardware acceleration after b (as described above) but then still got it again as described by c (as per above).
I am a bit pressed for time in the next week or so but will try and install the 'certified' Revit driver (how often does Autodesk update that data I would wonder) and see how it goes.
EDIT: Opened Revit again after the crash (did not restart machine). Everything started ok but then the OVP lost track of the Revit crop window size. Come to think of it, some of the above crashes may have been related to Revit 3D view window adjustments (and also one section box adjustment).
Queries:
1. Should the FOV not inherit the Revit viewport FOV setting when the OVP camera is not active? I'm all for flexibility but once we mess with this in the plugin settings, there is no way to reset it to match exactly the Revit VP. Or is there?
2. Did we cover section boxes during the beta phase? I can't remember... and my other machine is now 'Octane-decommissioned' (have to deactivate Standalone AND plugin, to reactivate there) so I'm not going to check. But it would be great if we could get section boxes to work because it gives so many options in terms of creating various views.
Bugs?
1. The plugin VP does not adjust its view to correspond with the Revit view when changing Revit viewport size.
2. Once I close the plugin, it is greyed out in Revit and I have close my Revit session before I can reactivate the plugin.
3. The plugin does not remember the Cuda active device setting in subsequent sessions. This is soooo irritating because once I realise this is the issue my screen is already lagging bigtime and the mouse curser crawls over to the Cuda Devices tab, has a few miss-clicks until I can finally again deactivate the Quadro. I am pretty sure this is a Standalone issue since it happens there as well (at least in 1.2).
Useless information
The 3D transfor node is brilliant! I am so glad you added that in. Now we can do basics like change the orientation of floor boards or tiles on the fly. Yay!
Thanks again for a great plugin, Paul! It's got such a future!
Seeker