Hello Manuel,
You need to right click then "save position" before restarting the software.
JL
Printable View
Hello Manuel,
You need to right click then "save position" before restarting the software.
JL
OK...i go try your suggestion!
Thanks
I have just installed the latest version on my Airbus sim, to do some testing. First I have to say this is the most realistic software I have seen and the method of installing Side-sticks, flaps etc., is the best I have seen in simplicity. It is a pity some other developers could not look into this way of doing things !!
Ok there are some problems, but I have no doubt these will be rectified, simply because we are all using different setups and hardware. Makes it hard on Jean Luc. I also have to get to know how it all operates !!
I have not installed all the computers yet, as I need to fix any problems on the main ones first.
I am using FSUIPC.ini to start the Starter program on the FSX computer. All the other computers are using WideServant.ini to start and close the Starter Programs.
Here is a list of computers that I am using :
Computer 1. Running FSX + FCU+FMGS SERVER+FBW : i720 @ 4.0 ghz.6g ram. XP64
Computer 2 Running EWD+SD+OVHD + Sounds+ InterFaceIT : 2.6 Ghz, 4G ram. XP64.
Computer 3 Running Captain ND +PFD: 2.7 Ghz, 2 G ram, XP64.
Computer 4 Running MCDU : 2.5 Ghz. 1 G ram, XP.
Here are a couple of problems that I have already listed on the bug tracking site, for others to compare their findings with mine.
Switches on the Overhead not working correctly withn InterFaceIT . The On/Off switches for the lights, seatbelts, no smoking etc., do not switch on/off after they are switched on.
All the momentary ones are ok,which is all of the overhead Korries.
Axis on BUO836X Not availible. All axis on the BUO836X are working perfectly on throttles, Flaps, etc. but the last one which is DIAL pot. will not come up at all on the FMGS_Config.exe. It shows as working ok in the Microsoft game controller as working ok. Need to use it on the Spd Brk.
Lock up On approach and AP on and at 1500 ft I get Alpha Floor and most times it will not be recoverable. The nose come up for no apparent reason and of course the speed comes back and then lock-up. Not doing ILS, just normal approach. Have not installed the Master and Caution Warning Switches yet.
Hope this information will help Jean Luc. I was in Nice during September but unfortunately had very little time, othewise would have been nice to meet you.
Kind regards............Brian W.
JL hold off on the problem with the lockup on approach. Doing some more testing at the moment and I suspect a problem maybe in the MCDU. Will report back after more thorough testing.
Regards...........Brian W.
Hello Brian,
I have similar problems with the taxi light, seatbelt-and nosmoking -toggle in conection with InterfaceITAPI.
I have been also reported this to JL. I think he will take care of it but still do a couple things with higher
priority. I can not confirm Problems with the BUO836X and FMGS_Config. All the axes and dimming of the display works with it.
Kind regards
Hi,
I'd need more info on this "DIAL pot", I'm not sure how this is interpreted by windows afterwards? if you can point me to the bodnar documentation that would help as well.
Cheers,
JL
Features
•Push-in terminals for all connections
No more soldering or screwdriving. Push in to connect. Press tab and pull out to disconnect.
•32 truly independent digital inputs for buttons and switches
No matrix, no diodes, no daisy-chaining. And yes, each input has its own two terminals (GND can be shared between inputs if necessary.)
•Support for up to 16 rotary encoders
A pair of digital inputs can be connected to rotary encoder. All main types supported (1, 2 and 4 pulses per detent)
•8 analog inputs with true 12-bit resolution and independent wiring
4096 steps of resolution. Even 1/4 of this range is still 1024 steps!
To support true 12-bit performance each analog inputs has independent set of +5v and GND terminals, oversampling and sophisticated signal filtering
•8-direction POV hat switch
•Compact outline of 123x52mm (4.85"x2.05")
With 93 wire terminals onboard it is only 50% bigger than a credit card
•Natively supported by Windows Vista/XP/2000/Me/98, Mac OS X and Linux
True Plug-and-play at its best.
http://www.leobodnar.com/
That is about all the information availible. Only 7 analog inputs are detected by FMGS. Not the 8th.
Cheers.................Brian W.
Hello,
Ok thanks I will investigate. The 8th axis should be read, but I admit I have no means to test that. I will look if there is any obvious bug first.
Cheers,
JL
Hi to all:
After a few tests in FBW, I still can not yet the best performance, specially when in landing, because we need a faster response in the sidestick for left and for right, and i can't this faster response, after try a few settings...
Can someone share the settings in FBW and the configuration of sidestick?
Thanks
Manuel Sacramento
I think is good. The model IFDG/PA/other in full configuration -> aileron deflection must be large.
See here:
http://www.youtube.com/watch?v=LRilx-a3Hro
http://www.youtube.com/watch?v=oWOwIYcrSJQ
Could be large the deflection in aileron, mas you need feel the aircraft, and control it, and if this movements have a big large deflection you can't control it very well...
Can you share is your settings in FBW ?
Thanks
I use standard settings FMGS.
I changed ProjectAirbus model.
The changes are large.
Now JeeHell check it.
I changed:
- N1 (according to data from a real simulator)
- Thrust (plane does not move by itself on Idle)
- Trim (about 2.5UP in full configuration during approach)
- Elevator (there is no horizontal oscillation and now plane captures GS in each configuration and speed).
- Min_ailerons_for_spoilerons - (This settings assures that the SD will show the aileron arrow in the right time).
- and other less important things.
I'm working on it yet.
See the videos on my channel:
http://www.youtube.com/user/zenek900?feature=mhee
Hi:
Thanks for share your settings and tests...THis mean soon we will have this settings for improve the realism right?
I don't know.
IFDG or PA models also are good.
JeeHell decide which model would be good to FMGS.
I used a model of PA. I compared to IFDG (native to FMGS). I added improvements. I like the effect.
That's all ...
Hello Brian, and others who use leobodnar's card, or cards with more than 6 analog inputs:
It seems the way I look up for joystick information is a bit outdated by nowadays standards, and I'm currently limited to 6 analog inputs (X,Y,Z, rotX,rotY,rotZ). I've been looking at how to add the remaining two, but it's quite a lot of work and time I don't really have right now on this topic. I will do my best, but will not come in the next weeks anyway, sorry for the inconvenience...
Cheers,
JL
Hi JL
Many thanks for this great piece of software.
While configuring, I noted the option for the MCDU to move Lines 1-6. Is there a way to move (up/down) the line for the scratch pad? The scratch pad line overlaps with line 6, which might be an issue of the font not working properly (not sure).
Thanks
Jamie
Hello Jamie,
As written in the User Guide, you have to use up/down arrows to move the scratchpad line. And left/right to move the title line.
Regards,
JL
Is there any possibility to make this work with A330 model?
-Jon
Hi
Thank you for the advice on the scratchpad; I had overlooked that in the guide, apologies.
I am struggling with another thing, the backlighting of the FDS XPNDR (the number keys are not backlight) and the FDS Comms (same problem). Is this something which is yet to be implemented or is there a function to activate the backlighting? It works quite well for the FDS FCU.
On another point. When configuring the tiller, I can see the rudder (in F/CTL) moving left / right. However, the rudder (nose gear) will stay left or right and not move back to a neutral position. It feels, as if the nose wheel sticks at the commanded input, making it very difficult to maneuver. Could this be an issue of the neutral zone?
Thanks a lot
Jamie
Hello,
Jon, you need to get in touch with Chris from dalpi project, his nickname here is kikigey I think.
Jamie: I'll try to look at the XPDR/COMMs backlighting, however the documentation is not complete on these modules and since I don't own them it's hard to make sure everything works correctly. Concerning the rudder not going back to neutral, yes it can come from your input axis neutral zone.
Cheers,
JL
Hi JL
Thanks a lot. The rudder / tiller shows "weird" behavior. I substantially increased the neutral zone. It seems that the rudder moves much too quickly and does not automatically revert back to neutral, but sticks. I increased the neutral zone to 2500. Is there a way to configure / calibrate joystick axes more granularly?
Update: I investigated a bit further. I think one issue is that the tiller moves the rudder, e.g. to the right. If the tiller is released to zero, the rudder deflection will remain. In order to get to neutral, opposite rudder input is required, i.e. deflection to the left. Shouldn't the rudder revert to neutral once the tiller is released to neutral?
Thanks for checking the backlighting.
Best
Jamie
Hello Jamie,
In current release version, rudder/auto cooridnation is not yet perfect, this will be much improved in next version.
I suggest you turn on FS native auto-rudder, it will be better for now.
Cheers,
JL
Hi JL
Many thanks for your quick response! I have made some further tests and resolved the rudder/tiller issue. Unfortunately, this led to some further questions ;-)
Thank you very much and best regards
Jamie
Rudder Trim
In the IITcreator, I am unable to find the references for the switches Rudder Trim Left / Rudder Trim Right / Rudder Trim Reset. Is there another way to configure these switches?
PS: I found that when configuring in the FMGS only the tiller, without configuring an axis for the rudder, the tiller behaves incorrectly (not moving back to neutral). What solved the problem for me is configuring tiller and rudder on the same axis.
Instable Autoflight
I am using the FSX model provided in your suite. When switching on Autoflight, the plane behaves unstable (e.g. the elevator begins to oscillate fast) and the AP will not follow the flight plan because the autopilot, at some point, disengages. In almost all instances, the plane will stall.
I checked the aircraft.cfg provided in your package against the the AdvancedUsersSetup guide. There are some deviations (e.g. for the flap speeds and other flap related data as well as the number of tank selectors); I think these should not be relevant.
In the AP/FBW, the only selectable option is PA Airbus though.
Do you have a suggestion what could be wrong here?
System Info
- FSX
- FSUIPC 4.7x (which I understand should now be compatible, correct?)
- Model: iFDG FSX as provided in the installer package
Positioning of STBY Instruments Lost
I fail to save the position of the Standby Instruments (namely ISIS and DDRMI). There seems to be no "save position" context menu for these instruments?
Hello,
Rudder trim: not yet implemented. I will look at the rudder/tillee axis issue.
Autoflight: if you have the correct acft installed, then the problem may come from the FPS you get in FS, they should not go below 20/25, or the AP behaves incorrectly.
STBY instruments: if I remember correctly, their position/size is stored when you manually close the STBY main window. Using the starter to close all soft prevents the storing of the position.
Cheers,
JL
Hi JL,
I have a small issue regarding the ILS. Sometimes I have a small lateral offset to the runway. The AC is still aligned with the runway but way off center line. The MLG is close to be off the runway during touchdown. example: ILS approach EDDV - 9R. Is it related to the new nav data? any clue?
and do you plan to add the estimated flyover time for each waypoint in the mdcu? I guess such a feature needs a more stable estimated arrival time to your destination before you can start to work on the time of each waypoint... ?? so many questions :)
Thanks for this nice software!!! :)
Cheers,
Rob
Hi JL
Thanks a lot.
Re the Autoflight: I don't think that FPS should be of an issue on that specific machine. I will check and report back.
-- Do you recommend to limit FPS in the FSX settings?
-- Is there an option to force the software to not use Core 0 (which seems to be most used by FSX), i.e. force the A320 Suite to only use Core 1 and higher?
Thanks
Jamie
Hi there,
I also use the brilliant FMGS beta 24 Software by Jeehell. I am using FSX, FSUIPC 4.756 and everything is running smooth and very well.
But yesterday I started my first Online Leg (IVAO) with the FMGS b24, I saw the other aircrafts on the screen during taxi out etc but I did not see the traffic on my ND.
Off course, at the MCDU / TCAS Options / I set MODE C, TCAS MODE TA/RA and TCAS TFC to ALL. But nothing appeared on my ND during my flight, however there were a couple of flights which had should be appeared on the ND!
And it doens't matter if I am using just one system or using three computers on a network. In both setups there is no Traffic on my TCAS/ND!
Because I am using FSX as a Newbie (I just changed from FS9 to FSX), maybe I have to do some settings I don't know.
Do I have to set something special in the FSUIPC?? Here it says: "Limit TCAS Strange = 40" and "Set TCAS id string from = Flight" ; which were the default values!
In fact, when I was using FS9 and FMGS Software I did have TCAS Traffic on my ND !!
Thx a lot for your kind assistance in advance !
Best regards
Joerg
Hi Joerg,
TCAS has been deactivated since it didnt work as it should. JL mentioned that earlier. I guess we have to wait on a new version in which it will be implemented again. So it is not related to any problem with your system.
Cheers,
Rob
Hey Rob,
thx a lot for this quick answer! I didn't notice that Jean-Luc deactivated the TCAS: Good to know that this has not to do with my setup anyway.
Nice weekend to all
Joerg
Hello,
Rob:
-ILS offset: is the localizer signal centered on the PFD and ND? if yes then either the navdata is wrong or that specific ILS really has a lateral offset on the approach. Do you have the charts to confirm that?
-flyover time: it is planned, but as you said I need first a better VNAV calculation. I don't know when it will be better, it's a LOT of work.
Jamie:
-I personnally limit the FPS at 30 fps. It frees CPU for the other software and I recommend that.
-It is really a BAD idea to allocate specific cores to software, in any way. First, some of my programs are multi threaded and can make use of several cores at te same time. Secondly, windows is in fact very good at dispatching cores to software when they need it.
Joerg: yes the TCAS is not functionnal for now. I will try to get it back in next version, but not guarantee on that...
Cheers,
JL
Hi JL
Thanks a lot.
Setting a 30 FPS lock helped to improve the Autoflight behavior enormously. Thanks.
What I noted is that under certain circumstances (I am not yet able to explain which, but it happened multiple times), it is not possible to engage managed speed and/or managed heading. AP1 / AP2 will activate just fine, but the FCU, upon pressing HDG or SPEED, will not change to the ---.
If I find out what the issue is, I will post a follow-up.
Thanks again for your work with this; much appreciated.
Jamie
hallo.
wo kann ich den A320 FMGS beta 24 runterladen finde nur liinks die niicht mehr aktiv sind:-(.
bitte helft mir danke.
liebe grüße
adrian
Hello,
Sorry I do not speak German...
JL
The current link is from post number #38Quote:
Originally Posted by adipdm
http://www.jeehell.cockpitpassion.fr/A320FMGS_B24.1.exe
Hallo Fritz.
THX
Liebe grüße
adi
Question @ all
Is it true that Nvidia video cards work better with jeehell's software than AMD cards? Can somebody confirm this information?
Thanks
René
I've used GForce and Radeon graphics cards. No problems with A320 FMGS.Quote:
Originally Posted by flapsdown
hello,
The only people who complained about issues that could be related to their graphic card, used an ATI card. However, I believe most ATI cards with up to date drivers are perfectly fine.
Cheers,
JL
Thanks both of you! It was hard to believe this "rumour" but as I intend to assemble a new PC I'm interested in this question.
Greets
René
Hi JL,
the forum became pretty calm... I guess we are all waiting on a new release :) Any rough estimate for V25? Or its new features????
However, here just a little bug report regarding DU dimming: When PFD an ND are in XFR the dimming is not cross referenced. Both DU's are in their original bright state.
I assume ND should use the input from PFD and vice versa when in XFR.
Best regards and a BIG Thank you,
Rob