MarkHurst
-
Posts
409 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Posts posted by MarkHurst
-
-
19 hours ago, BudSpencer said:
The pitches of the sound files STILL don't blend into each other at all, not even nearly!!
It's hard to know what you're referring to unless you post some examples. I think the new sound is much improved. I posted a link to a test flight earlier.
-
1
-
1
-
-
10 hours ago, pierre fsx said:
hi,
Hi am back flying with the twin otter and i cannot get the GNS 530 to work. I get a message "ok" flashing white see picture and it seems to be stuck there?
What do I have to do to get it working?
Thanks
Have you tried pressing the ENT button?
-
1
-
1
-
-
You need to use the variables that start with "KAP140_". Have a look at this video, which shows me doing it in SPAD.neXt.
-
1
-
-
On 12/3/2022 at 9:12 PM, Allard said:
I have the exact same issue. I don't use the WT GNS 530 and I don't have any autopilot mods installed. I do have a Honeycomb Bravo connected but it happens even when with the rotary dial set on Heading. If the rotary dial would send pulses it would be to the heading bug.
Perhaps something else is sending repeated commands. I haven't checked recently, but MSFS used to have the design 'feature' that buttons held down would send the mapped command over and over again. So if you have a stuck button, or if you have an unexpected function mapped to a toggle switch, you would get that effect. Also, the described effect (held altitude incrementing by 100ft over and over) is reminiscent of what the 'UP' button on the KAP140 does when in ALT mode. It's supposed to increment by 20 feet but when I checked it incremented by 100ft, thought only once. (Perhaps a later update has modified that.)
-
2 hours ago, PaladinX said:
Hello? Any help from Aerosoft?
Since the Honeycomb Bravo seems a common factor here, have either of you tried disconnecting it to see if that makes a difference?
-
Approach sound. This was the first (new) beta, so the mix changed a bit.
-
1
-
-
2 hours ago, PaladinX said:
Hello,
since the sound patch, the Twin Otter is taken out of my Hangar and goes for some flights. But i have a strange issue, im not sure if i do something wrong.
- ALT is set to 9000 ft. The KAP140 and the SET ALTITUDE DISPLAY both show the 9000 ft.
- I take off manually, go on my course, then i activate the AP (no matter if on the KAP140 or on my Honeycomb Bravo, tried both)
--> The SET ALTITUDE DISPLAY changes immediately to 1000 ft above my current altitude. Every 100 fts, it goes one step up (all the time) and beeps like hell because i reach the next 100 fts altitude. I can not change the SET ALTITUDE when i turn the knob.
So the SET ALTITUDE changes together with my flying altitude every 100 fts, without any input, the KAP140 value stays all the time at the correct 9000 ft.
Any ideas?
I don't see this behaviour. Can we assume you aren't running any AP mods, such as the FS2020-USER-TESTER KAP140 mod? From your description of the continued incrementing I would wonder if the rotary dial on your Bravo quadrant is sending uncommanded pulses. (My Leo Bodnar rotaries sometimes do that for reasons I don't understand.)
-
3 hours ago, meierzwo said:
On the Pilots Side, the Altimeter Gauge lost its needles. Copilots Side is okay.
SU11, latest Nvidea Game Ready Drivers.
That's normal, it's a different type of gauge.
-
1
-
-
9 hours ago, amahran said:
But does changing the altitude selection in the KAP140 drive the Collins PRE-80 to change the altitude shown in the display window? I wouldn't think so; I believe that window is only driven by the selector knob on the PRE-80 unit.
As far as I recall, the PRE-80's cannot be actuated by any integrated avionics systems, so changing the altitude selector on the KAP140 shouldn't drive the altitude window to change in the Collins unit.
Yes, it does. No point trying to make sense of it, this is a fictional mashup.
-
1
-
-
If you're trying to figure out how to switch off the dark theme after the recent forum update, it's at the bottom of the screen under 'theme'. Phew
-
The KAP140 has its own alert functionality, which is what the Collins one is slaved to. It's slaved both ways, so you can preselect the altitude on the upper dial too if you want. The alert light isn't implemented, though. I suppose you could have two independent alerters, but it doesn't seem to make much sense.
-
2 hours ago, Abrams Tank said:
Hi. Thanks for your help! I tried it your way, by pushing ALT and changing it to VS speed mode, before hitting the vertical speed down arrow, in Step 5. When I did this, the first time I clicked on the vertical speed down arrow, the vertical speed dropped very mildly (to -100 feet per minute or about -0.1 on the VSI) and the the Twin Otter nosed down ever so lightly, which was the behavior I expected. This is much better than the behavior than before, when the Twin Otter nosed down severely, hitting -4 on the VSI!
Yes, that sounds right. It will dial in 100-fpm increments with each button press!
-
1
-
1
-
-
7 hours ago, RobbieAC said:
I set both VOR1 and VOR2 to the same frequency, and the OBS to the same values. VOR1 shows I'd correctly going towards the VOR station, and the right deflection. VOR2, however, shows I'm going *away* from the station. Am I missing something? Isn't this a bit odd?
I'm not at the PC but VOR1 is the HSI, VOR2 is a whatever-you-call-that-instrument. The OBI will centre in two different (opposite) settings of the instrument, one with a TO indication and one with a FROM indication. If you know this, then I guess that isn't the problem
-
39 minutes ago, Abrams Tank said:
- Now I am getting close to my destination. So I turn the blue altitude knob on the “SET ALTITUDE” to 1500 feet.
- When I click the up arrow Vertical Speed button this time, the Twin Otter will nose down severely, jumping to as much -4 on the VSI, or even beyond -4 on the VSI.
I'm not 100% sure what you are seeing here, but those two steps suggest you are expecting the wrong behaviour. (I assume you mean the DOWN arrow button in step 5, by the way.) If you are on ALT mode, the up/down buttons don't set vertical speed, they nudge the altitude up or down in small increments. Well that's what they're supposed to do, but they don't work according to the manual. I don't think that's a factor here. What you should do is to preselect the new altitude (your step 4), then press ALT to flip from ALT mode to VS mode, then press the down button a few times to set your VS.
That said, I have found the VS mode a bit buggy. I did some bits of SPAD.neXt programming to make it work better. I have made a video about this, which you can find on my YT channel by clicking the link in my signature. (I posted a link here before but it was removed.) Maybe that will help.
-
1
-
1
-
3 hours ago, haseen said:
Which autopilot is more authentic for twin otter? The p3d's or the msfs 2020's?
That's not really a fair question, they are just different autopilots. The MSFS one has the old AP106 panel slaved to the KAP140, which I doubt is found in real life.
-
3 hours ago, Enright said:
the change in pitch (the pitch of the sound, not the propeller pitch) is not smoothly proportional to throttle input. There's a tool to help with adjusting pitch and blending samples here:
But are you sure it is supposed to be? It would be helpful if you could post a video showing what you are doing and how it sounds, and then saying what you are expecting with reference to that video. Taken at face value, and as far as I understand these things, your expectation that the pitch changes with throttle will only be true at very low power settings (idle to the governed range). Ones the props are spinning within the governed range, they are running at constant speed, so the pitch doesn't change with the power setting. There has been talk of missing turbine noise mixed in there, but that's a different thing.
-
1
-
-
3 hours ago, echo_oscar said:
It’s very difficult to fly a stable approach with the latest patch.
But it's difficult to land STOL without it. I'm all for tweaking, though.
-
16 minutes ago, Mathijs Kok said:
Is very much okay.
OK, I edited to attach the list.
-
2
-
-
I found how to see the list in SPAD.neXt. You just need to show the data list (go through the motions of setting an action to change a data value) and filter the list by 'DHC6'. I see 100+ Lvars, as in the attched image. (Sorry, I couldn't see how to capture it as text.) I said it was 297 variables before, but I think that's too many. SPAD's search functions don't always seem to do what I expect
-
The "!" was surely not the reason for the problem.
Just thought I'd follow up on this as I have had the same problem for many months, and yesterday I happened across this thread in looking for a solution. Well, the solution was the same - i.e. removing the '!' from the folder name made everything work again.
I have one other bit of information, which is that I am pretty sure my WinchX stopped working right after I installed Luciano Napolitano's Key2Mouse (www.wideview.it). I don't know why this should be, but I have two further observations about Key2Mouse. First, the installer did something very nasty that corrupted my mouse pointer which, if I recmember correctly, fixed itself when I rebooted Windows. And second, Key2Mouse appears to be a very old utility, evidently designed for 16-bit Windows and which installs some very old custom controls and stuff. It would not be surprising if it is barely, or not quite, compatible with modern 32-bit and 64-bit versions of Windows. Although having said that, it may be the installer that's at fault, as the program did work for me once it was installed.
-
I did check my fs options and it's say 1920x1080x32 - this are any other places to chance that option?
Dunno, sorry, it was just a guess. It might still only show up at night, though, assuming the lighting is different. You might also check the TEXTURE_MAX_LOAD parameter in fsx.cfg. Mine recently set itself (or something set it) to 64 instead of the default 1024, which made lots of things look odd. Doubtful whether it affects 2D panels, but you never know.
-
Suddenly my night texture is ugly, can anyone help me? is it a problem in fs9.cfg? or is my graphic card?
You haven't accidentally switched to a 16-bit colour mode?
-
Nick, Thank You. Maybe one day I will see some of Your screenshots of this?
Check out the Aerosoft official screenshots, they look suspiciously like Nick's work!
-
"....axis roll..."
You are right again. It is bug of dynamics which I fixed already and will put in patch.
Is this patch available yet? I've seen at least one reference to someone having installed v1.1, but I can't see any announcement or download link.
New sound set test
in Model, Animations, Sounds and Manuals
Posted
Well okay, I can hear small differences in the examples you give, but I can't say if it's right or wrong. I can see that the change of tone in the first vid is a bit faster, but it matches the rate at which the prop RPM spins up. And it's not that dissimilar to what you see in this real world video at 1:26. Maybe it's just a reflection of how fast you add the power.