cancel
Showing results for 
Search instead for 
Did you mean: 

DOOM 3 BFG - VR ( V0.021 Updated 3-12-2017)

Samson
Heroic Explorer

Latest Release And Downloads:

Latest Version: V0.021

https://github.com/KozGit/DOOM-3-BFG-VR/releases

Updates from v0.20:

Edit: Many many thanks to 2EyeGuy for all his hard work on the .020 release, and for handling bugfixes and compiling this release while I was on vacation

Additions:

QuakeCon style teleport. ( jkchng )

Fixes from v 0.020

Fix issue #107: use other hand for movement.
Fix issue #97: Fix talking waking monsters.
Fix issues 100 & 106: Change language detection to use sound files. Issue #100 and Issue #106            
Fix issues #113 and #27: Fix timing issues.    
Improve issue #27:Disable ASW and make it a menu.
Improve issue #103:    Fix loading old savegames with different scripts.
Fix crash loading 020 save games, and allow old versions.
Loading RBDoom savegames works now.
"Fix" loading script objects of different sizes.   
Fix save and load menus.    
Adjust installer, Readme, and other docs for v 0.21 Alpha.
Work Around Movement Popping.

**EDIT:**
Known issue: After saving a game it might appear greyed out in the load game list and be unable to find it. To fix this issue, either use this console command before opening the load game menu, or exit the program and restart it:
testSavegameEnumerate
This issue is fixed in the next version.


Previous Release:

Doom 3 BFG VR: Fully Possessed V0.020 Alpha


This is sizeable update with many new features and improvements.


New features include:


Teleportation is now supported, including a parabolic aiming beam.


Voice commands are supported - say a weapon name to select it!


Flicksync mode based on Ready Player One.


Many aids to prevent motion sickness, including a new Third Person movement mode.


Many other improvements have been made, please see the readme.txt for a full feature list and documentation.

https://github.com/KozGit/DOOM-3-BFG-VR/blob/master/README.txt


Default Configuration

No single controller configuration or comfort setting is going to accommodate all users equally,

so Doom 3 BFGVR: Fully Possessed defaults to a comfort oriented mode.
In the default mode, comfort ( or snap ) turning is enabled by default,
and artificial movement uses the Third Person mode. These settings
should provide a comfortable experience for almost all users. These
settings may be easily changed or disabed in game if they do not suit
your needs. From the System Menu ( say 'System', or press ≡ (menu) on
the left Touch or Right Vive ), then select 'VR Options' then 'Comfort +
Safety Protocols'. From this menu, use the 'Turning' options to change
the turning mode (' smooth 'is standard analog turning - caution -
smooth turning causes motion sickness in most people ). Use the 'Motion
Sickness Aid' options to change the comfort settings. 'None' disables
all motion aids, but this will induce motion sickness in the vast
majority of people.


Default Controller Layout

The default controller layout can also easily be changed in game. Any
controller button or Stick/Pad axis can be mapped to any in game action,
to easily create a controller layout tailored to your liking. From the
System Menu ( say 'System', or press ≡ (menu) on the left Touch or
Right Vive ), Select 'Controls' then 'Key Bindings', Scroll through
the list and highlight the action you would like to change the control
for. Press the trigger to enter 'bind' mode, then simply press the
controller button or stick/pad axis you would like to assign to that
action. If the button or stick is already assigned to a different
control, you will be asked if you are sure you want to re map, otherwise
you are done! A button or joystick/pad axis can be unbound from an
action the exact same way.


Installing Doom 3 BFG: Fully Possessed.


There are two options for installing the mod: A self-extracting installer, or a .zip file.

Due to the inclusion of new player AAS files needed to support teleportation, the size of the mod has

increased a fair amount. You will need about 1GB of free hard drive space to install the mod.


Installing with the self-extracting installer

Download the file 'Doom3BFGVR_Fully_Possessed_Alpha020_Installer.exe' from the release page at the top of this post and execute.


By default, the installer will look to install the mod in the default
app directory in your Steam library on drive C. If your Steam library is
in a different location, or you have installed doom 3 someplace else,
browse to the location of your Doom 3 BFG installation. IMPORTANT
If you browse to select a directory to install the mod, the installer
will append 'Doom 3 BFG edition' to the install path. REMOVE THIS from
the install path, so that only the full name of your Doom 3 BFG
directory is displayed. Failure to do this will result in the mod files
being installed in the wrong directory. Once installed, you should see
a folder named 'Fully Possessed' inside your main Doom 3 directory
along with some support files and the Doom3BFGVR.exe. Launch this .exe
to play.


