jimcarrel

Members
  • Content count

    608
  • Joined

  • Last visited

About jimcarrel

  • Rank
    Member

Contact Methods

  • ICQ
    0
  1. No problems with my install. I did complete uninstall of P3D and re-install of 4.2. Then applied the 6616 update. AS16 started right up and performed as expected.
  2. Main thing to remember is that when you get an SSD over half full you start degrading that hopeful speed advantage.
  3. Can't really answer your question, but I've yet run into a default P3D heli that made it worth considering.
  4. your comp. will not blow up, just set it to 1 and see what the effect is If ;you don't own any 1 meter mesh it will not show up as 1 meter anyway
  5. If you ran the complete full installer rather than the individual parts, Client, Content,etc. all you need to do is uninstall Client, then reinstall the Client.
  6. Excuse me please, I had the Piston Duke v2 installed in P3D3.x and now it's in 4.1 with add-on.xml. I have Legacy and the Turbo in same folder with the Piston. If you're familiar with the xml thing, you will see how I have it; ---------------------- <SimBase.Document Type="AddOnXml" version="4,0" id="add-on"> <AddOn.Name>Duke B60 V2 P3D3</AddOn.Name> <AddOn.Description>Aircraft RealAir</AddOn.Description> <AddOn.Component> <Category>Effects</Category> <Path>E:\RealAir\dukeb60v2\Effects</Path> </AddOn.Component> <AddOn.Component> <Category>SimObjects</Category> <Path>E:\RealAir\dukeb60v2\SimObjects\Airplanes</Path> </AddOn.Component> </SimBase.Document> -------------------------------- <SimBase.Document Type="AddOnXml" version="4,0" id="add-on"> <AddOn.Name>Duke B60 V2 P3D3</AddOn.Name> <AddOn.Description>Aircraft RealAir</AddOn.Description> <AddOn.Component> <Category>Effects</Category> <Path>E:\RealAir\dukeb60v2\Effects</Path> </AddOn.Component> <AddOn.Component> <Category>SimObjects</Category> <Path>E:\RealAir\dukeb60v2\SimObjects\Airplanes</Path> </AddOn.Component> </SimBase.Document> --------------------------------------------------------- <SimBase.Document Type="AddOnXml" version="4,0" id="add-on"> <AddOn.Name>Legacy V2 P3D3</AddOn.Name> <AddOn.Description>Aircraft RealAir</AddOn.Description> <AddOn.Component> <Category>Effects</Category> <Path>E:\RealAir\Legacy V2 P3D3\Effects</Path> </AddOn.Component> <AddOn.Component> <Category>SimObjects</Category> <Path>E:\RealAir\Legacy V2 P3D3\SimObjects\Airplanes</Path> </AddOn.Component> </SimBase.Document> Of course I still had P3Dv3 installed when I went to v4. So required folders and info was copy and paste job
  7. Same to anyone who reads!
  8. Why is it so important to get in the last word...quick, someone post after me!
  9. There are people who see "the glass" as half-full, those who see it as half-empty and then there are those who see nothing in the glass. That must be a dry and thirsty life.
  10. To be totally fair, when I was in H.S. Reading Comprehension was readily taught. I think that got way-laid about 20 years ago. So nowadays, someone a lot younger than I get tripped up by printed phrases that are comparable to other similar printed phrases. When things aren't taught, they disappear. (just sayin') By the way, I have problems with AI aircraft models doing that black thing, so I'm going to try the tip provided.
  11. LOL, ranting does need a wee bit of justification.
  12. I would have to put JustFlight in that list that tries to treat customers right. At the same time, they are in business to produce revenue. Version 4 was a bit of a pita for smaller companies compared to larger ones.
  13. Way back when... is nice to remember when one was so inventive, (if like me) not so much now. Something must have changed.
  14. Thanks for that info Vic! I was watching Perry Mason last night and started thinking about where I would start researching FSUIPC. Makes sense that I might look at Pete's site.
  15. I've been meaning to do this for years, but, alas it has never come to pass. I've kept up with the paid version for years,but the only thing I ever did with it, was set the battery to not discharge while setting on the ramp and turning off autosave. It's always completed those tasks flawlessly. That would for sure fix the problem of making sure my stick ID's were consistently correct to match up with DCS.