praga
-
Content Count
23 -
Donations
$0.00 -
Joined
-
Last visited
Posts posted by praga
-
-
LINDA 2.6.6 and Q400 module 2.2 have been released on the Download sub-forum.
Thank you!
-
Linda: 2.6.4
Q400 module: 1.3
FSUIPC4: 4.948
FS2Crew: 1.3
Befor purchase of MCP2B No problems
After purcase sound problems.
With MCP2B and commented out body of function Timer () NO PROBLEMS.
-
Hi Mark and others
I have got FS2Crew Q400 v1.3 set up with P3Dv2.5 and the LINDA module 1.3. I can confirm the intermittent/broken/curtailed/missing voice responses affecting the FO, Ground and Cabin Crew responses. I have looked at the various comments on this thread and tried the suggestions. None works to solve the problem or to point me towards the cause of the problem. Like you I have no idea of the source of the problem or why LINDA may be interfering with FS2Crew. LINDA only interfaces with Q400 via the SDK. It should not affect the sound stream from FS2Crew. I have not experienced any issues of this type with the Airbus FS2Crew. I am therefore totally stumped and can not, at this time, offer any way forward for you. When I have the odd evening free I will have a further look but please do not hold your breath. Sorry!
Did not helped you commenting out body of
function Timer ()
?
It seems to me it is more Majestic SDK problem, unless LINDA is using SDK wrongly.
-
Great, I find work around!
Comment out body of function Timer () in Modules\linda\aircrafts\Majestic Dash 8 Q-400\actions.lua
There is something fundamentally wrong with the reading values from Q400. (May not be Lindas fault)
If I comment out everything except
ipc.writeLvar("MJC_VAR_READ_CODE", 31281)
it still mutes the briefing for some time.
-
No unfortunately I did not identified problem. Gregg_Seipp suggested to execute function ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50) in InitVars function. I did that and it gives me error. That's all I wanted to say by my post.
And The problem start exists once MCP2 is initialized, which occurs after this function is executed.
-
As a workaround,
ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50)
in the InitVars() function as a test
[E] *** LUA Error: ...es\linda/aircrafts/Majestic Dash 8 Q-400/actions.lua:30: attempt to call field 'writeLVar' (a nil value)
function InitVars () -- uncomment to disable display -- AutopilotDisplayBlocked () AutoDisplay = false ipc.sleep(100) --Q400_YOKE_VISIBILITY_off () MJCD8_VS_Show () MJCD8_ALT_Show () MJCD8_HDG_Show () MJCD8_SPD_Show () ExtPwrTxt = 0 ipc.set("CautAdvTest", 0) ipc.sleep(100) OnGround = ipc.readUW("0366") ipc.writeLVar("L:RADIO1_SERV_INT_KNOB", 50) end
-
Hi Mick , Thanks for your reply . So i understand that i'm not alone !! I Hope someone can solve this issue because it's really bad to fly with one of two software's disabled
Fly safe
Evangelos
I also confirm this.
Step to reproduce:
Start Linda with MCP combo disabled.
Star fs2crew.
Start briefing.
Everything should work OK.
While briefing is still playing, enable MCP Combo in Linda and reload Lua engine. Periodic mute periods will manifest during rest of the briefing.
It must be in the code periodically checking MCP combo.
Is there source code for Linda available?
-
Just click on RIGHT button in FPL page. Then you can set altitude and how many miles before that point you want to be at that altitude.
-
Is there way to step through filght plan leg by leg? Video shows stepping page by page, but espetialy arrival, if wrongly entered can give me trouble.
Thanks
-
Did you tried to complete reinstall?
-
Tried today version 1014, I confirm I can reproduce WRONG behavior. It is bug introduced in 1014. Please report. Add me as cc in the report.
Thank you!
-
Tried today version 1014, I confirm I can reproduce WRONG behaviour. It is bug introduced in 1014. Please report. Add me as cc in the report.
Thank you!
Edit: Updating database to 1502 does not fixes the issue for me.
-
Version 1013, Airport LKPR works as expected.
-
I would bet it is plane out of trim. This plane needs to be retrimmed on speed or power change.
-
Condition leveller - fuel off
(Power leveller - DISC) - not sure if needed but should be in that position anyway.
A/F Select - ON
-
We modeled it the way they do it at this one particular airline.
Everyone's different... million ways to skin a cat.
May I ask, was it USA based airline?
I am asking because TA (Transition Altitude) can be as low as a few thousand feet in Europe. Altimeter settings is in FS2Crew part of Descent checklist to the line. Way before one will get clearance to descent to or below TA (e.g. 5000 ft).
-
Would it be possible to add feature to skip checklist completely?
E.g. When training for landing, I do slew aircraft to/before finals.
-
1) Check requirements
2) Set up speech recognition http://www.support.fs2crew.com/help/manuals/#pageid=speech_recognition_setup2
3.1) Open WordPad
3.2) Start voice recognition
3.3) Read all red commands (and violet examples) from http://www.support.fs2crew.com/help/manuals/#pageid=normal_checklist4
3.4) Check recognition rate. Train recognition until success rate is high enough you can rely on it.
-
Where I can find fs2crew licence?
Am I allowed to resell it?
-
Only solution that worked for me is to set location to US and language to English/US.
"Great" solution.
Is there possibility to use 3rd party speech recognition?
-
I would also humble ask to add multiple shift states. Or button combinations as in FSUIPC. Thank you.
-
When I try to run speech recognition after setting up speech recognition language to English- US I get error:
The recognizer language must match the language of the user interface. Please change the recognizer language in the Speech Recognition control panel under Advanced Options
[Feature request]Gear pins
in FS2CREW: MAJESTIC DASH8 Q400
Posted
During before start checklist my FO confirms that gears pins were stowed.
But in fight I found out he forgot to stow it. My fault of not double checking.
Is there settings that he will stow it for me?
I found FMS to be immersion breaking.
Thank you!