VRC 1.1 : Betatest für das erste Update startet

[Martin Georg]

Hallo,

na ob man das nur ein "Update" nennen darf? Gestern ging die erste Testversion von VRC 1.1 an die Betatester raus (heute morgen schon die zweite ), und die Liste der Neuerungen, Fixes und Änderungen ist beeindruckend! Ross Carlson erwartet nach eigener Aussage eine Testphase von wenigstens einem Monat, "in 2 weeks" stimmt also mal ausnahmsweise noch nicht.

OK, gehen wir in medias res. Hier die Liste der Änderungen und Fixes:

Here's the new feature list:

- 3D radar mode
- Simple radar mode (identical to old Ground mode)
- Profile import/export/merge functions
- Reminder lights button (Lights blink to indicate waiting
chat, handoff, reminder list, and override mute)
- Right-click context menus for targets, aircraft list,
controller list, flight strips, weather panel, chat groups
- .findac command for supervisors (Jumps to a/c location)
- Hotkeys for all tool windows. (Alt + number)
- CTRL-G opens diagrams window for active display
- SELCAL dialog (shows list of aircraft which contain a SELCAL
code in their remarks - double click to send SELCAL)
- Mute button on Comms Panel mutes your mic when overridden
- .fd command toggles diagram(s) on/off
- CTRL-ALT-SHIFT-double right click shows mouse coordinates in
command line for cut and paste into ACSim/TWRTrainer files
- .showstats command shows some stats on number of aircraft you've
worked with during the session
- .resetstats command resets statistics counters
- Added $type() function for aliases (inserts a/c type)
- Added $atiscode variable for aliases or ATIS
- Added $route variable for aliases
- Added $aircraft variable for aliases (inserts selected a/c callsign)
- .showloc command shows center and range for specified controller

Here's the list of feature tweaks:

- F9 v/r/t now amends flight plan remarks
- Opening a new sector file now sends position update immediately
(This is to get new targets appearing instantly instead of
after a 15 second delay when moving to a new area.)
- Flight strips for radio-selected a/c are highlighted in the bay
- Most key combos now work from any window
- Callsigns in reminder list message sorted by time in reminder list
- Chat group members are greyed-out if offline
- Chat window title bars flash when message waiting (optional)
- Strips are only auto-added to the bay once per callsign
- Option to auto-delete strips when pushed to a controller
- Ruler data button can now be toggled off in General Settings
- Ground radar mode now shows a/c type and ground speed
- VRC radar mode now has vector line similar to DSR mode
- Observers cannot initiate G/G calls
- Selecting a controller via CSEL now updates controller info
shown in the box at the bottom of the CL
- Stations for which no METAR downloaded are no longer removed from
the WX Panel - allows for intermittent stations
- Standby target now easier to distinguish in GND/TWR modes
- All dot commands now work from chat window command lines
- Aliases used in private chats now use the radio-selected a/c
as the reference for functions such as $alt()
- When clicking a target to untag it (F1) the target is no
longer radio-selected
- Ruler data now drawn with leading zeros for consistency
- .showvis now shows a range ring around all vis centers
- Traffic pointout mouse combo (SHIFT-CTRL-click) now handled as
a "give way to ..." command when a/c are moving at less than
50 kts (assumed to be on the ground, taxiing)
- Either end can now close an override
- New chat windows now open at the x/y of the primary display
instead of at 0,0 which was causing problems for some users

Here are the bug fixes:

- Shift key no longer scrolls CL
- NDV METAR code no longer breaks parser
- Fixed crash due to HTTP error during server download
- ESC key now closes Comms Panel properly
- Percent signs no longer break text shown in radio log area
- Fixed crash due to repeatedly clicking a WX Panel entry
- Chat history now scrolls to the bottom when a new message
is received while the chat window is hidden
- Sector IDs longer than 2 characters are now valid
- Tool windows now brought to front when unhiding them
- Fixed crash caused by "F4 <ASEL>" with no selected a/c
- Fixed crash due to ATIS lines with only spaces
- Fixed crash due to missing parameters on alias functions
- Fixed race condition caused by using $altim() at start of alias
- Fixed crash due to use of some alias functions in private chat
- Airspace ceiling no longer limited to 32k
- Anchors now recognize 2 character VORs

