vorpX impressions

I’ll have to dig up a Falcon 4 version. I had a disk once. And I bought F4:AF…I’d be lost on how to install BMS (or even find it)…but I’ll give it a whirl tomorrow…

1 Like

Look what I found in a drawer next to my desk!

5 Likes

dance1

https://www.youtube.com/watch?v=AjPau5QYtYs

3 Likes

I might need some WD40 to get this thing to spin up…

1 Like

FALCON-001

crazy1

4 Likes

Should I register for product support? :thinking:

FALCON-004

2 Likes

Fill it out, print it on the dot matrix and then fax it?

2 Likes

Where’d I put my 300 baud modem and WinFax Pro??

1 Like

Don’t forget to install the new Trumpet Winsock package if you’re going ‘online’.

1 Like

Don’t forget to load your QEMM memory manager. :slight_smile:

You’ve got my attention now with BMS. What about 4.34?

2 Likes

Whew…there went a couple hours. Heading to bed but here is the long and short of it.

Falcon 4 BMS install went fine:

Falcon 4 (original CD)
BMS 4.33 U1 Setup
BMS 4.33 U2 Incremental
BMS 4.33 U3 Incremental
BMS 4.33 U4 Incremental
BMS 4.33 U5 Incremental

Up and running, but couldn’t figure out why I couldn’t get full screen 3440 x 1440. The 2D menu is always smaller…I think it is hard coded, but when you launch into 3D (not VR 3D) it should fill your screen. Well, mine wasn’t until I checked this:

With that box checked, I was able to run in regular 2D at full resolution. Now, trying to hook vorpX has been a whole different affair. I’m had varying success with it. But only when I have the above setting unchecked, which puts my screen resolution at 1024 x 768 in VR. You also have to use OpenTrack…but it DOES work. I went through every combination of check boxes, admin rights, and launching orders to try to get VR at high resolution, and I just can’t get it…I’ll try more tomorrow…

Apologies for the mouth breather imitation…was holding all my stuff right up to my face trying to get my phone in the right spot…

4 Likes

Mon Dieu! You were up all night. Decisions, decisions…

:see_no_evil: I see now there is a 4.34 full installer and two updates. I’m switching to that build this morning and will report back.

4 Likes

Spent all morning with 4.34 and could not get vorpX to “hook” to it. I may go back to 4.33 to dabble since I did have success with it.

1 Like

Since VR grabbed me I’ve not touched F4-BMS. Shame, I know; I didn’t really fly DCS ‘back then’. I’ve not un-installed it hoping somehow it would be VR’d. Looking forward to your report, and digging into the washer/dryer for $40 bucks…

That’s a bummer. We all appreciate your doing what must be hair thinning at times.

I’ll probably not spend a huge amount of time sorting this out, but I’ll be sure to ask about it over on the BMS forums. Going back to 4.33 resulted in the same outcome so far. I can get BMS to run at high resolution in 2D, but it will only run in VR at the lower resolution that results from leaving the “disable full screen optimizations” unchecked. Checking that box will let me load to the BMS/Falcon GUI where you select missions, and settings, but once I start a mission the headset goes black even though I can hear the game playing and responding in the background. It’s almost like vorpX can’t handle the change from the GUI menu to the gameplay resolution.

I’ve tried all manner of compatibility modes, G-Sync, V-Sync, resolutions, and refresh rates but I can’t make the breakthrough to high res AND VR…only low res and VR.

If anyone had any further suggestions on that…I’m all ears. I will try a few more vorpX profiles on it tonight, but I don’t think it is a vorpX problem…

Thanks for the work. Based on a search a few weeks ago that’s kinda what I expected; some responses at BMS forum made it sound like they have no intention to ever make it VR. Probably cuzz of the underlying engine/API I’m sure.

Quite a few people have tried getting BMS to work over the years with different VR headsets and different ways including VorpX. There is one thread going back to 2016.

Some of the Devs have posted over the past year or so that VR is something they had talked about and hope to implement in the future…but we will have to wait and see if that happens.

More testing…still have not cracked the resolution issue…