Some pre upload texture thumbnail testing

\

Here's the test Alfred-Wegener "Polar 6" texture

https://dl.dropbox.c...C-GHGF_test.zip

 

Both options working for me, I need some others to test this!

Feedback: PM me!

 

Thanks, Daniel

 

Your 2 thumbnails work just fine as intended. Nice bright colors.

No lighting in the GNS area but the Reality XP 530 has full lights when moved to the VC1 area.

Self-illumination turned on now, please re-download _allblank mdl. May well look horrible at first, but should allow tweaking. Just to check whether this is the right way to go.

 

https://dl.dropbox.com/u/51024107/DIY_panel_01.zip

I've noticed a tendency for what seems like the throttle sticking occasionally. Has anyone else seen this happen? I don't think it's a controller issue, the same thing happens when I adjust the throttle using the keyboard, and I see the throttle lever move but according to the gauges and aircraft behaviour the throttle setting doesn't seem to change. It might be happening at higher throttle settings but I haven't tested it extensively. I know turboprop engines can react quite slowly to throttle changes but this is way beyond normal. I'm getting round it by killing the engines and doing a fast restart (which thankfully happens quite quickly) but I'd rather not be doing this on final!

 

Thoughts anyone?

Don't firewall engines to begin with, except maybe on T/O.

Don't firewall engines to begin with, except maybe on T/O.

 

That was my first thought, so I made sure I kept the throttle out of the red zone and still got the sticking. I'll try again with the throttle lowered a bit more. Thanks.

Self-illumination turned on now, please re-download _allblank mdl.

 

https://dl.dropbox.c...IY_panel_01.zip

Thanks again for your work. I will test it later and report back.

Edited. Works like a treat now. The gauges show up at night and allow for their lighting to work. But I will stick to the 3D models I think, they look great. But I'm sure the other folks will like the added tweak options due to the new panel structure.

 

On the throttle sticking issue. I only get this when testing roughly by using the keyboard to set TO power. Means that F4 is used and I just check something like the things on the panel setup or so. By using this method, I can see that the full power remains, even when pressing F1 multiple times or using the hardware throttle of mine to return to save engine speeds.

 

So it seems like the full power drives into a condition from which the throttles have to recover, so to speak, and take time to do so. The longer you apply full power, the longer they will stick in that condition.

 

As said, only happens when smashing them to the stops, not when using appropriate takeoff power settings.

The gauges show up at night and allow for their lighting to work.

 

Very good, I'm relieved to hear it. Let me know if further tweaking from my side is needed as may be because self-illumination needs to be burned into the mdl.

 

in the next few days I'll upload a fully updated BT-67 package integrating all the bugfixes made so far. I'll be away for a while starting next week but Daniel's repaints are in the offing and the team is watching this thread, so further suggestions can by all means be collected and considered for a future V3. It so developed that we were actually using you as testers and I want to say that I am extremely grateful for all the constructive comments made here.

 

Cheers,

Manfred

We have to thank you guys, Manfred. I never ever saw such an excellent service and that's from payware standards, while you folks offer your work for free. :Applause:

 

 

On the model with the self-illumination. I guess I'll let the other guys speak.

 

I'm back on the 3D GPS models (with just the RXP screens), as planned. While the other model allowed for full VC RXP control, the optics with the flat appearance came in too much as a downside for me.

 

Great idea on the fully patched package. I guess this will help the guys not reading every page of this thread.

On the throttle sticking issue. I only get this when testing roughly by using the keyboard to set TO power. Means that F4 is used and I just check something like the things on the panel setup or so. By using this method, I can see that the full power remains, even when pressing F1 multiple times or using the hardware throttle of mine to return to save engine speeds.

 

So it seems like the full power drives into a condition from which the throttles have to recover, so to speak, and take time to do so. The longer you apply full power, the longer they will stick in that condition.

 

As said, only happens when smashing them to the stops, not when using appropriate takeoff power settings.

 

Yep, it was "engine abuse". 80P When using more realistic power settings I don't get the throttle sticking. Nice to see an aircraft where some engine management needs to be appled! So many don't (not something we EVER make use of in racing.... :P). I'd never come across throttle sticking as being the result though; the more usual outcome seems to be a gentle unpowered glide back to earth.....

Nick, I still think that the sticking shouldn't happen. But we may agree that doing something wrong (firewall throttles at sea level in the Basler) to cause some 'other wrong' to develop is nitpicking to say the least.

 

I can only guess, but I think that something happens and 'gets sticky' when going at or above 100% torque. 100% throttle at altitude isn't a problem, this worked fine here for some hours, without sticking.

Thanks Manfred and team!

 

Here is my layout for the moment. I changed some of the guages to the Carenado 208b becuase they have a little more resolution for my 8040x1600 rig. Click for full size.

 

Pleasure. Yes, those HD gauge bitmaps certainly add a lot more quality to the panel.

Right you are. But Daniel's trouble was that he has one livery with two options. Ski and no ski. So he was looking for a way to have two different thumbnails and only one livery texture folder.

 

Here is where the true "power" of the texture.cfg really show it's stuff!

 

In the ski version's ..\texture.ski folder:

 

[fltsim]

fallback.1=..\texture.noski

fallback.2=..\texture

fallback.3=..\..\..\..\Texture

fallback.4=..\..\..\..\Scenery\Global\texture

 

The only bitmap required in the "ski" variant's folder is the one that's different from the "noski" version, and its own thumbnail.jpg file...

 

The texture.cfg will "fallback" first to the ..\texture.noski folder for the remaining bitmaps, then "fallback" to the root ..\texture folder for whatever is left, et cetera...

 

The principle advantage of the texture.cfg paradigm of course is that it completely eliminates the need to have any duplicated bitmaps, which reduces the entire package size considerably! :p0303:

I solved it now using 2 texture folders: texture.C-GHGFski and texture.C-GHGF

texture.C-GHGF contains the full texture set + no ski thumbnail

texture.C-GHGFski contains only ski texture, ski thumbnail and a texture.cfg fallback to the no ski 'Polar 6' texture base folder. It's the easiest way and you don't mess up the Basler root directory with thumbnail images ;)

 

Textures will follow with v2.0!

 

Greets, Daniel