-
Posts
336 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by diamond26
-
-
10 hours ago, Gryzor said:
Performance it seems to me lower with 2.9.4.53549
At least with the F-18, I have in VR an average of 1,5 ms more (from 7.8 ms to 9.4 or 9.5...)
Anyone noticed this?
Yes I witnessed the same. It's a bit lower with 2.9.4. Nothing else though (stutters or bad artifacts)
-
On 2/23/2024 at 11:30 PM, chase said:
The other strange thing was Texico was refueling anther tanker upon Wakiki. Which you can imagine takes forever. So I just by passed
it and went to the boat. I never saw this before, so I figured it's a bug
@baltic_dragonI flew the mission last night and this behavior is still there. Obviously I went directly to the carrier but it will be nice to have it resolved next time you revisit this one.
-
11 minutes ago, Jenson said:
The AI keeps chasing issue should be solved now, just revised trigger rules to let them return when all Players fall back into a safe zone.
You are right on the Tanker as well, it's too close to the enemy forces, however, I also received feedbacks from other players that they thought the tankers are too far (for some other missions) and it takes too long for a refueling job. I agree that this is not practical to place the tankers so close to the frontline, but I still decide to keep them there just to make the missions easier to play.
Thanks for the update.
The Tanker topic is a matter of reality vs game play. If people want an easier play then I understand the slight disortion of reality. At least we managed to get refuelled without being shot down!
-
@Jenson last night we flew the remastered M10 (thanks again for keeping this campaign updated). We noticed an issue with AI DCA. They followed us in our return till the carrier and actually we had to enable one of them as he got too close. Carrier group then took care of them while we were performing our CASE III recovery.
Note: Texaco 1-1 seems to be too close to enemy forces ( there was a point that the tanker was 45 nm from the enemy)
-
12 minutes ago, Maddaawg said:
how does blocking in on a PC keep it from updating?
The guidance was only to block Oculus PC app to go to V63.
For the headset, apart from what you suggest (which I haven't tried) the only option is to keep wifi off
In addition the headest updates if you have SW updates off are enforced after some time. For example v62 in my case has a mandatory enforcement by 28/3. So I guess you are safe in headset with SW updates set to OFF even with wifi on for some period of time which will be mentioned by META. -
1 hour ago, Hoirtel said:
Do you create a folder called staging? same for tmp
I only created a bak.staging (actually renamed an existing folder) and a bak.tmp folders and it worked as suggested by @Lange_666
-
6 minutes ago, VirusAM said:
(can't find a way to stop the auto-update but I am safe for now)
what about this suggestion :
-
I have also mentioned the issue to META in their support page (not that it matters too much as they use AI for response! )
-
I'm coming back on this topic of low VR performance.
F1 on a low spec machine (like my laptop with an RTX2060 6GB) is definetely not playable in VR compared to other models.
Using Link (Quest Pro) and the same settings the difference between F-15E (heavy also in VR) and F1 is 15-20 fps which brings the F1 down to 9-10 FPS
Using Virtual Desktop F1 is a bit better with 20-30 FPS.
This means that F1 is making more aggressive use of VRAM.
And to give you a more startling comparison, F-18 free flight in the same map is averaging 50-60FPS!
-
-
Same problem as OP witnessed today. Map is functional but getting the message to install it.
-
On 2/18/2024 at 11:33 AM, freehand said:
I've not yet had any major issues with oculus cable link
Me too, Oculus Link provides better quality and stability and ASW is miles better that SSW from VD. VD seems to help when I use my laptop as the VRAM is limited and the VD's VRAM use is better compared to Link.
8 hours ago, nikoel said:I believe the issue might be that you haven't selected the "Pass face-tracking to PC" option in the Virtual Desktop VR menu settings. (I am paraphrasing the name, not in front of my PC right now)
That's a requirement for eye tracking to work for VD and Qpro. I imagine won't do anything for Q3
- 1
-
On 2/14/2024 at 12:51 PM, 7Coolhand said:
How do You disable the quad view for testing performance ON/OFF?
is there a settings to just disable this tool?
Have bought a new GPU and want to do some testing.
According to Mbucchia's guidance the QuadViews can disabled through STEAMVR settings
https://github.com/mbucchia/Quad-Views-Foveated/wiki#temporarily-disabling
-
15 minutes ago, Jenson said:
I have checked the mission editor and the setting is okay, CVN-71 carrier will activate ICSL on channel 11 at the start of the game. I don't think it's the trigger zone bug because this activation is not linked with any zone. Just a kind reminder, make sure you are communicating with CVN-71 rather than CVN-73, and make sure you have boxed the ILS on HSI.
In M06 everything worked as designed. ILS was present from start to finish (also in the yellow kneeboard page unlike the previous times) . And indeed we were talking in all three missions to CVN-71. Not sure where the problem was.
-
@Jenson in the last two missions that had Case III recovery (M03 and M04) we didn't have ILS available. When you join the mission you can see in the kneeboard for a moment the ILS 11 but then it dissapears. Is there something I can do to make sure ILS is working or it's part of the trigger issue? We are planning M06 tonight which is also CASE III recovery.
-
5 hours ago, Jenson said:
Thanks for the feedback again, me and my squadron guys had played this mission about 1 month ago and ILS was working, channel is 11, but I will double check later.
BTW, I assume the DCS game is still bugged with the trigger zone entry detection, just wondering how did you make this mission work?
Yes we were on CH 11, but nothing seems to work for all 4 of us. I noticed that the usual yellow kneeboard page didn't have ILS noted.
we had the same question regarding triggers but it seems that the system sorts itself out after passing a trigger or two.
For example both in M02 and M03 while on carrier we were receiving information not relevant to our stage but for M02 as soon as we were out of 10nm (the trigger for AI launch) and after Rock in M03 things became normal and we had all he info that usually provided in the different stages like the tasking or the shot down of Colt 1-2 etc. In M03 we were not given Other options until return to WP5, 6 for enabling tanker. (I don't know if you had more earlier)
-
Hi @Jenson we are enjoying your missions and we plan to complete the full campaign. Tonight we flew M03 which was really good fun.
One comment in the remastered version is that despite ILS was mentioned in the briefing, that wasn’t available in the mission which made our CASE III recovery challenging. -
Hi @Jenson thanks for this nice work.
I have a small comment regarding the remastered Mission 02. We flew it in my Squadron with 4 guys flying the Hawk 1 and we let Hawk 2 on AI. We received the updated F10 for the AI and I ordered them to launch TALDS. We got the response in the menu about launching phantom planes but the AI fired HARMs instead.
Additional tasking worked nicely. -
I'm using as a backup a laptop with RTX 2060 6Gb and I was able to enjoy Q2 with some limitations. First you have to reduce Textures and Terrain textures. MSAA 2x is taxing on old systems but if you can't use DLAA then you have to bear the cost. You can also try the OpenXR toolkit options for upscaling (NIS, FSR) to reduce the total pixel load.
You can also try reducing FoV setting in ODT or OTT if you use that. A figure of 0.75 will help a lot without sacrificing too much of actual view.
In any case don't expect high FPS when you aim for clarity. The max I got with the laptop is 50-55 FPS in multiplayer using Quad Views and Quest Pro. Normal figures are around 30-35 FPS
-
Problem solved by deleting the DCS.openbeta_server folder in Saved Games! Thanks to Yoyo from Discord
-
Since the last update I cannot see through GUI the dedicated server. Something is wrong with port 8088 or something else. I have tried full repair, checking port forwardings, firewall settings (although I had no issues in the past) to no avail.
I've seen the same issue was mentioned in the forums back in 2019 but no solution was given.
Any ideas?
-
1 hour ago, Hiob said:
I'm just asking, because the ghosting in general seem to get better with higher fps and worse with lower fps. But that's just an observation of mine. Can't really back it up. I was just interested in more data points.
I can confirm the same. Coming from my laptop back to my PC I noticed a difference in the level of gosting ( max 50 fps on laptop, steady 72 on PC)
-
17 hours ago, slughead said:
Get the Globular Cluster Comfort Kit. It solved all the comfort issues for me. I just use the replacement pads and haven’t used the strap.
Completely agree for Globular kit
-
2 hours ago, zhaohaob88 said:
The interface of the new version is really too cluttered, for people like me who are not good at English, I have been looking for 30 minutes now, and I still can't find a place to load the dcs path 555555555
Here
DCS Patch notes discussion April 2024
in DCS 2.9
Posted
here are two test on my system with Qpro (using Quad Views) and process lasso to distribute better the cores' workload
null
nullnull