emerkel Posted July 30, 2015 Share Posted July 30, 2015 Hi Andre,I saw in the most recent update (6.39) there is a possibility of importing 3d shading objects. In the past, objects (regardless of location in the model) have imported as 'ground' objects and don't factor into the shading table. Has this changed? I've imported a shading object but it is still recognized as a ground object and doesn't affect near shadings. Is the import process different for these shade objects or is this functionality still not ready?Thanks!Evan Link to comment Share on other sites More sharing options...
André Mermoud Posted July 31, 2015 Share Posted July 31, 2015 I don't know. The Shading objects should be defined as such in the Helios3D program. It is a specific definition in their output file. Now there may be a "youth" problem with this import. Please send your Helios3D file (*.h2p) to support@pvsyst.com. Link to comment Share on other sites More sharing options...
Helios210 Posted August 21, 2015 Share Posted August 21, 2015 (edited) Hello,I've spent some time attempting to understand how PVsyst interprets the .h2p file so I can automatically build them with something like a PYTHON script, this is what I have so far:INSERT10 - Unknown, seperates panel from ground object if changed22.467,3.532,6.914 x,y,z co-ordinates50 - Unknown, causes maximum orientation difference error90.00 - Azimuth55 - Unknown, causes maximum orientation difference error30.96 - Baseline Slope56 - Unknown, appears to have no effect0.00 - TiltDGM - Defines plane as ground object5.000,0.000 ,6.840; 0.000,5.000 ,9.840;0.000,0.000 ,6.8400.000,5.000 ,9.840; 5.000,0.000 ,6.840;5.000,5.000 ,9.840I want to define the plane as a shading object, not as a ground object.I've also tried using Skellion's Export to PVsyst functionality with the same result - I can only seem to create ground objects when I really would like shading objects.Many thanks,H. Edited August 6, 2018 by Helios210 Link to comment Share on other sites More sharing options...
André Mermoud Posted August 21, 2015 Share Posted August 21, 2015 The format .h2p has been developed in collaboratioon with the Helios3D team, specifically for the import of helios3D files. It has not been published, and we don't intend to completely document it in a near future as it is still evolving, nor to support its use. Skelion has used it for their plugin, but without any contacts with us. PVsyst doesn't support the Skelion files. Link to comment Share on other sites More sharing options...
oron Posted January 6, 2016 Share Posted January 6, 2016 hello andre,is there a plan to support the skelion files?skelion export the model to *.h2p like helios3d.this kind of support can really eas up thing and allow us planners to do a realistic simulations. Link to comment Share on other sites More sharing options...
André Mermoud Posted January 7, 2016 Share Posted January 7, 2016 Skelion exports models from the Sketchup representation, but the representation of objects in Sketchup is not really compatible with the way PVsyst is waiting for shading objects. You can try importing these scenes, perhaps they will look correct, but we don't guarantee the shading calculations. We will implement our own Plugin for Sketchup within the next months, with our own constraints about the structure of the object's representation. Link to comment Share on other sites More sharing options...
kautzer Posted April 27, 2016 Share Posted April 27, 2016 Hi Andre,Any updates as to when PVsyst will have its own Sketchup plugin? Thanks. Link to comment Share on other sites More sharing options...
anjana961 Posted July 26, 2016 Share Posted July 26, 2016 Hi Andre,Is it possible to import jpeg image files into PVsyst for use in shading scene? Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now