Jump to content

mmerelles

Members
  • Posts

    1,190
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by mmerelles

  1. Because this bird is meant to be a very deep simulation of the real thing and what pilots get when entering the cockpit. Captain & first officer are expected to set their audio panel accordingly as part of their initial flight deck preparation flow.
  2. You are missing to activate the MIC for COMM1 Captain's side. See picture attached. I do train over PE, if you need more help let me know.
  3. mmmm since you mentioned this behavior arises after quite some time over the simulation, this could be a hardware temperature issue. I.E. it happened to myself running a latest spec imac which goes extremely hot under xplane hardware demands. I had to install a fan control app to proactively cool down the hardware. If the CPU or the GPU (graphics card chip) reaches the hardware operating temp limits, it automatically throttles down their operating Ghz frequency for allowing the hardware to cool down preventing damage. This will cause sudden/intermitent massive fps drops to the simulation that requires full hardware power for running smooth at all times. i would suggest to Jan's recommendations above you also monitor your hardware operating temps and frequency when you experience this.
  4. My fault not being clear enough. Assuming your xjoymap plugin is up & running properly EHSI mode & EHSI range commands should be under main/ tree not under xjoymap/ default tree see below noted in red [EHSI Range] new_command=EHSI Range dataref=ixeg/733/ehsi/ehsi_range_cpt_act description=EHSI Range values = 0, 1, 2, 3, 4, 5 [EHSI Mode] new_command=EHSI Mode dataref=ixeg/733/ehsi/ehsi_mode_cpt_act description=EHSI Mode values = 0, 1, 2, 3, 4 Note there is no tree specification in the command, this means they will be created under xplane main/ tree by default, scroll for them there to map If you want your commands under xjoymap/ tree, the syntax for the lines above should be: new_command=xjoymap/EHSI Range new_command=xjoymap/EHSI Mode note: you can also create your own tree. i.e. new_command=IXEG737/EHSI Range note2: don't ask me why commands you create with no tree specification goes to the main/ and not to the xjoymap/ by default. Devs decision hope this clarifies.
  5. xjoymap plugin allows you to create assignments on a per aircraft basis. Every aircraft developer provides their own datarefs for their simulation. you create a 'xjoymap.ini' text file on a per aircraft basis and the file has to reside on each aircraft root folder. Everytime you select an aircraft in xplane, xjoymap will check on the aircraft root folder you are selecting if an 'xjoymap.ini' file exists and load it for aircraft assignment parametrization or will do nothing if the file is not found. No need to have a file for each aircraft in your hangar. Just for the ones you require special assignments. xjoymap.ini file has a syntax structure for making the assignments you must comply. The documentation is included on the plugin and several examples over the forums. this is an example of the xjoymap.ini file you have to place under the 737 root folder to map the captain's EHSI range and EHSI mode to buttons or keys. ******************* xjoymap.ini [EHSI Range] new_command=EHSI Range dataref=ixeg/733/ehsi/ehsi_range_cpt_act description=EHSI Range values = 0, 1, 2, 3, 4, 5 [EHSI Mode] new_command=EHSI Mode dataref=ixeg/733/ehsi/ehsi_mode_cpt_act description=EHSI Mode values = 0, 1, 2, 3, 4 ***************** note: 0,1,2,3,4,5 are the values the 'range' dataref will cycle under each mapped button clic. Each value has a corresponding range on the simulation 0,1,2,3,4 are the values the 'mode' dataref will cycle under each mapped button clic. Each value has a corresponding mode on the simulation you can order the modes as per your liking or even cycle between less values. 1,4,5 (assuming you have no interest for 0,2,3 range selection) Now you go to xplane joystick & assignment tab or buttond adv tab on the right side you will see under xplane standard list the new commands EHSI range and EHSI mode for you to map
  6. You ve got it Selecting EHSI map range has multiple options. So a custom command clic will not do it because the simulation doesn't know what size you want to set. This is a good example of a dataref 'ixeg/733/ehsi/ehsi_range_cpt_act' depending the value you set on the memory position, the range you get in the EHSI. You need xjoymap, a lua script, or simular, to map your hardware button to the dataref and each clic you cycle the value stored on the dataref for different ranges. If you are a cockpit builder you may have a multi-position knob and no need to cycle, each position stores the proper value on the dataref for direct access to required range. I do use Goflight MCP PRO MCP myselft and pollypot GIT software, there are ixeg 737 aircraft profiles already done and available under their page for inmediate download. No need to fine tune nothing. GIT is the app (like xjoymap or lua script) that interacts to the goflight hardware, and based on your selection manipulate the aircraft datarefs properly and vicebersa. If something changes and the aircraft datarefs GIT displays/illuminate whatever in the goflight hardware.
  7. xp10? 1. go to joystick & assignment 2. go to buttons adv or tabs key. Depending you want to map a key or a button 3. you press the button you want to map (or you select the key you want to assign) 4. on the right side, you clic on the top right corner "custom cmd field" and a tree will popup. Navigate to ixeg stuff and select whatever you are looking for there. i.e. 'a/p disc' xp11 works the same but the UI is different and there is still parsing issues for the information to be shown properly. You need to map / un map blind at first, and then items will populate on the list. note: It is quite common people confuses Custom Commands vs Custom Datarefs or think they are the same. They are not, both lists are documented under the "2-interface guide.pdf. Custom commands. These are actions the developers provide for the users to map to key/buttons directly. So when you invoke them via button or key press, they perform an action pre-programmed. you use custom commands via mapping as explained above. i.e. 'a/p disc' when you map this custom command to a button or key, when you clic it will disconnect the autopilot Datarefs. These are memory positions the simulation store values. Based on the value the simulation does/show something. You can not map datarefs under joystick and assignment, you need a plugin/programing to manipulate the aircraft datarefs. i.e. 'the altimeter on the mcp' dararef. Doing a clic you do nothing. You need to store there values 100ft 1000ft 15000ft whatever you need to store that will be the target for the nav systems. i.e. suppose a 3 position light switch. storing a 0 value means light is off, 1 value means low intensity, 2 means high intensity. So when you build a cockpit, depending on your hardware switch position you store a 0, 1 or 2 on the dataref. I am giving you just generic examples to understand what a dataref is for i tried to be as simple as possible on the explanation. Hope this helps
  8. please try attaching your 'log.txt' file found on your xplane root folder. There could be there some clues of the issue after the crashes.
  9. you should open your support topic request under the SAAB340 support forum. http://forums.x-pilot.com/forums/forum/158-saab-340a/ you have lot of information there as well. You have to attach your xplane log.txt file found on your xplane folder after you try to use the aircraft so we can see what is going wrong
  10. These screenshots confirm the CPU is going to hell once you introduce changes on the FMC but we need to see what -process- is consuming the CPU. On the task manager clic the tab 'process' and sort them by cpu usage column. Check what the status is before and after introducing changes to see what process consumes the cpu
  11. It is not the a/c (aircraft?) folder you need to exclude. It is the entire /xplane 10/ folder you must exclude. Most importan to exclude it on windows DEFENDER
  12. if you are running xp11 beta 12 engines may not start, this beta is broken. otherwise please provide more details for help
  13. as per your vid, anytime you engage the AUTOPILOT the aircraft immediately enters CWSP & CWSR mode. This means the aircraft is receiving pitch and roll input from the yoke overriding A/P. Most likely you use a desktop grade yoke/joystick and the potentiometers are sending spike signals continuously (quite common on desktop grade hardware and coming worst with aging), the aircraft "thinks" you want to regain control (as it happens on the real thing if the pilot manipulate the yoke having a/p engaged) and goes CWSP & CWSR modes to concede control. Please try going to the 737 left side menu, preferences and move the CWS nullzone slider all the way to the right. This will increase the simulation capacity to ignore input from the hardware while A/P is engaged. hope this helps. check also your hardware is fully calibrated.
  14. I have no idea about the unexpected roll issue Right FD 'MA' light is off because Left FD was the MAster at that time. This is just fine.
  15. Wasn't LES team (creators of the magnificent SAAB340A) being working on a 747-400 or that project was cancelled?
  16. This is called crosswind correction The aircraft is pointing the nose 10 degrees to the right of desired FMC trajectory/course due to the existing 88 knots of right crosswind pushing the entire aircraft to the left. If the aircraft a/p does not point the nose to the right to counteract those strong cross winds the aircraft trajectory will be deviating to the left of the desired course. Try changing to HDG SEL mode instead of LNAV and set HDG 131 to coincide FMC course. The aircraft nose will be pointing to 131 as per the FMC, but after a few minutes your aircraft will be flying far to the left of the desired trajectory due to the winds. I prepared a picture for you, hopefully this makes simpler to understand what is going on here.
  17. when this interview took place? i have seen a post from Randazzo a few weeks ago to someone asking about porting the 747 and he said the DC6 was a layer to learn and interact with XP for the future, but XP does not support what they require for their complex 747 yet. While his response was about the 747, i am wondering whether this also restricts their 737NG or 777 porting?? (i am specifically interested on the 777 from them not the 737) 05/feb copy/paste from his response post ************ Actually, this has absolutely NOTHING to do with my decision that we will not be porting the 747 to X-Plane any time soon. Our products are designed to be largely platform independent- which takes a HUGE amount of work up front, but was more or less accomplished with this product. The DC-6 development was designed to build the connection layer that will exist between any PMDG airplane and X-Plane. We simply need the platform to catch up with what we are able to do under other platforms before we can move something as big and complex as the 747 into X-Plane. Currently the platform cannot take this airplane in the level of detail we have created it, without us removing some pieces that our customers feel are pretty critical- and that we feel are critical to the product's success. That is it in a nutshell. ************* link (page 2): http://www.avsim.com/topic/503584-pmdg-747-will-come-to-x-plane-aswell/page-2
  18. Glad to hear you ve got it working!
  19. I am on the celphone now and reading your log comes quite difficult. But seems you have the gizmo plugin trying to load twice? Gizmo seems loading at the beginning and again at the end of the log refusing to start check xplane resources plugins folder you have not duplicatd gizmo plugin
  20. My apologyes if you felt offended by the answer, maybe being a spanish guy my phrase is incorrect about the meaning. regards your car purchase comparison, i think it does not apply here. IXEG people is one of the the very few people i know were pretty clear and straight forward about the product shortcomings for 1.0 release made PUBLIC for anyone to decide on the purchase read here Edit: yes upcoming version is in beta and pictures of progress being made are available on another thread
  21. Nobody can answer this, not even the developers as they stated already. It will be ready when is ready. For those attempts made by the devs to shed some ETA, they were killed by unhappy users when targets were not met. Simulating a multimillion boeing aircraft systems to perfection for 80 bucks is a complex task thrust me.
  22. you need to request a link reset, send an email to support@x-aviation.com and you should receive a ticket # confirming your request got into the system. A response should take up to 3 business days.
  23. cool, nice work. Thanks for sharing this.
  24. do you remind the details of your flight? origin/destination airport departure runway and arrival departure prcedure, transition, route, transition, arrival procedure and approach? entered data, flight level, etc? i can try to replicate your flight over the weekend and see if i do get same result.
  25. I do also forgot to mention, the aircraft may stop following the magenta under certain rare conditions (known bug being worked on for the next update), maybe we have had a bad coincidence here. Maybe the aircraft just stopped following the magenta earlier unnoticed and you assumed it happened while you disengaged VNAV.
×
×
  • Create New...