The minimal sample of BIMSurfer v3 doesn't work with the latest version of BIMServer.

[diegovisentin]

In version 1.5.187, something must be wrong between BIMServer and BIMSurfer because even the minimal example does not work.

Steps to reproduce the behavior:

1. Makes the appropriate configurations to the "home\plugins\org.opensourcebim.bimsurfer3-0.0.277.jar\apps\minimal.js" file
2. Start BIMServer
3. Point to "http://localhost:[port]/apps/bimsurfer3/apps/minimal.html"
4. No 3d drawing appears
5. Redoing the steps with the previous version 1.5.186 instead works

An incompatibility has probably been introduced between the client and the server with the current version, though I can't identify the cause. I was only able to verify that login and project retrieval are successful, but downloading and drawing are not.

[hlg]

Thanks for reporting. I've been able to reproduce this. It seems as if execution of BinaryGeometryMessagingStreamingSerializer is broken. With 1.5.187, during download with this serializer, there is a very short stream generated with 88 byte only and GeometryAccellerator reports a total of 0 triangles. This serializer works a bit different from most others. I am going to scan through the changes to find the one(s) that might have affected the download with this type of serializer.

[hlg]

I found the reason for this regression: 10fe78a. Somehow, the query in GeometryAccellerator does not work anymore.

BIMserver/BimServer/src/org/bimserver/geometry/accellerator/GeometryAccellerator.java

Lines 131 to 153 in b27aa20

	Query query = new Query(packageMetaData);
	QueryPart queryPart = query.createQueryPart();
	queryPart.addType(packageMetaData.getEClass("IfcProduct"), true, excluded);
	Include product = queryPart.createInclude();
	product.addType(packageMetaData.getEClass("IfcProduct"), true);
	product.addFieldDirect("geometry");
	Include geometryInfo = product.createInclude();
	geometryInfo.addType(GeometryPackage.eINSTANCE.getGeometryInfo(), false);
	geometryInfo.addFieldDirect("data");
	geometryInfo.addFieldDirect("boundsMm");
	Include boundsInclude = geometryInfo.createInclude();
	boundsInclude.addType(GeometryPackage.eINSTANCE.getBounds(), false);
	boundsInclude.addFieldDirect("min");
	boundsInclude.addFieldDirect("max");
	Include dataInclude = geometryInfo.createInclude();
	dataInclude.addType(GeometryPackage.eINSTANCE.getGeometryData(), false);
	dataInclude.addFieldDirect("boundsMm");
	Include dataBoundsInclude = dataInclude.createInclude();
	dataBoundsInclude.addType(GeometryPackage.eINSTANCE.getBounds(), false);
	dataBoundsInclude.addFieldDirect("min");
	dataBoundsInclude.addFieldDirect("max");

I did not yet understand how the direct references in this query and the object placement query work differently. Below is the codes that creates the directField entries in the object placement query for reference.

BIMserver/BimServer/src/org/bimserver/BimServer.java

Line 750 in 7f1661e

objectPlacement.makeDirectRecursive(new HashSet<>());

BIMserver/PluginBase/src/org/bimserver/database/queries/om/Include.java

Lines 290 to 312 in 7f1661e

	public void makeDirectRecursive(Set<Include> done) {
	if (done.contains(this)) {
	return;
	}
	done.add(this);
	if (this.fieldsDirect == null) {
	this.fieldsDirect = new ArrayList<>();
	}
	if (this.fields != null) {
	this.fieldsDirect.addAll(this.fields);
	this.fields.clear();
	}
	if (hasIncludes()) {
	for (Include inc : this.includes) {
	inc.makeDirectRecursive(done);
	}
	}
	if (hasReferences()) {
	for (Reference reference : references) {
	reference.getInclude().makeDirectRecursive(done);
	}
	}
	}