Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/virtualw/public_html/Site/FAQ/index.php on line 9
VWN: Frequently Asked Questions
Skip over navigation
Home
News
Features
Community
Contact Us
Company
Not a member yet? Register for full benefits!

Username
Password

Frequently Asked Questions (FAQ)

Concisely, What does VWN cover?

In a nutshell, we cover the following areas:

Direct Technology

CAVE, CAVElib, Heliodisplay, DataGlove, HUD, HMD, Neuralprosthetic, these and oh so many more technological devices and theoretical systems designed to interlink the mind into virtual reality, or augmented reality systems.

VR Developments

Haptic interfaces, Human-Machine interfaces, immersive experiences, patents, legal cases and so much more. All the latest developments occuring in the VR field, as it pushes forwards - all interlinked, and cross-indexable, we work to not only display but inter-create systems, and encourage further growth.

AR Developments

Augmented bodies, AR HUDs, developments in augmenting reality by merging both. Speech recognition, gesture recognition, speech replacement, RFID and the sensor web. GPS, and so much more. Everything occuring in the modern world of augmented reality, almost as it happens, and as with VR we interlink, promote and find ways that different approaches can benefit each other.

World Content

Oh great, we have all these wonderful world-systems. Now, what exactly do we put in them? Content of all kinds for virtual replication. Mythological creatures, models, skins, ancient and modern weaponry, architecture, geology, getography, professions, natural formations - all geared explicitly for recreation in the virtual.

As much content as possible, in as many different formats as we can, to give you a chance to fill your world with greatness.

 



Warning: Unknown: write failed: Disk quota exceeded (122) in Unknown on line 0

Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0