Und damit das nicht nur trocken klingt, gleich mal 2 Screenshots des 3D Modes von Ross:











Zum 3D Mode gibt es eine längere Erklärung von Ross, die ich am besten auch mal gleich hier poste:

Here's a brief description of what the 3D mode is all about:

The 3D radar mode came about for three reasons. The first reason is because I thought it would be really handy to be able to approximate a "tower view" within one of your display windows. Even though the VRC 3D mode is a simple "wire-frame" mode with no aircraft models, terrain, textures, weather, etc., it can be a lot of fun to use when working as TWR or GND. The second reason is because I thought it would be really fun to code, and would give me an opportunity to start to learn 3D graphics programming in OpenGL. The third reason is because I watched "Pushing Tin" and thought of how cool it would be to have a 3D virtual radar screen that showed imagery similar to the scenes showing what's going on inside Nick Falzone's head in the movie.

Obviously, this 3D mode is not meant to model anything realistic. It is mainly just a novelty feature. I have no intentions of expanding its capabilities at all. I wasn't even sure if I was going to leave it in the release version. Think of it as a "poor man's tower view" until we get a REAL tower client like XTower.

To use the 3D view, select 3D from the radar mode menu. You can then pan and tilt the "camera" by holding the right mouse button and moving the mouse. If you hold BOTH the right and the left mouse buttons and move the mouse, you can slew the camera around the 3D world. The following dot commands are supported to help you configure the 3D view:

.set3dcenter FIX - moves camera to FIX
.set3dalt FEET - sets camera altitude to specified altitude MSL
.setterrrainalt FEET - sets the altitude at which sector data is drawn

You can also adjust the camera altitude by holding the CTRL key and rotating the mouse wheel.

VRC implements rudimentary target "smoothing" to make them move smoothly in 3D mode. This smoothing is NOT as accurate as that found in SB3, FSInn, XSquawkbox, or XTower. You WILL see jumpy aircraft if position updates are delayed due to network lag.

You can "lock" the camera on a target with ".lockview <ASEL>". Use ".lockview <ENTER>" to unlock.

All targets are drawn as simple "paper airplane" models. There is no size or shape variation to the models. Each target has a line drawn from its base down to the terrain altitude in order to give an altitude reference. (Since there are no shadows, it can be hard to tell how high an a/c is above the ground without this line.)

The data tags in 3D mode rotate among the callsign, the altitude and ground speed, and the scratchpad and aircraft type. The target is shown with a dot or an asterisk to indicate standby or mode C squawk, respectively.

That's it for the 3D mode. Play around with it and have fun.

[Meinolf Höhler]

Hmmm, 2 Screens? Irgendwo ist da was verloren gegangen

[Martin Georg]

Das ist aber komisch - hat da wer rumeditiert??? Hab das 2. Bild wieder eingebunden.

[Klaus Koths]

Sieht aber nett aus....

[Daniel Raetzel]

Braucht man dann für die VRC 1.1 Version 4 Bildschirme *duckundweg*

[Martin Georg]

Schönefeld am Abend ...

Was allerdings irgendwie nicht funktioniert hat, ist ".setterrainaltitude" ...

[Frank Helmschrott]

Was allerdings irgendwie nicht funktioniert hat, ist ".setterrainaltitude" ...

RTFM das heisst auch ".setterrainalt" und funktioniert zumindest bei mir einwandfrei.

[Martin Georg]

*grmbl*

[Thomas Purbs]

Zitat von Martin Georg

Schönefeld am Abend ...

Hat das Ding etwa auch ne Funktion, alle Fieger auf Sectorfile-konformen Positionen anzuzeigen?
Alle vier auf korrekten Parkpositionen bzw. mittig auf dem Taxiway, hab ich ja nochnie erlebt...

[Wolfgang Hagel]

Siehst du an den senkrechten Strichen (stellen die Höhe dar) unter dem Flieger. 3 auf den Stands einer am taxeln. Wenn die Airporthöhe eingestellt ist sitzen die direkt auf den Stands