Installing with the .zip file

Download the 'Doom3BFGVR_Fully_Possessed_Alpha020.zip' file from the release page at the top of this post, and
extract into your main Doom 3 BFG directory. You should see a folder
named 'Fully Possessed' inside your main Doom 3 directory along with
some support files and the Doom3BFGVR.exe. Launch this .exe to play.


Compatibility with existing Mods or Native Doom 3 BFG

Doom 3 BFG: Fully Possessed stores all changed assets and save games in
their own directories. Installing the mod will not interfere with
existing mods or the native game.


Compatibility with the Hi-Def texture pack

Doom 3 BFG:Fully Possessed is compatible with the hi-def texture pack.
Please be aware that the 'generated' folder included in the hi-def
texture pack is corrupt, and will crash the game if not deleted. This
is not an issue with this mod, but with the texture pack itself. After
installing the texture pack, delete the 'generated' folder inside the
'Base' directory.

NOTES


  1. The texture pack also installs German language files. If you do not
    want the game menus to be in German, delete the 'german.lang' file in
    the 'Base/Strings' directory.
  2. It does not matter if you install the mod first or the texture pack
    first, but be aware that games saved without the texture pack installed
    will not work once the pack is installed, and vice versa.

Reporting Bugs

Many bugs have been addressed in this relase, but if you do find one,
please open an issue on our tracker. We can't fix it if we don't know
its broken!

https://github.com/KozGit/DOOM-3-BFG-VR/issues


Enjoy!




OLD UPDATES:

--------------------


Update 12-10-2016

Fixed bug related to save game crashes. Archives updated


Additional Update 12-9:

I've updated the OpenVR version of the mod to address  issues some people were having, and added a few new features.

There are now versions of the mod that support OpenVR and the Rift/Touch natively via the Oculus SDK.

See  below for a link and additional info. 


Update 12-9


I've updated the mod and posted a test verison with native Oculus/Touch support.

This includes full motion controls and the ability to interact with in game guis and the PDA by using them as touch screens.

Release:

https://github.com/KozGit/DOOM3-BFG-RIFT/releases/tag/v0.11-alpha

Please
make a clean copy of your doom 3 directory before installing, right now
this mod will not co-exist with other mods as too many of the
assets have been changed.

Take a look at the description on the release page, and the two readme files
included in the archive.  I've also included a .pdf that lists
most of the common cvars you can use to configure the mod.  Please
remember all the controls ( all joystick axes and buttons) can be
unbound or remapped to any other control. In the system menus go to 
(Settings->Controls->Key Bindings)

There's still a little oddness during loading screens.  Let me know if you find any issues. This is the first test of this, so there may be issues I'm unaware of, please let me know if you find anything.



------------------------------------------------------------------------------------------------------------

Previous update:


I've been working on a mod for Doom 3 BFG edition for a while, and it might be ready for an alpha test. I'm looking for people to test and let me know what issues ( and I'm sure there will be some ) you have. ( Please note this is an entirely new mod, not a variant of an existing one.)


Anyway, here we go:

https://github.com/KozGit/DOOM3-BFG-RIFT/releases

New features:



Full motion control support for weapons, with support for right or left handed control.

Reload mechanics and motion controlled melee attacks are NOT finished yet, but in progress.

For now press the attack button to punch and reload to well, reload. Grenades are now

thrown via motion controls.



Flashlight modes

The flashlight can be held in the off hand, mounted to the weapon, mounted to the player helmet, or

mounted to the player body. If 'mount to weapon' mode is enabled, and a weapon without a barrel is

selected (e.g. grenade, fists, chainsaw) the flashlight is temporarily moved to the head.



Player body view modes:

You can chose to view the entire player body with ( very very basic ) IK for the arms, view the weapon and

hands, or view the weapons only.



Weapon sight modes:

Chose from a laser sight, laser dot, circle dot, or crosshair.



Optional heading indicator.

With independent head/body movement it's easy to forget which way the body ( and forward

movement) is pointing. The heading beam points in the direction the body is moving. Beam can be

solid, have arrows, or scrolling arrow. Temporary artwork.



Movement options:

The player body is locked to user position, so moving in the real world moves the player body.

Optional comfort turning, with user defined delta and repeat delay.

Walk speed adjustment from game default consistent over level changes

