Help would be appreciated.

Is there any setting that I can chage the default chase view to the back of the aircraft??

Is the setting of Standard -> Viewpoint -> Cockpit: long, lat, vert arm pilot's viewpoint affect the chase view??

On plane maker when I click save I get an error saying "You installed two incompatible GPS/FMS systems on the copilot side. You probably meant to install one for the pilot and one for the copilot.

I've tried ticking the copilot box, unticking it, ticking it on one and not the other etc but I can't see to get rid of the error. Any help appreciated.

Since I just discovered that airframe de-icing doesn't work on my aircraft anymore, I thought I'd best check if I had checked the "Anti-Ice Equipped" checkbox in "Special Equipment" ... but it's gone.

Where did it go? Is it still needed? If not, what's the secret to get anti-icing to work?

My aircraft has a single "ins_ice_surf_boot" switch. The "frame", "lwing" and "rwing" data-out values show ice accumulating even if the switch is "on".

Many thanks in advance!

Regards,

Henning (HoHun)

I've been trying to add a searchlight to a plane. I've added a spot light at max brightness and this is working well on land. However as soon as I go over water it stops illuminating. Can't even tell if it's on or off except by going outside the plane and looking at the nose.

Any idea what I'm doing wrong?
Thanks,
Graham

I have several years of experience with Autodesk Fusion 360, so I thought I'd try building a full scale 3D model which could be brought over into xPlane 11 via Blender. Fusion can export into both Wavefront .obj and Filmbox .fbx file formats - both of which are importable by Blender.

As a preliminary exercise I built a reference trident that was oriented to Fusion 360's default co-ordinate system. That was exported into both .obj and .fbx formats and imported into Blender. Those are the first three images shown below. One of the first things I noticed was that references to the appearance and material properties made it from Fusion into Blender when I used the .fbx file format.

Another discovery was that in exporting the Blender file into xPlane I could add "paint" to a part by manually editing the xPlane .obj8 file to add a TEXTURE directive pointing to a .png file that is simply a 64 pixel x 64 pixel .png "paint chip".  64 x 64 pixel size was chosen because making it any smaller didn't reduce the file size below 1kb. (I’ll discuss pixel pitch and scaling in depth later.)

The rendering engine seems to simply tile the color square onto the object's mesh.  I use a pixel size of 100 per inch because it simplifies the math when calculating object dimensions; A 20.48" wide x 10.24" high panel is 2048 x 1024.

I believe this is possible because the  .obj file which xPlane2Blender creates seems to conform to the Wavefront .obj file format which optionally includes texture coordinates.  It's not a full UV image Unwrapping but provides enough UV data to enable the rendering engine to paint the part.

For objects which only need one color applied everywhere this seems like an easy way to get a monochrome paint job. By taking a different approach to building the aircraft’s geometric model I've been able to obtain some quick and easy results. 

Quoting from that document;

Wavefront OBJ File Format.pdf

I have inadvertently zoomed and scrolled my PlaneMaker 10 view and now I cant see my aircraft model at all.

How do I recentre the view to Normal please?

I'm trying to port my XP11 aircraft to XP12. when I go to engine specs, I get a popup X-System message with:

flt_to_str NaN
v=NaN

Then Planemaker CTD.

I can't find which setting it's moaning about; any ideas?

Cheers!

Cessna 401 - Copy.txt

Regards, Ryan

Link to the vision jet G2

https://forums.x-plane.org/index.php?/files/file/49550-cirrus-vision-jet-sf50-g2/

Regards, Ryan

My queston is which parameters in Planemaker govern Gear Shock firmness or Wingflex? 

Thanks

I'm messing around with jet aircraft in Plane Maker with XP12, and after creating my first jet and configuring what feels like every section, I get this error in X-Plane when I load it up:

0:00:26.587 E/SYS: MACIBM_alert: I have found an engine with ZERO RPM for the GREENLINE RPM entered in Plane-Maker!
0:00:26.587 E/SYS: MACIBM_alert: Hard to get max power at zero RPM!
0:00:26.587 E/SYS: MACIBM_alert: Fix this in Plane-Maker!
0:00:26.587 E/SYS: MACIBM_alert: Aircraft/EB-52 Megafortress/EB-52 Megafortress.acf
0:00:26.587 E/SYS: MACIBM_alert: C:/GitLab-Runner/builds/2dtum6M9/0/x-plane/design/source_code/engine/fm/fm_init/init_pln.cpp:636

I don't know where this "greenline RPM" value is. I saw that there is one for other types of engines, but the Jet 2 Spool type doesn't have a section to enter that in.

What am I missing here? What did I forget to configure?
I can provide the .acf if necessary.

When pressing TF, this should enable me to see the course TO my VOR or the radial FROM the VOR.  

I know that X-Plane is capable of providing this radial as it is seen here on the 530 screen; it says VOR   LBY.   The RAD is 150 degrees.

I cannot find a dataref anywhere that lets me come up with a RAD of 150 degrees (or whatever is showing on the Garmin 530, just using 150 as an example) when I am trying to use in with my newly created T/F button on my SL30.   I have searched through "heading", "course", "bearing" and "RAD" datarefs (and RAD is huge...it included all the radio references) in my DataRef Viewer window.   I have looked now for two days....I give up. 

Would anyone have any ideas on which dataref I could use to give me the current radial from a VOR?  Or any other technique to get this value?

Thanks, 

Terry