Search results

Just drag the image to a new location to save it. ---------- Post added at 05:40 AM ---------- Previous post was at 05:32 AM ---------- File lease is this: Orbiter\Images\CurrentState.jpg

Just use tileedit

Does this not work? I do not know why I have not tried anymore .... https://www.orbithangar.com/searchid.php?ID=5607

NOW WORKS !! :woohoo: Thank!!

Sorry i would have a question, I have always used OrbiterSVN, now I have also downloaded Orbiter2016 with all HR texture packages but with D3D9 you can not see the waves... With Orbiter SVN: Do I have to set something up?

Widewake is one of the most beautiful bases of Orbiter(for me), it's a sad thing not to implement it in Orbiter2016, I think anyone who uses Orbiter has Wideawake in the addon list. When I downloaded Orbiter Beta, the first thing I checked was the island of Ascension ... and there was not ...

:lol: You need to be more precise with the coordinates. :cheers:

When...I downloaded the mesh and made the code, and it works. I changed from quadrilateral to spherical: oapiVCSetAreaClickmode_Spherical (AID_NAVMODE, _V(-0.1264551,1.500134,2.812949), 0.015); Also in quadrilateral mode (I have redone the coordinates)...

Sorry Gattis, the command should make KILLROT, but it may not work if the vessel is stationary, try to change the command to PROGRADE ... only for a check In clbkVCMouseEvent case AID_NAVMODE: //BREAK ToggleNavmode(NAVMODE_PROGRADE);

It works?

bool TALON::clbkLoadVC(int id) { switch (id) { case 0: // commander position SetCameraOffset(_V(-0.41, 1.6, 2.241)); SetCameraDefaultDirection(_V(0, 0, 1)); SetCameraMovement(_V(0, 0, 0.2), 0, 0, _V(-0.3, 0, 0), 75 * RAD, -5 * RAD, _V(0.3, 0, 0), -20 * RAD, -27 * RAD)...

You put the coordinates in the wrong sequence, see above .... oapiVCSetAreaClickmode_Quadrilateral(AID_NAVMODE, _V(corner#1), _V(corner#2), _V(corner#3), _V(corner#4));

You can also use a mesh to better calculate the coordinates in 3D space.

The coordinates of my code are not those of TALON, you have to put the correct TALON coordinates

In my opinion, you have a coordinate problem, usually the X coordinates are the same in the first group of two and change the Y coordinates, and the second group of two. The Z coordinates are all equal, of course if the area does not have strange inclinations. This is the code I use and it...

Try it like this, just KILLROT... bool TALON::clbkLoadVC(int id) { // ID is the Preset Camera Position huds.size = 0.3; huds.nmesh = 2; mfdController->HandleLoadVC(id); oapiVCRegisterHUD(&huds); SURFHANDLE const tex1 = oapiGetTextureHandle(meshhg_VC, 5); // switch (id) { // case 0: //...

Maybe you have to move the code? bool TALON::clbkLoadVC(int id) { // ID is the Preset Camera Position huds.size = 0.3; huds.nmesh = 2; mfdController->HandleLoadVC(id); oapiVCRegisterHUD(&huds); SURFHANDLE const tex1 = oapiGetTextureHandle(meshhg_VC, 8); switch (id) { case 0: //...

The code you write is used to draw bitmaps, does not need this if you use the meshes.

Certainly, the important thing is that the coordinates are correct and do not overlap with other functions.

You can use the shuttleA code in Orbiter SDK