Option for forward movement to be in direction off hand controller is pointed

Headkick and knockback are disabled by default but can be toggled.

For non motion controls, you can lock the view and aim together, or use independent aiming with user

defined deadzones



Hud options:

Hud is translucent and projected into world.

Hud can be locked to the view or the body.

Hud position and size are configurable.

Hud can be toggled on or off, or faded in when user looks down past defined angle

If hidden, can be configured to reveal when health below defined level

Individual Hud elements can be turned on or off if desired



Stat Watch ( for the love of god someone come up with a better name )


Ammo stats are provided on a wrist worn armament inventory device if player has weapon equipped.

Soon to provide health stats as well.



Gui interaction modes.

Player can choose one of three ways to interact with in game guis

1) Look direction controls gui cursor

2) Weapon aim controls guis, in the event weapon has no barrel (grenade, fists, etc) default to look

direction

3) If motion controls are enabled, guis can be touch activated. When close enough to touch, look at gui

to activate then touch gui to control.



PDA is rendered as model in game.

PDA can be held in hand, or fixed in a position in front of the player body. If gui touch mode is enabled, the

PDA works as a touch screen device. Pressing escape during the game brings up the system menus in

game on the PDA.

PDA fixed position can be adjusted.



Cinematics

Cinematics are now from a fixed camera position. This is still being worked on, but is much better than the

free camera IMO. Some camera files still need to be tweaked for some of the cinematics. Pressing the PDA

button will exit the current cinematic



Pixel density can be adjusted.



ALL controller buttons and axes can be re-mapped to any control or action.



Weapon models have been fully fleshed out.

All of the options are currently controlled via cvars that start with vr_.  I'll add the options to the menus at some point.

The code has not been tested on any machines other than mine, so hopefully it will at least run for some of you 🙂

There are some issues I do know about. The loading and saving transitions are pretty glitchy, which is annoying.  I'll either smooth them out or just black them out.  I changed how the player hand animations work, so occasionally the hands don't play the correct firing animation.  I know how to address just need to implement.  The weapons also jump/blink for a frame when you change weapons, I know how to address I just need to get to it. Also, the source code is a mess, it's not actually on github at the moment, I'm working to clean it up and get it posted soon.

Anyway, let me know how it works for you!





908 REPLIES 908

elboffor
Consultant
I really want to try this out, but I also really want to wait till I get my touch controllers.
1st world problems right here!!!
This is my forum signature.
There are many others like it, but this is mine.

RABID
Expert Protege
just tried it on a clean install. its crashing on the intro cut-scenes. all 3 campaigns. using an Nvidia 980 with latest drivers

Leyland
Expert Protege
The biggest problem with this release is this:
https://github.com/KozGit/DOOM3-BFG-RIFT/blob/master/COPYING.txt

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights.  Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received.  You must make sure that they, too, receive or can get the source code.  And you must show them these terms so they know their rights.
It looks like your source code is out of date with your binaries. Is this something we can just request from you and you email to us, or were you just not planning on releasing it?

Anonymous
Not applicable

Leyland said:

[snip]

It looks like your source code is out of date with your binaries. Is this something we can just request from you and you email to us, or were you just not planning on releasing it?



Samson said:
[snip]

Also, the source code is a mess, it's not actually on github at the moment, I'm working to clean it up and get it posted soon. 




danknugz
Superstar
this works with touch?
A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on forums?

Leyland
Expert Protege

AndyW1384 said:
[snip]

Also, the source code is a mess, it's not actually on github at the moment, I'm working to clean it up and get it posted soon. 






That's no excuse :smile:

My code is a tremendous mess, the code he has in his repo right now looks considerably better than what I have right now (he has things in actual files!)

The purpose of sharing code isn't so that people admire how beautiful your code looks (although they can), it's to help fix bugs and for people to learn how things work.

Besides, in my experience in open source, the worst criticisms I have gotten is not from other coders but from end users.

Samson
Heroic Explorer

Leyland said:

The biggest problem with this release is this:
https://github.com/KozGit/DOOM3-BFG-RIFT/blob/master/COPYING.txt

To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights.  Therefore, you have certain responsibilities if you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received.  You must make sure that they, too, receive or can get the source code.  And you must show them these terms so they know their rights.
It looks like your source code is out of date with your binaries. Is this something we can just request from you and you email to us, or were you just not planning on releasing it?

