Jump to content

planebass

Members
  • Posts

    21
  • Joined

  • Last visited

About planebass

Recent Profile Visitors

512 profile views

planebass's Achievements

Newbie

Newbie (1/14)

  • Week One Done Rare
  • One Month Later Rare
  • One Year In Rare

Recent Badges

5

Reputation

  1. Smart catch!! And rgr okay. Thanks for the input.
  2. Hi, After stumbling on the following video: I noticed that the water color of this user is a lot more darker/blueish than mine (see attached). So my question: Is it possible to change PFPX water color? If so how? If not, might it be that this user's monitor settings are just as such that it looks blueish/darker? Thanks Ashwant
  3. I think you used tabs on your keyboard? If so that messes up things when printing out in PDF. In that case I'd advice using the space bar or the <&#:xx> code for starting your text at a specific place (note the "xx" in the code is the number needed to start at the specific point. So, <&#:20>////// APPENDED MESSAGES ////// - starts that line of text at the 20th character in that line...). Also, I think you're missing the Winddata sections start and end -> <&WindDataBlock_Begin> <&WindData[1]:65> <&WindDataBlock_End>
  4. Same here...can't even release an OFP with Active Sky (after having switched from the server) as it is stuck trying to download NOTAMs.
  5. Nvm @Serge75, I just redownloaded the FAA Route Translator Spreadsheet, re-ran everything and it all works. I have my .txt file to import into PFPX. I think maybe from previous saves something must have corrupted the spreadsheet... In any case, thank you for the help.
  6. Yes I have been able to export the FAA routes previously (before the quotes change) perfectly. Yesterday I read about the quotes problem and applied the fix and it parsed the data succesfully (see below image): This is how the output tab looks like: Not as yours....I've included the formula field...but can't figure out what #REF! field it's missing....
  7. Hi @Serge75, It all worked until step 6...upon saving it gives me an error: "Type mismatch" Followed all the steps in the sheet (including removing the quotes). It parsed the data successfully and told me to continue to step 6 where I get this error. Any ideas how to fix this?
  8. Hey MD-82, Maybe it would work by adjusting the fuel policy to add fuel for an alternate and then during planning eliminate the automatically added 30 min hold fuel? Maybe this way it also then accounts for ALTN-2,3 and 4? PB
  9. Ohh SRD's, yeah I know of it I used to download them from the download page but you have now provided me with the keys to the kingdom (especially since I can now also update my FAA routes ). But I assume you created the spreadsheets? If so, I'd like to run an idea by you which I have tried myself but am not sufficient enough with macros. So it didn't pan out....
  10. What spreadsheets? Could I get in on the action? I assume it's NATS tracks for non-PFPX subscribers?
  11. Hi all, I love PFPX but I'm finding that certain "codes"/features is still lacking. With the above tread title I'm referring to this old tread -> I'm working on an OFP template and I'm also looking for AVG TRACK and TOC TROPOPAUSE and the ability to have the Navlog display the title text above every new page (as most real world OFP's do), amongst other things. Don't get me wrong, I'm not lashing out at PFPX or anything...who am I to even "force" requests as top priority...however as a PFPX entousiast from day 1, it is dissapointing that it takes so long between updates (if the software is even still in development..). For instance, often I'm busy planning a flight and the program just crashes on me (v2.03 and mostly during weather [ASKY] loading but sometimes also during calculations when a second time it calulates perfect without crashing). I've learned to expect this but I don't think it's a very stable software.. 1. Does any of you have alternate suggestions how to bypass the lack of above request (AVG TRACK, TOC TROPOPAUSE, Navlog display the title text above every new page)? 2. Developers, are you still developing? Is the software alive/dead? It's just for me a piece of mind that I can either move on instead of ranting on here...don't hold this against me. I refuse to switch over to the competitions as personally I find none of them to the level of this software. I think this software has so much more potential. I love it! It just sucks that there is absolutely little to no updates/fixes/status updates etc (apart from here and there support from what I can see). And I know you all have a life, so do I. But not even a 5 minute status update now and then????
  12. Hi, Can anyone do the KLM A333 PH-AKB? https://www.google.com/search?q=klm+a333&rlz=1C9BKJA_enNL822NL823&hl=en-GB&prmd=insv&sxsrf=ACYBGNRLOoA9xJN68FGASsA-8iSMNyiuYA:1575886381763&source=lnms&tbm=isch&sa=X&ved=2ahUKEwiy4vafqqjmAhVBbVAKHehsDWwQ_AUoAXoECA4QAQ&biw=768&bih=915&dpr=2#imgrc=1KWhy-2y6SJw_M&imgdii=C4HOqfFgsDKFeM Thank you.
  13. Hey Mathijs, Happened to me this afternoon. Here form the windows logs...anything I can do? Sporadically it crashes sometimes...sometimes also after a while of it being open/using it. Today it started and then crashed... Faulting application name: PFPX.exe, version: 2.0.3.0, time stamp: 0x5c0e3189 Faulting module name: ntdll.dll, version: 10.0.18362.1, time stamp: 0x9bbcb4a9 Exception code: 0xc000041d Fault offset: 0x00040153 Faulting process id: 0x250c Faulting application start time: 0x01d5632a7fc32779 Faulting application path: E:\Add-Ons\Professional Flight Planner X\PFPX.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: 6509798b-8ef2-4711-901b-2b40a5cd5889 Faulting package full name: Faulting package-relative application ID:
×
×
  • Create New...