Search results

Ok, I've started on the PNG export. Check out the 12-png_export branch if you want to follow progress. I'm exporting to 16-bit single-channel (greyscale) format, which seems to be read without problems by the latest Gimp. I think for now I will implement the 2-file (PNG/meta) solution. It's a...

I'll look into that. Good idea - at least for the elevation data. I don't want to allow editing the surface layer, since it uses a lossy (DXT1) format, which means that every edit cycle potentially degrades the data. The surface layer should always be edited directly in the source data. I...

Here is a trial build of the Qt-tileedit version I've been working on. This should work stand-alone without the need of installing any Qt runtimes. It has all the functionality of the original Matlab version, with a few notable additions: It can read from compressed archives as well as the...

I'm monitoring this thread, but I am unlikely to find time to do much on this for a few weeks. Just to be clear: the idea here is to flatten the terrain on the fly at runtime, rather than an offline tool that performs the flattening by modifying the elevation tiles, correct? And the flattening...

I haven't thought about that yet, but there is no any immediate rush to change anything here. Maybe the base/pad number reference can be replaced by a location identifier that can be added to the quadtree tile, to avoid having to enter the location in the scenario file by hand. In any case...

Tree merging would indeed be a very useful feature, not just for a future surface structure layer. Alternatively for the surface structure layer at least, it may be possible to do the merging at runtime by Orbiter itself, since unlike the other layers this is fairly trivial (just add the...

Regarding terrain flattening, a few things to consider: * currently, the vertical elevation resolution is quite low (1 meter in 2016, potentially finer in the beta, but only globally, and only if the total global elevation range can be encoded in 16bits). This means that smooth gradients can't...

No worries at all, mate, and I do appreciate the constructive criticism. :cheers: I definitely agree that user-friendliness is important, so the VesselBuilder addon is a huge step in that direction. Hopefully the new tileedit tool will make it easier to flatten runways, so that problem might be...

I don't want to hijack this thread, which after all is an announcement of a new AMSO version, which is big news in its own right for many users. However, it looks like some response is in order, so here goes: I don't see any problem with developers writing addons for previous Orbiter versions...

Thanks - looks promising. I'll try it, I'm just a bit worried about the OpenSSL dependency which I don't need. Hopefully that can just be ignored. Yes, Qt isn't exactly a lightweight package ... Hopefully the static linker is clever enough to include only the actually referenced modules in the...

The new Qt version of tileedit now has approximately the same functionality as the previous Matlab version, so I'll include it from the next Orbiter beta. I have a question though: By default, Qt only supports dynamically linked applications. This requires them to ship with a fairly extensive...

Good to hear that it works now! Although the fact that lift and drag for the horizontal foil are now zero makes me slightly ... uneasy :lol: What happens if you remove that airfoil altogether? Does it behave the same? Just to confirm: Your lift, moment and drag coefficients _are_ symmetric...

Good to hear that Orbiter is still going strong there. Say hi to Manuel, Andreas and Valerie if they are still around :thumbup:

Out of interest (but slightly off-topic ;) ): are you by any chance at the IRS at Uni Stuttgart?

The point I was making is that if you have a body that is rotationally symmetric w.r.t. its longitudinal axis (as I guess your capsule approximately is) then your two airfoils probably will also have identical and symmetric lift characteristics. Therefore the body's rotation along its...

This is a stab in the dark, but is it possible that the problem is that both your airfoils are generating drag, but (effectively) only one is generating nonzero lift?

You declare (and use) variable MFD_buttons, but you never define it, unless that bit was omitted from the code snippet. Also what is the difference between MFD_buttons and MFD_BUTTON_POS? Finally, you address MFD_buttons with indices 1-3, but the valid range is 0-2. If you drop a breakpoint in...

sed?

I had a quick look at it. At first glance, it seems very - colourful :lol: This appears to be a mosaic that combines a panchromatic Cassini ISS band with multispectral infrared information from VIMS. Note that the latest highres Titan textures are already based on the Cassini ISS mosaic...