When I put the video on youtube a year or so ago showing progress using the razer Hydras, I started getting spammed for requests on how to compile, how to play, feature requests etc.  The game was in a completely unplayable state, and I didn't have time to deal with all the requests, so I moved the code to a private repo to continue working on it.  As it's private,  I've stupidly been using it for lots unrelated things and generally made it a mess.   It has nothing to do with criticism, ( I freely admit I'm a terrible programmer, no amount of code clean up will hide it ) I can't just throw the code over without cleaning it up - at a minimum removing unrelated code and my coarse language from the comments.  The code will be released when its ready, and I wont apologize for that.

But still,  with all the posts here and on reddit about progress,  no one, including yourself, ever reached out to anyone here to ask if the code was available, or want to collaborate,  which would have been given or done gladly. To me, THAT's the biggest problem with this release. And yet you'll take the time to make vaguely condescending comments now?  There's no competition here man, we should just be having fun. 

( And for the record, there are far, far bigger problems with this test than the source isn't available yet. 🙂 )

Leyland
Expert Protege

Samson said:
When I put the video on youtube a year or so ago showing progress using the razer Hydras, I started getting spammed for requests on how to compile, how to play, feature requests etc.  The game was in a completely unplayable state, and I didn't have time to deal with all the requests, so I moved the code to a private repo to continue working on it.  As it's private,  I've stupidly been using it for lots unrelated things and generally made it a mess.   It has nothing to do with criticism, ( I freely admit I'm a terrible programmer, no amount of code clean up will hide it ) I can't just throw the code over without cleaning it up - at a minimum removing unrelated code and my coarse language from the comments.  The code will be released when its ready, and I wont apologize for that.

But still,  with all the posts here and on reddit about progress,  no one, including yourself, ever reached out to anyone here to ask if the code was available, or want to collaborate,  which would have been given or done gladly. To me, THAT's the biggest problem with this release. And yet you'll take the time to make vaguely condescending comments now?  There's no competition here man, we should just be having fun. 

( And for the record, there are far, far bigger problems with this test than the source isn't available yet. 🙂 )

I'm not going to bother arguing with you, I don't consider this a competition either, rather I am actually interesting in seeing your changes, and the only reason I am not asking for it now is that I am still working on mine and wouldn't have as much time to look at it. What I am more worried about, and seems like a realistic scenario at this point, is that you disappear and never release the source code.

In my experience releasing binaries is a heck of a lot more trouble than releasing source code, maybe you've had a different experience, but as a recent example, I've had to buy a Vive this week (which I had planned to do much later on) in order to fix bugs because someone figured out they can run my binaries on Vive and shared the news on reddit.

Keep in mind also no one had to ask for source from these guys http://www.mtbs3d.com/phpBB/viewtopic.php?f=142&t=16703 and I even contributed a patch to them as a result (I'm LeeN), and your work here has benefited from them having shared their source.

Thane_
Heroic Explorer
@Leyland: is this the version of Doom 3 VR that people are playing all over YouTube the last few days?

@Ayndroid: the size of the world is designed and made in 3D, everything should be exactly as the developers intended, in 2D or 3D. That's why I Nvidia 3D Vision work so well all you have to do is convert the game automatically to 3D and just a few things like Shadows or lighting needs to be fixed and you're good to go in general. 3D modelers, like myself, actually use digital rulers and units of measurement when building models. Unless something very strange is happening everything should be exactly the right size.

Syndroid
Heroic Explorer

Thane_ said:

@Ayndroid: the size of the world is designed and made in 3D, everything should be exactly as the developers intended, in 2D or 3D. That's why I Nvidia 3D Vision work so well all you have to do is convert the game automatically to 3D and just a few things like Shadows or lighting needs to be fixed and you're good to go in general. 3D modelers, like myself, actually use digital rulers and units of measurement when building models. Unless something very strange is happening everything should be exactly the right size.


But that doesn't seem to be the case with Doom3. Either the model designers or the level designers didn't use any type of measurement system. My bet is on both.
I made a few models and designed a few maps myself for several mods on different engines since 15 years ago. I too haven't used any measurement system back in the day. But yeah, I'm not a professional and I never modded Id Tech engine 4, so I can't comment on that..
Anyway,  a can in Doom 3 has roughly the same size as a human head, And the level geometry itself isn't always 100% believable either. ^^
Stuff like this isn't as noticible on a 2D screen than it is in VR.

But again, it isn't gamebreaking bad in this case. It's just noticiable if you're looking for it.