Thanks for the report. Can you please post a detailed instructions on how to reproduce that (and links to any addons/modules required) so I would be able to check it out?There seems to be a rather weird occurence with Greg Burch's modules. Looks like a Normals issue to me, but the modules work perfectly fine in vanila as well as in d3d9 client, so I guess you would want to know about it:
Also, another issue: Meshes added to a vessel with VESSEL::AddMesh() during runtime don't seem to be visible.
Ok I will take a look at this.
UCGO has been tested by several users in D3D11CLient and there have been no issues. I can't fix this issue unless there is a way to reliably reproduce it...
This one should be fixed now - please download latest version and confirm if it indeed is fixed.
Can you please mark on the screenshots what is wrong? Is is the issue with incorrect solar arrays rotation? Or something else?
I looked at this problem and wasn't able to identify issue. Can you please tell me what function do you use to rotate meshes?
That was my point
I dunnow why and how it works in D3D9 client, but I do know that Dan is manually transforming vertices for rotation in UCGO - I know this because he has asked me to assist in this issue, and I've developed a function for him to do such transformations.
Here is a function that builds rotation matrix for rotation along arbitrary axis (rotationAxis has to be a unit-vector, angle is in radians):
void BuildRotationMatrix(MATRIX3& result, const VECTOR3& rotationAxis, double angle)
{
auto c = cos(angle);
auto s = sin(angle);
auto t = 1.0 - c;
auto x = rotationAxis.x, y = rotationAxis.y, z = rotationAxis.z;
result = _M(t * x * x + c, t * x * y - s * z, t * x * z + s * y,
t * x * y + s * z, t * y * y + c, t * y * z - s * x,
t * x * z - s * y, t * y * z + s * x, t * z * z + c);
}MATRIX3 rotMat;
BuildRotationMatrix(rotMat, _V(0.0, 1.0, 0.0), M_PI / 2);
auto srcVector = _V(1.0, 0.0, 0.0);
auto res = mul(rotMat, srcVector);MATRIX3 total = identity(); //identity matrix
MATRIX3 matRot;
//roration along X axis
BuildRotationMatrix(rotMat, _V(1.0, 0.0, 0.0), angle_X);
total = mul(total, matRot);
//roration along Y axis
BuildRotationMatrix(rotMat, _V(0.0, 1.0, 0.0), angle_Y);
total = mul(total, matRot);
//roration along Z axis
BuildRotationMatrix(rotMat, _V(0.0, 0.0, 1.0), angle_Z);
total = mul(total, matRot);
---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiBlt
Colour key argument not supported by graphics client
---------------------------------------------------------------
Finished initialising panels
D3D11Client::clbkGetViewportSize
Finished setting up render state
D3D11Client::clbkPostCreation---------------------------------------------------------------
>>> WARNING: Obsolete API function used: oapiRegisterMFDMode
At least one active module is accessing an obsolete interface function.
Addons which rely on obsolete functions may not be compatible with
future versions of Orbiter.
---------------------------------------------------------------As we all know, planets and moon don't actually emit light - they just reflect sun light. So this is how that could be approximated for atmosphereless bodies:
I have a new HDR post-processing engine almost ready (actually two engines - one is based on Compute Shaders, and another one is based on Pixel Shaders), so this could be solved by that. The reason I'm planning to put on two engines is that on different hardware these approaches give different results - on some HW PS-based engine is faster, on others - CS-based. So I've decided to let user play with them and choose the one that is faster for his hardware.
What version do you have? Please post here a full orbiter's window header.
