I agree. 4.37 with 8K is so great, there’s no way back to “2D”-BMS for me.
Posts made by Pitbull
-
RE: Pimax 8K rocks in 4.37 - Or how to solve the issues with it!
-
Pink screen
I‘m also using the Pimax 8KX and so far, it‘s so amazing playing BMS in VR.
But sometimes, mostly on the ramp, when I turn the head at certain directions I get a pink screen either only on one eye and when I turn further the complete screen gets pink and sometimes I even get a CTD. If I turn back my head to a previous position, the pink screen disappears. It happens mostly in campaigns so I guess it‘s linked to the amount of ground traffic, but so far I cannot say what causes this problem.
Has anyone the same issue and maybe a solution?Cheers
Pitbull -
RE: Problem with custom "IVC Client.ini" … i'm lost
I agree that the option “outsiders=all” actually makes no sense if you were connected to an online mission. I have never tested the “new” workaround without the “IVC Client.ini” file present, since it always works as desired the way I described it earlier.
For me the option “outsiders=awacs” is not very useful, simply because I don’t want to have any range limitation as AWACS operator, so it’s easier for all pilots (they always can hear AWACS) and the TE builders (they actually can place the AWACS aircraft wherever they want).
Maybe I can do some tests in my LAN with the different IVC Client.ini settings and for sure I will post my results here.
Did you also have IVC Crashes with the newest procedure?
Cheers
Pitbull -
RE: Problem with custom "IVC Client.ini" … i'm lost
The procedure you have used is outdated and I have posted a new procedure in a later post. Sorry for the misleading two procedures (I have deleted the old one now).
The correct procedure is as follows:
- set “outsiders = all” in the IVC Client.ini file
- start BMS and connect to the host,you have to select “Enable IVC” in the Comms window
- select the online-TE and go to the 2D-World
- change to the IVC client and select the option “Force Local Control”. The IVC client will disconnect automatically. Connect again and set the desired frequencies again.
- leave BMS in the 2D-World
- start F4AWACS
Cheers
Pitbull -
RE: Problem with custom "IVC Client.ini" … i'm lost
Yes, only for AWACS/ATC.
-
RE: Problem with custom "IVC Client.ini" … i'm lost
We have tested it yesterday and I can confirm that it works as described in my last post.
Cheers
Pitbull -
RE: Problem with custom "IVC Client.ini" … i'm lost
Yesterday we wanted to test the procedure in a mission with our squadron and unfortunately the IVC-clients crashed again . So I did a retesting tonight and found out, that the procedure I have described above is wrong.
After several successful tests today I am now convinced that the following procedure works for AWACS operations:- set “outsiders = all” in the IVC Client.ini file
- start BMS and connect to the host,you have to select “Enable IVC” in the Comms window
- select the online-TE and go to the 2D-World
- change to the IVC client and select the option “Force Local Control”. The IVC client will disconnect automatically. Connect again and set the desired frequencies again.
- leave BMS in the 2D-World
- start F4AWACS
It is important, that you follow the procedure exactly as described above. If you start IVC client as standalone first, it won’t work.
Cheers
Pitbull -
RE: Problem with custom "IVC Client.ini" … i'm lost
Yes, the sequence is only for the AWACS operator, except the ini file. All clients need to have to place the ini-file with the outsiders option set to “all” in the …\bin\x86\IVC\ folder.
Pitbull
-
RE: Problem with custom "IVC Client.ini" … i'm lost
I think I have found a solution for this problem, or let’s call it a workaround.
If you set “outsiders = all” in the IVC Client.ini file, the AWACS/ATC operator has to be at least in the 2D-World and connected to the multiplayer-game. Then the other clients won’t crash and you can transmit as ATC/AWACS via IVC with no range limitation.
Find below a step by step description of my successful testing today. I will test the whole thing next week with our squadron and hopefully it will also work with more than just two clients (as in my testlab).
PROCEDURE DELETED -> see later post for correct procedure!!!
Cheers
Pitbull -
RE: Problem with custom "IVC Client.ini" … i'm lost
I have tested this issue intensively because we have the same problem here. If you have an IVC Client not in the 3D-World and the option “outsiders = all” is set, either by ini-file or command line, all 3D-IVC-Clients crash as soon as the “standalone” IVC starts transmitting.
IVC Logs weren’t very helpful, since the logs stopped at the crash and didn’t show any error.I did also some testings with all clients in 3D-World and the option “outsiders = all” was set. I expected that with this option set on, you can hear each other even if the distance between two aircrafts was very big, but you couldn’t hear anything. Maybe I didn’t understand exactly what this options effects in IVC.
Hope we can find a solution for this “bug”, since human AWACS is so vital especially in complex missions and I wouldn’t miss it.
-
RE: MP: all jets flameout and deepstall suddenly
No crash at all.
Pitbull
-
RE: MP: all jets flameout and deepstall suddenly
I’ll pick up this thread because we still have this strange deep stall issue in multiplayer games.
Tonight we did a mission with 5 clients connected to a dedicated server and shortly after take off, all (human) aircrafts went into a deep stall. Server was in 3D.
We switched then to another host (one of the clients was hosting the game) and the mission went perfectly.
It looks like it’s not a bandwidth nor a weather problem.
Fortunately I was able to take logs on the dedicated server and at the time the deep stall occurred, the logs had following strange entries:
Pitbull