ODBC Error
-
- Posts: 32
- Joined: Sat Sep 20, 2014 2:25 am
- Location: Australia
ODBC Error
I'm getting an odbcji32.dll unable to load error when opening a flight with the aircraft followed by "Error connecting to database etc.. & the SQL_handle_env failed (IM004)" message. I then get a "session not connected message" when trying to program a flight plan or input the current airport location.
I've installed the aircraft several times & as administrator, completely removed MVAMS between installs & still get this error every time.
Any ideas?
I've installed the aircraft several times & as administrator, completely removed MVAMS between installs & still get this error every time.
Any ideas?
- doodlebug
- Posts: 1642
- Joined: Sun Feb 19, 2017 2:49 pm
- Location: LYX>YUL
Re: ODBC Error
Does the plane work otherwise?
-
- Posts: 32
- Joined: Sat Sep 20, 2014 2:25 am
- Location: Australia
Re: ODBC Error
Yes from what I can see. Have been able to start it OK & fly a circuit no problem although as I reported elsewhere previously the quadrant levers are still not animated to coordinate with my hardware.
Am downloading the new beta now & will see how it goes.
Am downloading the new beta now & will see how it goes.
-
- Posts: 157
- Joined: Sat May 09, 2015 2:33 am
Re: ODBC Error
I am not sure what you mean. Are you talking the power levers, propeller levers, condition levers or all of the above? What hardware are you using?
Are you using FSUIPC to define the axis? If so have you tried removing those definitions?
I have two Saitek power quads, 6 separate axis, and I have no problems. The condition levers will stick at the low idle position and this is on purpose so it is harder to mistakenly shut off an engine when setting low idle.
-
- Posts: 32
- Joined: Sat Sep 20, 2014 2:25 am
- Location: Australia
Re: ODBC Error
Yes they are the levers I am referring to.
I have a PFC throttle quadrant which I use FSUIPC to program & although they are working correctly & the aircraft is responding to the inputs from them correctly the levers in the VC do not move correspondingly. They remain visually fixed in one spot & they only move when I drag them with the mouse. I had raised this with the alpha version last year & was told that the movement had not yet been programmed. I thought something like that would have been done for the beta. I assume this is still to be implemented however thought I'd raise it just in case.
Re assigned the No.1 condition lever & still no difference. Can start & shut down the engine using my hardware however the lever doesn't move in the VC.
I have installed the latest beta & both this & the ODBC error are still present.
I have a PFC throttle quadrant which I use FSUIPC to program & although they are working correctly & the aircraft is responding to the inputs from them correctly the levers in the VC do not move correspondingly. They remain visually fixed in one spot & they only move when I drag them with the mouse. I had raised this with the alpha version last year & was told that the movement had not yet been programmed. I thought something like that would have been done for the beta. I assume this is still to be implemented however thought I'd raise it just in case.
Re assigned the No.1 condition lever & still no difference. Can start & shut down the engine using my hardware however the lever doesn't move in the VC.
I have installed the latest beta & both this & the ODBC error are still present.
Last edited by Rossco on Sun Sep 22, 2019 3:36 pm, edited 1 time in total.
-
- Posts: 157
- Joined: Sat May 09, 2015 2:33 am
Re: ODBC Error
Can you assign the axis inside of P3D with that controller? I recommend that to begin with.
-
- Posts: 32
- Joined: Sat Sep 20, 2014 2:25 am
- Location: Australia
Re: ODBC Error
OK have got them working with a bizarre twist.
I usually have the controllers turned off in the sim & only use FSUIPC to minimize conflicts. With this aircraft I have found that I have to have the controllers turned on in P3D for them to work visually.
This is the only aircraft I have that is showing this behavior. Late here so will investigate this further tomorrow & see what I can do to program the sim controllers to ensure I don't have a conflict.
I usually have the controllers turned off in the sim & only use FSUIPC to minimize conflicts. With this aircraft I have found that I have to have the controllers turned on in P3D for them to work visually.
This is the only aircraft I have that is showing this behavior. Late here so will investigate this further tomorrow & see what I can do to program the sim controllers to ensure I don't have a conflict.
-
- Posts: 32
- Joined: Sat Sep 20, 2014 2:25 am
- Location: Australia
Re: ODBC Error
Well have found as pointed out last night the only way I can get the levers to move in sim is by allocating them through P3D.
And although calibrated both with P3D & FSUIPC the throttles still do not visually move through their full range & only travel from full down to above flight idle. I can get the aircraft engines to get to ground idle & reverse using my hardware although this is not showing visually in the sim. Props & condition levers do travel their full length.
This is the only aircraft that I have that does not show moving levers when only programmed through FSUIPC & controls deactivated in the sim. This includes your own DHC3. Looks like the programming in the KA is unique for some reason?
And although calibrated both with P3D & FSUIPC the throttles still do not visually move through their full range & only travel from full down to above flight idle. I can get the aircraft engines to get to ground idle & reverse using my hardware although this is not showing visually in the sim. Props & condition levers do travel their full length.
This is the only aircraft that I have that does not show moving levers when only programmed through FSUIPC & controls deactivated in the sim. This includes your own DHC3. Looks like the programming in the KA is unique for some reason?
-
- Posts: 32
- Joined: Sat Sep 20, 2014 2:25 am
- Location: Australia
Re: ODBC Error
Have spent some more time trying to sort out issues I'm having with the throttles/props.
1. Levers do not move if not activated through P3D
2. When activated I'm unable to set idle through calibration. Always idles high & condition levers have no effect.
3. Using FSUIPC only I can calibrate to get prop showing 1050rpm @ idle & my condition levers operate low idle, high idle OK. (Not sure what they should be at true low idle yet).
4. Using FSUIPC only I'm unable to select prop setting & have it stay there. RPM will return to wherever the prop levers are positioned in the VC. So if they are at full fine then rpm will always return to 1700rpm after initially changing with my hardware. VC position is overriding my hardware!
5. Using controls activated in P3D prop levers will move & remain at the hardware setting. However am unable to get throttles to idle on the ground so I'm stymied both ways at the moment. For idle on the ground I need P3D controls off & for in flight prop settings need it on!
Hope you can follow this.
1. Levers do not move if not activated through P3D
2. When activated I'm unable to set idle through calibration. Always idles high & condition levers have no effect.
3. Using FSUIPC only I can calibrate to get prop showing 1050rpm @ idle & my condition levers operate low idle, high idle OK. (Not sure what they should be at true low idle yet).
4. Using FSUIPC only I'm unable to select prop setting & have it stay there. RPM will return to wherever the prop levers are positioned in the VC. So if they are at full fine then rpm will always return to 1700rpm after initially changing with my hardware. VC position is overriding my hardware!
5. Using controls activated in P3D prop levers will move & remain at the hardware setting. However am unable to get throttles to idle on the ground so I'm stymied both ways at the moment. For idle on the ground I need P3D controls off & for in flight prop settings need it on!
Hope you can follow this.
-
- Posts: 157
- Joined: Sat May 09, 2015 2:33 am
Re: ODBC Error
For #1 a developer will have to answer to the way.
#2. What do you consider high? At LOW IDLE the N1 speed is 62% and at HIGH IDLE the N1 speed is 70%. My testing has shown the engines to be right in the ballpark of these numbers considering the actual airplane uses push-pull cables to a pneumatic fuel control unit some slop is expected.
#3. The governing range of the primary governor is 1450 to 1700 RPM. You should NOT be able to tune your controls to adjust propeller to 1050 RPM. That is a matter of the speed of the output shaft (Condition Levers to LOW IDLE and Power Levers at Flight Idle) and the ground low pitch stop. As long as the propellers are outside of the avoid range call them good. If they are in the avoid range then push up the condition levers until they are out. Normally we would write this up and have maintenance adjust the idle screw on the FCU.
#4. You have to set your controls through P3D. If you try to adjust to FSUIPC then, you see what you are getting.
#5. Again set and calibrate your controls in P3D. That will give the best performance. I understand that some want a reverse range, but that is undoable. You can set a reverse range using a lua call through FSUIPC.
#2. What do you consider high? At LOW IDLE the N1 speed is 62% and at HIGH IDLE the N1 speed is 70%. My testing has shown the engines to be right in the ballpark of these numbers considering the actual airplane uses push-pull cables to a pneumatic fuel control unit some slop is expected.
#3. The governing range of the primary governor is 1450 to 1700 RPM. You should NOT be able to tune your controls to adjust propeller to 1050 RPM. That is a matter of the speed of the output shaft (Condition Levers to LOW IDLE and Power Levers at Flight Idle) and the ground low pitch stop. As long as the propellers are outside of the avoid range call them good. If they are in the avoid range then push up the condition levers until they are out. Normally we would write this up and have maintenance adjust the idle screw on the FCU.
#4. You have to set your controls through P3D. If you try to adjust to FSUIPC then, you see what you are getting.
#5. Again set and calibrate your controls in P3D. That will give the best performance. I understand that some want a reverse range, but that is undoable. You can set a reverse range using a lua call through FSUIPC.
-
- Posts: 47
- Joined: Sat Jun 16, 2012 12:55 am
Re: ODBC Error
I’m having similar issues as the OP using my virtual fly TQ6+ quadrant. Hopefully we’ll be able to se the throttle quadrant controls through FSUIPC in the future since that’s how all of my other aircraft are set up and I don’t use any P3D control assignments.
Also with the TQ6 the reverse/feather range etc are part of the axis so it would be good to be able to take advantage of that.
Also with the TQ6 the reverse/feather range etc are part of the axis so it would be good to be able to take advantage of that.
- doodlebug
- Posts: 1642
- Joined: Sun Feb 19, 2017 2:49 pm
- Location: LYX>YUL
Re: ODBC Error
Rossco - I have asked our team to look at this - in the meantime would you mind adding your system specs (including windows version) to your signature - it will help in their diagnostic efforts
-
- Posts: 32
- Joined: Sat Sep 20, 2014 2:25 am
- Location: Australia
Re: ODBC Error
Hi Oisin,
Thanks for this.
Have added system specs & OS to my Signature as requested.
Thanks for this.
Have added system specs & OS to my Signature as requested.
-
- Posts: 658
- Joined: Sun May 11, 2014 11:49 am
Re: ODBC Error
Hi,
Engine control levers' operation is custom controlled based on P3D related events, as we cannot depend on external addons some users might not own.
However, it is possible to configure all levers through FSUIPC without the need to have them mapped in P3D.
Please follow this example for all of your levers:
Available events are:
AXIS THROTTLE SET
AXIS THROTTLE 1 SET
AXIS THROTTLE 2 SET
AXIS PROPELLER SET
AXIS PROPELLER 1 SET
AXIS PROPELLER 2 SET
AXIS MIXTURE SET
AXIS MIXTURE 1 SET
AXIS MIXTURE 2 SET
Beta and reverse power will be configurable in the release version.
Tomas
-
- Posts: 47
- Joined: Sat Jun 16, 2012 12:55 am
Re: ODBC Error
Thanks Tomas, I was just about to make a post about the challenges of not being able to map beta and reverse to a throttle axis so I'm glad to hear it will be included.