Jump to content

Marvin Palmer 878607

  • Content Count

  • Joined

  • Last visited

Everything posted by Marvin Palmer 878607

  1. It's back up again. Thank you Justin.
  2. TOADD is the waypoint you could have been transferred (based off your flight plan) https://nfdc.faa.gov/nfdcApps/services/ajv5/fix_search.jsp?selectType=state&selectName=AK&keyword=toadd ...which is in Denver Airspace. As a Terminal Controller (me), you'd get a runway [Mod - Happy Thoughts]ignment and type of approach desired at about 30-50NM out which coincides with my airspace. or If you listen to the ATIS of the Arrival Airfield (if they are online), you'd have an idea of which ones are in use.
  3. Page 10 of Craig Phillips Aircraft Situation Editor...
  4. Stefan, I have my sectorfiles on the autodownlaod feature of ES, (PAZA Sector)...but I do not have the asr nor the sct/ese uploaded just yet (stiil working out the issues. And my understanding is I can define several commenads off one line... ASR reads... line 1: PLUGIN:Display Elements:commands:.yeska5 line2: PLUGIN:Display Elements:.yeska5:6:.yeska5:1:JOH TED MDO:5:YESKA SOGBE sct has the above info and (dot) yeska5 keeps the star at the top of the list
  5. I had that issue awhile back and all I did was Right-click on the "Hungarian Matias.prf" and towards the top where it says Opens with: [Change...] and [Mod - Happy Thoughts]igned it to Notepad.
  6. Really nice feature to have! How does the the command line work to display a specific STAR with waypoints? is this possible off one command line. and How does the Radar function work? Is this designed for just one radar being displayed or all of them like (dot) showantenna In my sector file I have YESKA5 in this STAR, i would like to see YESKA and SOBE fixes at the same time....
  7. Good to hear, I need to start playing around with plugin scripts. It seems the best way to make your own personal modifications.
  8. VATSIM doesn't replicate wither they are modeC or ModeS capable..They are in theory ALL mode C and S. The only difference is if they use the proper suffix code to display. I've noticed that a lot of times the pilots do not place a suffix code in (or are primarily /F). If you have your radars placed and using professional radar, your target symbol (as explained by Gergely) will show up based on which radar picked it up and what suffix code is being used. I do cheat sometimes and change the code myself in the aircraft's flightplan, just to see different returns. If you go to "OTHER S
  9. That's the beauty of Euroscope. There's little if not any changes required to set this up and view tower traffic.
  10. try un-installing the program, re-download VRC from the website, and see what happens then (start fresh and delete your VRC folder as well)
  11. What about reducing your Range, and add more VIS points to cover your area?
  12. If they have the airfiled diagrams...look under tools, Diagrams. If no luck then I'd get ahold of the ZAB folks and ask about their sectorfiles.
  13. If all else fails try switching to another server and try it again. This has happened to me a couple time in the past...also had echo from the pilots too.
  14. Ross, they were the new ones that will take effect 09 FEB. It seems that alot of fixes are changing, or just recently changed within the last two months or so. This is a great feature, and you are going to maintain it, just thought from an FE perspective I can manage the ones for my ARTCC.
  15. Ross, I use FADDS, but I'd like to maintain just around the Radar sites, not necessary to maintain the entire ARTCC. I use the 60NM box around ANC and thats all is needed really. I just need a way of converting it to your format for use is all.
  16. Rahul, what method did you use to update the file...I ask because I want to update my files but to just the area (radar range). I don't think its necessary to have waypoints in another ARTCC...I've downloaded yours because it had the new waypoints!
  17. you need to have both the ese and sct files with the same name.... ENTLes.ese & ENTLes.sct & ENTLes.rwy
  18. The solution (if not alredy found) is to "shift + click Vatsim button"
  19. I guess it begs the question of...can you add more vis points?? is this an software constraint or server? Is there a way to code 6 or 7 vispoints without bogging down VATSIM servers, or is this going to be a known problem. I've engineered the Alaska region from scratch for the Euroscope client and run into similar issue of dead space. a lot of the Arctic region is not covered and the entire area west of the W180/E180 line. Small annoyance but still an easy workaround. Marvin
  20. If you connect to the server and this happens....switch to another server and re-check. I've run into that before when controlling. It's not a bug in software or coding...just an occurance. Marvin
  21. Ok, CZEG is rather large when it's displayed as a flat map...do you have traffic in the Artic region? maybe move point four (4) down or south and move it as needed while controlling for the Artic traffic? I know these are work arounds, just some ideas. Marvin
  22. Based on my inital look...you showed the visibility rings before you logged in...it will give you an incorrect ring size before logging in VATSIM servers. Connect to the network and do a .showvis....that should give you an better picture of your visibility rings, plus you can adjust as needed to get the coverage you need. Cheers Marvin
  • Create New...