Recent content by jarmonik

Yeah, it looks like RA is counted in opposite direction. And there is then of-course the Earth Mean Equator and the current actual pole from oapiGetPlanetRotationMatrix() which might explain the difference in Dec. In which case the pole should be replaced by earth mean pole, obliquity of...

It's a debug feature to allow to take the camera behind the scene to see how planetary tiles are rendered. Might be good idea to disable in "Release" build.

I haven't run any tests but this is what I came up quickly. Should precession be included ? double z = dotp(apparentLOS, pole); double Dec = asin(z); Vector Aries = _V(1,0,0) Vector X = crossp(pole, Aries).unit(); Vector horiz = apparentLOS - pole* dotp(apparentLOS, pole); double hlen =...

The vulkan client that I am working on is about 50% complete. There's lot of background work done such as DDS de-compressor and compressor, Image loaders/savers, mesh renderer, dynamic object/buffer managers (not build-in feature in Vulkan), Orbiter API 2D surface interface and plenty of vulkan...

Sorry, I can't verify a bug. The error code indicates that D3D9Client.dll doesn't found. Which is kinda odd. I don't recall reports of this kind of problem before. Could this be some kind of protection issue "access denied" If you install Orbiter under "Program Files" folder then that's a way...

The crew is preparing to get some sleep. I'll appreciate a lot if some-one can sleep under those conditions. The excitement and stress would mess up my head and I would be getting any sleep. But I guess that these guys are so experienced that this mission is not much more than a busy day on ISS.

That was a great launch, mankind is once more on it's way to the Moon. Hopefully we will see Lunar landing with-in the next two years. Would like to see the TLI but I'll have to get back to bed. Go Artemis.

Had to wake up middle of night for watching the launch, looks like we are still go for launch...

That's a potential fire hazard. Maybe just a black image on a full-screen on an image viewer.

This is exactly how it is. There is a work-a-round: Press Ctrl+Alt+Delete to cause the window to pop-up on purpose. Click "Ok" to close the window and then shutdown your display. Orbiter should keep running without graphics. When you are ready to continue. Turn on your display and shutdown...

That sounds like a good idea. It could be easier for everybody if add-on specific files are located in add-on folder. That is also great idea, it's been on my mind long time. There's no dependency management of any kind right now and it must improve. Maybe the dependencies could be checked...

Could we simply contact them and ask for a license assuming, that it's free, and hopefully something that we could redistribute. At least for a time being until we got an open source replacement ready. Starting to pay for a license that's no go.

Having a lot of add-ons that do not work and causes a system crashes must be very annoying for users. So, is there something we could do about it ? 1) I suppose we could try to improve debugging and compatibility from orbiter side but it does have it's limits. It would require people with...

In Orbiter 2016 D3D9Client doesn't have access to a scenario information such as runway lights configuration etc... So, the client must reload all the configuration files starting from Scenario file to Sol.cfg, Planets and bases. The error is a result of inconsistency between what Orbiter has...

Nearplane 0.0f will causes a fault. Must be higher than zero and as large as possible. Orbiter uses 0.1f or 1.0f for VC and exterior values varies by camera-vessel, camera-ground distance from 0.1 to 1e3. Farplane is non-critical.