Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 01/10/2017 in all areas

  1. Hey, I had the same problem last night just after the installation of AIRAC 1316 (FBO panel texture 1 ID: 2 is not a real FBO object. Failed with: GL_POINTS) I reinstalled the 733 via installer and it works again. Today I retested to update the AIRAC and re-crash (but this time I had aside the navdata files, reinjected in it and it's ok). I'll see later for AIRAC. Pat.
    2 points
  2. Hello All, What is the purpose of this two-position command (pushed or pulled) on the left side panel ? Any news of the 1.4 version ? Jean-Pierre
    1 point
  3. You can definitely expect a texture improvement. And more.
    1 point
  4. The scenery is now complete.You can find it on x pilot dsf secenery.
    1 point
  5. You can use RTH to adjust the intensity, it works ok. Sent from my iPhone using Tapatalk Or Ventura sky, actually I will recommend Ventura sky over RTH.
    1 point
  6. Ok thank you I did a full flight under XPlane 11 and I had no problems. I activated the APU in the PlaneMaker.
    1 point
  7. The scratches are part of the textures. You could remove the glass object from the aircraft in Planemaker, but you are effectively voiding support if you do this and you may lose glass from other areas. FYI: The DC3 is on the list for an XP11 upgrade.
    1 point
  8. My brain getting picked? I don't think it's even possible to make an aircraft that's cross compatible without some major changes. There's always changes that have to be made in the code. It happened with the Saab. When we started making it, it was intended to be for XP9 and 10. Then 10 came, and we saw a few major changes happened. The weather radar being one of them. So we dumped XP9 development and went strictly for 10 only. It would have been way too much work with a very low ROI. XP9 was pretty much dead by the time we finished the Saab. So it wouldn't make sense to make it for both platforms. If it's an aircraft with no plug ins, you can simply move the aircraft over from 1 platform to the next with no issues. If there are issues, opening the aircraft in the new version Planemaker, then saving it, usually fixes them. Some datarefs may be made inactive (which actually happened for the Saab in XP11), but it's not always a major problem. There's a new PT6 engine model in XP11, and that's thrown a bit of a spanner in the works for the Saab, so that's the thing we're working on now. The other big change now is PBR in XP11. Then to get the code right for the new version of X Plane...that could take a few weeks or a few months. It's kind of a shame that this happens, because it puts everything else on hold, but it's just part of the process and we have to get it done.
    1 point
  9. No accurate estimates on when it will be done. We have to get our previous aircraft working in XP11, first. (A few things have changed regarding plug ins). For the Citation, if all goes well, we're looking at next year, hopefully, the first half.
    1 point
×
×
  • Create New...