search

KozGit / DOOM-3-BFG-VR

Doom 3 BFG VR: Fully Possessed. Doom 3 BFG with native Oculus Rift/Touch or OpenVR support
GNU General Public License v3.0
372 stars 52 forks source link

Where is the version v0.022? #258

Open danylopez123 opened 6 years ago

danylopez123 commented 6 years ago

I only see the installer for v0.021 on the releases, im confused

sycspysycspy commented 6 years ago

0.022 is only a fantasy.

CarlKenner commented 6 years ago

Currently, you would have to build it yourself using the code here on GitHub. Sorry. And it's not quite finished yet anyway. I think Samson still wants to work on the hand pose animations or something like that.

KozGit commented 6 years ago

0.022 is only a fantasy.

https://youtu.be/vPQgfaB3S1c?t=5

jdawgzim commented 6 years ago

Beware of the feature creep. It's gotten hold of Half-Life 2 VR also

jdawgzim commented 6 years ago

What happened to that release that was coming out last November?

Midnightmaster commented 6 years ago

It was eaten by the Decembear...

sycspysycspy commented 6 years ago

We should skip v0.022 cause it's too good to be released and directly go to 1.0.

Slinkywinky commented 6 years ago

much disappointment

jdawgzim commented 6 years ago

Very quiet over here. Everyone enjoying SkyrimVR too much?

Midnightmaster commented 6 years ago

:-) 36 Hours in the last 2 Weeks 12 Hours Playtime 24 Hours Tweaktime

motorsep commented 6 years ago

@sycspysycspy whether I express my concerns or not, the circumstances won't change

KozGit commented 6 years ago

Look, I know it's taking me forever. I'm not dead. The project's not dead. I've done a lot of work since the last release. ( Even the last test release )

For those waiting patiently, I really do feel bad for how long this is taking. Some of these changes are turning out to be much more time consuming than I thought.

I can't give a timeline, but there are 3 things I want to finish before the next release.

1) Changing how the hands work. Most of the complex stuff is done, but still some work to do. This is where all my time is going now, and is the last significant change before release.

2) Updating the menus to support the new features/changes. This is tedious grunt work but not very hard. ( Shouldn't take more that a few days max. )

3) I would like to figure out what is causing the crashes at launch some people are experiencing. I can't reproduce this issue locally, so I'll need to find a volunteer who doesn't mind letting some strange guy from the internet remote into his PC to troubleshoot this issue. Estimated time - ?????

Once those three things are finished it will be released.

Thanks :)

jdawgzim commented 6 years ago

Everyone can contribute. Even if you're only skill is to compile the latest build and find reproduce-able bugs for the devs. No coding skills needed. :-)

KozGit commented 6 years ago

I normally hate deleting comments, but this thread was getting a little off tangent and a little boisterous, so I cleaned it up some. ( Including my own comment ). No offense intended to anyone who's comment was deleted.

I would just ask everyone to try to keep on topic and remain civil. Thx!

Nordomus commented 6 years ago

I really hope new version will come out soon. I've played previous VR mod(from different author) but was unable to finish it due to bug in hell :(

ubergeekseven commented 6 years ago

I have the crash on startup issue. I can set up a remote session at some point for you. I keep trying to get this working but cannot. I have revive installed with oculus as well as steam vr and wmr. I have not tried to use this with the vive only, just the wmr headset. When I launch, it starts oculus vr for some reason I cannot figure out. Nothing else launches oculus when starting. But it also starts steam vr and most of the time steam vr server crashes at that point. The error it throws is compositor error: 105

I have followed the exe install directions as well as the zip. I was able to get the dual screen to show up on the monitor at one point, and the head movements worked to select on the main screen, but nothing through the hmd. That happened 1 time. So I thought I was close. No go yet though.

I have 2 machines, the one I am currently using is a lenovo yoga 720 with an intel gpu, 1050 gpu and a 1070ti egpu connected. I think I saw a post from someone at some point, mentioning having mulptiple cards on the machine. My desktop only has a 1070 in it. I just had time to mess around yesterday, so I tried to get it working on my newer setup on the laptop. I can try on the desktop and report back, but this egpu setup is pretty awesome, especially with the wmr setup. Easier to transport and the resolution is very nice compared to the og vive. Makes me want to get the pro. Especially with the new ar stuff. But now that microsoft finally got the headset working after releasing in october, I want to give it a fair try. It sucked until last week. Sucked.

jdawgzim commented 6 years ago

Last commit Oct 16, 2017 when KozGit said 22 was releasing in a few weeks. I'll go cry myself to sleep and dream of demons.

Midnightmaster commented 6 years ago

What are you waiting for? The trial version of v0.22 works great and should be sufficient until the final appearance. Really great what was done here runs better than most games created specifically for VR. Have a little patience, the new version should appear in any case before Half-Life 3!

cercata commented 6 years ago

@Midnightmaster Where is that Trial ?

Midnightmaster commented 6 years ago

It says v021a but it´s the 022 Version. It´s only a very early test version of 0.022!!! https://drive.google.com/file/d/0B-_8Q_oQABjLX0liZEppdVgxVUU/view?usp=sharing

I think you need files from 021a to use this!?!?

KozGit commented 6 years ago

I have the crash on startup issue. I can set up a remote session at some point for you. I keep trying to get this working but cannot. I have revive installed with oculus as well as steam vr and wmr. I have not tried to use this with the vive only, just the wmr headset. When I launch, it starts oculus vr for some reason I cannot figure out. Nothing else launches oculus when starting. But it also starts steam vr and most of the time steam vr server crashes at that point. The error it throws is compositor error: 105

In the current build, the .exe first checks to see if there is a rift present via the oculus runtime, then if no rift is found it initializes SteamVR. ( Oculus changed things so home always opens now when that check is run). Obviously, there is potential for Revive to get confused when this happens, but again haven't tested yet. The upcoming version has a command line switch you can use to force select which API you want to avoid this issue.

Also, the WMR controllers don't work perfectly in the current version. Not sure if you can re-map the behavior thru steam, may be worth trying. I haven't had a chance to look at that code yet, but I think I saw were someone else had fixed it in a fork.

I very well may take you up on your offer for the remote session. If it's OK with you, I'll reach out when I'm done with the changes I'm working on to try to arrange a time. Do you by any chance have visual studio installed? If not, I can post a short list of things to install for the dev environment.

Thanks!

jdawgzim commented 6 years ago

Doom 3 BFG 66% off at GoG.com
https://www.gog.com/game/doom_3_bfg_edition