JeromeHeretic

Man, aren't they call you Speedy Gonzales? :-) Thank you!

Hello mr. @JonnyOThan, I noticed that in version 1.0.1 are not working descriptions for action group square lighting buttons (that AG1=something description made in VAB). In IVAs with moardv avionics this descriptions works fine. I tried swap to previous version 0.31.13.4 and there descriptions work fine. So it's 1.0.1 specific bug.

Upgraded to version 14.40.33810 and can confirm, that von Koch works perfectly now. Thank you guys...

Loudness you can change in setup. There is button you can move left or right for alarm loudness.

Ah, great... Thank you mr. Krazy1

I have problem with von Koch release. When i click tracking station, game crash. I want ask if somebody have the same experience or it is some black magic of my specific mod setup? I have there also Principia Kleene release, and this one is running fine.

Can you please do FreeIVA for MOARdV Plus?

Aha, so i found, that i have some IVAs which are using MAS_ASET_ALTIMETER_Adv and some using ASET_ALTIMETER_Adv from consolidated pack. And in MOARdV config is hands functionality wrong. Anyway... that's not problem of ASET consolidated pack.

So this is working only partialy. Tiny hand is OK, it is showing tenth of thousand now. But hundred hand an thousand hand functionality is swapped. But i don't understand why. As im looking in configs, it looks correct to me. ALT100, where is modulo 1000 and ALT1000 where is modulo 10 000 should work correctly IMO, but don't...:-/ EDIT: At the end i found, that it is problem only in Mk2 inline IVA retro cockpit, so it is error in setup of this IVA. In other cockpits altimeter works correctly. Yes, it was completely W.T.F for me, when i was looking for...

Confirm, that this works. (Tomorow i want try patch altimeter, if will have time.)

And what about Desert airfield navigation? As i was looking, adding new navigation transmiters is not easy. It's defined on so many places. Do you understand to it? BTW: It was just "nice to have" idea. Is teoreticaly possible build on planet real transmiter (probe core, battery, antenna) as VOR? Let say, i will do transmitter like this, and name it VOR_115.30, si it will be automaticaly visible by ASET pack as VOR on freq 115.30 MHz... Like that you can do your navigation network on any celestial body, not just on Kerbin (you can do it anyway, and use it as VOR by selecting it as target, but ASET pack will not see it and you can use it just like target on navball.)

I see, this error is old as the game itself and ASET pack just inherit it from ingame objects. Well, in my opinion it is incorrect. When you are doing pack of gauges and trying to make it so close to reality as is possible, is incorrect, when the gauge is not working as in real aircraft (absolutely independently on rules how original ingame gauges are working). Isn't possible do workaround by some unity config? If is possible by config just swap functionality of tiny hand (as the values comes from game engine) with funtionality of "hour hand" as it comes from ksp engine, is problem fixed. Hundred hand is ok, just somehow swap values for rest two... I'm thinking on some workaround just swap that two values without touching models (but i don't know unity.... so it's just a question).

If you are collecting bugs for next release, so on this altimeter: That tiny hand, with small triangle at the end, which looks as second hand on watch is in reality showing 10 000 (feets/meters/whatewa units), long hand, which looks as minute hand on watch shows hundreds of units and short one, which looks as hour hand shows thousands of units. So what is on screenshot should be altimetry something like a 7900 meters (because tiny shows 7000, minute shows 900 and hour hand is completely wrong,, should be around 7) , but in game it is showing 1970 meters (hours 10 000, minute 900, tiny 70). I don't know if this is extra setup in every IVA, or it is global settings?

Ah so, will check it next time. I think (at least for me), slow refresh rate is OK for me. I need it just for orientation for start retro burn of last landing phase. Under 5000 meters there's other gauge. I'm using that display only for aproximation of retro burn start. After that it's not important for me anymore, using other gauges around window. But thx for answer...

In Mk1 lander can is also non functional switch on altitude display. Switching between altitude and radar altitude is not working. But i wanted to ask why is not in ASET avionics any navigation for Desert airfield? There's no VOR, no directional navigation, no glide slope navigation. I was looking if is possible easily add at least VOR, to be able to find airfield by navigation instruments, but as i was looking i noticed, that i absolutely don't understand it at all, so i give up. Will be nice have it. That runway is realy short and is pretty hard land on it even with normal aircraft, land on that with big aircraft or with a shuttle is without instruments almost impossible. (And this runway is good for landing from polar orbit, because is in north south direction...)