Search results

The current HEAD should be Ok. I have detected some problems with zero-initialization, so, maybe the whole code base should be checked. D3DXVECTOR3 myVec = {0} // Compiles fine but fails to zero initialize struct myStr { myStr() { } int a = 0; int b = 0; } auto x = new...

Hi, I would need to be able to compile this project to debug the issue with moving docking port while docked. I get a lot of errors like "fatal error C1083: Cannot open include file: 'Orbitersdk.h': No such file or directory". Do I need to install the project in some specific location or edit...

Thanks for you help. I think I managed to get it sorted out. I created a new branch on a top of main and then used TortoiseGit to cherry-pick a range of commits from the "some_fixes". Yeah, it would be good idea to do more extensive code testing before merge. I did plenty of testing and...

I tried that and it made it look even more messed up. But I'll try it again. Yes, I made a backup copy of the repository.

Yes, the revert is merged. This is the current layout: X-Main-Main-X-Main-Main-X \ / \ / Feature Revert I want the re-apply the Feature on a top of main and continue working on it X-Main-Main-X-Main-Main-X \ / \ / \ Feature Revert...

I haven't had any luck. Looks like it refuses to rebase the branch because it's merged already. Maybe it's easier to create a new branch and re-commit the code.

I found my self in a trouble with the Git once more. I had to revert (undo) a merge of a bad pull request. I restored the branch "some_fixes" but it shows 3 commits behind, 0 ahead. When is should be 0 behind and about 10 ahead. So, I guess I need to re-base it somehow and I don't want to mess...

No, everything is working perfectly fine. Those caps that shows in your screen shots are very hard to miss. I am a bit puzzled by the problem. I have reverted the Orbiter Main back to it's previous state. Could you check that it works as usual ?

I have restored the old cache. So, let's see how this goes ? The binary goes in /Modules/Server/ Have you checked if the problem appears with the DX7 inline engine, if you are able to run it ?

Thanks for testing. I'll restore the previous cache code so that we can be sure that's it's cache problem. Problem is that the cache is for a physics. Graphics has it's own independent elevation management.

I still haven't been able to reproduce the problem but I did found a memory zero initialization problem that might have cause the issue. Here's a new binary for testing, could you check if the problem is fixed. Copy the file in /Modules/Server/ folder. This is x86 binary.

When doing debugging I noticed a problem in a tile elevation cache and fixed it (at-least, so I thought). I did plenty of testing with the new cache and never saw any issues. So, those screen shots are pretty concerning.. Something is a miss but what exactly. Is the flat area always under the...

There are some water rendering adjustments coming in in next version.

It's been noted. D3D9 is falling apart, newer laptop computers can't run it anymore. New replacement is planned and we need a better GUI, before that happens, I don't think I'll start working on any new graphics features.

Ok, so the need to move the docking port comes from a simulation of more realistic docking sequence. That's vital piece of information.

Thanks, I have checked the source codes and there are no changes related to docking routines. What is the severity of the problem ? If I start working on it, it will take quite some time since I am totally unfamiliar with the code in question. Martin would have a better insight. If a fix is...

Could you show the code that does this "trick" ? I'll look into it. The code that's been working before.

Yes, Done.

There's no lens flare, just the sun glare which can be tuned in realtime from D3D9Graphics Controls, you can also customize it by editing Glare.hlsl in /Modules/D3D9Client/

The changes in the HUD are not intentional. I'll compare the code to O2016 and try to fix it. The LaTeX demo looks very good. I used LaTeX to make IMFD and LTMFD manuals but haven't touched it past 10 years. It is one option to consider but would require wider discussion about documentation...