Jump to content

Visibility Range


Richard Jenkins
 Share

Recommended Posts

That bug only manifests when the servers split & reconnect.. it's a byproduct of the servers trying to resync with each other.

 

Is it just me, or does the bug still exist? I still, to this date, see controllers from halfway around the world when I'm controlling at ZLA. And I can't imagine a range of 600nm can accomplish all that. Is VRC version 1.2.1 the latest?

 

Thanks for your help.

 

Yes, it still exists. It's not a VRC bug, so the VRC version doesn't matter. (It's a server bug.)

 

You bet. I had a few run ins early last year with Harv Stein (VATSIM5) a few times for being seen around the world only to controllers (not pilots) I had no control over that but it took quite a few PM's to make my case.

Best Regards,

Thomas Mathieu

VATAME1 Region Director

VATSIM Africa Middle East

http://www.vatame.net

[email protected]

TMSIGVATAME.png

Link to comment
Share on other sites

  • 2 months later...
  • Replies 127
  • Created
  • Last Reply

Top Posters In This Topic

Guys,

 

today, when working at Accra Control in Ghana/Africa, I was shown in the controller lists of ATCOS in Europe, Canada AND South America. And I swear, my Vis points were set correctly. So I guess there are still some bugs around.

 

(And if it helps: I am using Euroscope, not VRC)

 

Alex

gen.php?img=_5_1&cid=899395

Link to comment
Share on other sites

Guys,

 

today, when working at Accra Control in Ghana/Africa, I was shown in the controller lists of ATCOS in Europe, Canada AND South America. And I swear, my Vis points were set correctly. So I guess there are still some bugs around.

 

(And if it helps: I am using Euroscope, not VRC)

 

Alex

 

This is a known issue. I have had many run-in's with Harv pleading to him that I had my client set up correctly but was still showing up in controllers' boxes all over the VATSIM globe. To this day, I still have controllers from all over asking me where "DNKK is"

Best Regards,

Thomas Mathieu

VATAME1 Region Director

VATSIM Africa Middle East

http://www.vatame.net

[email protected]

TMSIGVATAME.png

Link to comment
Share on other sites

  • 3 months later...

Many OBSing can be accomplished with "simulated traffic" in EuroScopes. This just pulls the Whazzup file (like ServInfo) from the servers every 2 minutes. If you want to listen to voice, you may log on with vis range of 5NM and tune to the controller you like.

 

It would be very helpful if I could see the current server load. I could choose the best server easier and track down some lag/connection problems with planes. Maybe output a simple number, accessible like the Voice server stats? (:18009/?opts=-D-R). Including vis range/number of vis centers of connected clients would be nice also.

RealOPS2011-sig.jpg
Link to comment
Share on other sites

Jonas, Didn't know Euroscope had that seems like it would be pretty cool.

 

But I am useing Vrc which is less complicated and more user friendly. (in my opinion)

 

Norm, In small artccs 200nm and a few visual points can cover the enitre artcc and more.

 

But in a Larger ARTCC 200nm and all 4 vis points cann't always cover all of the artcc.

 

even if you have the points vis not overlaping.

 

400nm is a bit high but i also have seen twr with rng 150nm and polietly told them it should be 50nm

 

maybe a max range of 300 or 250 for obs and i was unaware of this rule the first list should be updated.

ZAU S-2, Major Certified

ZAU S-1 Mentor

(Disclaimer: the post above does not necessarily express the opinion or stance of ZAU or ZAUs training program, this view is made by me and me alone)

7664.png

Link to comment
Share on other sites

Anthony,

 

The overlying restriction is the connection should be for a valid use. Whilst a person new to the hobby may consider using a higher range somebody in your position should be considering training on approach.

 

Anything other than this style of training connection wouldn't fit into the existing regulations.

Norman

sig_FSLBetaTester.jpg

Link to comment
Share on other sites

  • 2 weeks later...

After all this I'm still trying to understand how far an OBSERVER can go: 200 / 250 / 300 / 350...

It should be defined here and at VATSIM because there is some issues about OBS range that go worldwide and without a rule about OBS range it's dificult to do the job.

Eduardo P[Mod - Happy Thoughts]os

VATSIM Supervisor

VATBRZ Senior Controller

Link to comment
Share on other sites

After all this I'm still trying to understand how far an OBSERVER can go: 200 / 250 / 300 / 350...

It should be defined here and at VATSIM because there is some issues about OBS range that go worldwide and without a rule about OBS range it's dificult to do the job.

 

Thought i read somewhere on Vatsim that a standard maximum OBS range is 150nm, going higher than that needed a reason. its mostly due to the bandwidth resources available.

 

Ramos

ZAB Instructor

Link to comment
Share on other sites

Jonas, Didn't know Euroscope had that seems like it would be pretty cool.

 

But I am useing Vrc which is less complicated and more user friendly. (in my opinion)

 

I think Euroscope is very user friendly, as much as VRC, if not more.

 

On topic: It is true. Observers are heavily restricted. Once, I observed a lot, with a controller rating. I had a supervisor come up to me and tell me that I should control, as he had seen me observing on other days as well. I believe he talked to me twice. It was a very interesting situation, I then realized how supervisors react to observers, especially, as I was observing daily. I think observers do observe with ranges that are a little higher than they should be. I find in many places, observers may want to watch the whole airspace, but the centre of their visibility is at the edge of the airspace, or something to that, I think if they re-centre their visibility, 600nm of range would be necessary for maybe, very large airspaces, if there is an airspace that stretches 1200nm across. I think it would save precious bandwidth if observers, even CTR controllers were able to keep their visibility range 'as low as it could go,' to see what you need to see.

Jody Turner - I1

Toronto FIR - Facility Engineer

8942.png

Link to comment
Share on other sites

Sorry Norman, but really I just can't find these heavily restrictions for OBS (at least in visibility range)

Point is, although an observer SHOULD mantain appropriate range (an OBS watching GND ops shouldn't have more than 20nm, he/she usually go higher - sometimes 300nm) most use 300nm, some 400nm (and these ones sometimes trying to argue that their mentor just said this range was allowed).

So what I think should be done is a NOTAM from VATSIM estabilishing the top range for OBS because without a clear rule about OBS range there will be always issues with observers.

Unfortunately, while Michael Zazula was trying to get new ideas about CoC, I really didn't say put in writing it should be nice to have an article about ranges. If so it would be very very nice, because there are some controllers that inisist in a higher range than the allowed one. Some tell that they "forgot" to change it since the last ocupied position was "above" the present one, but some always are on the same position.

Eduardo P[Mod - Happy Thoughts]os

VATSIM Supervisor

VATBRZ Senior Controller

Link to comment
Share on other sites

  • 2 weeks later...
  • 4 weeks later...

I don't know if people with extra high vis ranges are VATSIM's biggest problem. I created a php script that shows ever controller with a vis set to high (http://nyfc.site90.net/VatsimPHP/VatsimPHP/badvis.php) and currently there are only 3 people on that list, the most I have ever seen is 8. I think a bigger problem is pilots / controllers with an inactive connection.

8629.png
Link to comment
Share on other sites

Isn't it that pilots (at least using FSInn) can adjust their visual range, too?

So if all would turn up to 150NM this would produce high bandwidth, multiplied by 7 (as this is the usual pilots:controllers ratio at VATSIM).

 

We ask pilots at events to minimize their visibility - for the sake of FPS on their systems, to prevent FS crashs and maybe this also relieves the servers?

RealOPS2011-sig.jpg
Link to comment
Share on other sites

Isn't it that pilots (at least using FSInn) can adjust their visual range, too?

So if all would turn up to 150NM this would produce high bandwidth, multiplied by 7 (as this is the usual pilots:controllers ratio at VATSIM).

 

We ask pilots at events to minimize their visibility - for the sake of FPS on their systems, to prevent FS crashs and maybe this also relieves the servers?

 

It's been a while since I looked at the code, but I believe the vis range for pilots is hard coded in the server. If FSInn allows you to change it, perhaps that's only for when you connect with FSInn in observer mode. (Which actually connects you as a controller, not a pilot.) Not entirely sure, though.

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

its the multiplayer range mode i think hes talkin about.

 

that have any effect on the servers? i can see how the range effects them on the controller side, but on the pilots side you cant see aircraft beyond 15 - 20nm, you can barely see them at that range but theyre there. beyond that point i think FS doesnt draw them at all

Link to comment
Share on other sites

its the multiplayer range mode i think hes talkin about.

 

that have any effect on the servers? i can see how the range effects them on the controller side, but on the pilots side you cant see aircraft beyond 15 - 20nm, you can barely see them at that range but theyre there. beyond that point i think FS doesnt draw them at all

 

The multiplayer range mode does not affect the servers at all. That range just determines whether or not the pilot software will add the aircraft to the current multiplayer session, when it gets a position update from the server.

 

In short, there is no way for a range setting in the pilot software to affect the bandwidth consumption of a pilot connection. (There are non-range-related settings that DO affect bandwidth, such as the high frequency position updates in SB.)

Developer: vPilot, VRC, vSTARS, vERAM, VAT-Spy

Senior Controller, Boston Virtual ARTCC

Link to comment
Share on other sites

The multiplayer range setting provides info on all acft, spd/alt and hdg in the set range. If more pilots with higher range are querying the server, then doesn't it use more bandwidth? I agree with Ernesto that you cannot see the plane, actually FS9 only shows 10 miles and FSX will show it a little farther out, but FSInn Rad shows upto 120 miles, just the data.

When is your next Flight||VATSIM HitSquad Member, ZOA/ZAK/GANDER/P1

 

Link to comment
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
 Share


×
×
  • Create New...