Sirbum

I will say that before this patch I would run my crystal in 72HZ mode and was doing fine in that it always pegged 72, If I tried to use 90 it would hover in the 80-85 range so still was not bad but would not stay at 90. Now, I just tried it at 90 Hz because I forgot I had changed it trying to get quadview to work in the last update and I was pegging 90 the whole entire flight. never changed anything graphics wise from before, so they obviously did something good that changed how the pimax works. Im elated with it. Hell I may even try 120 just for giggles, all though with a 4070TI I dont assume it will be able to run that, but I am happy with 90 as 72 was even fine with me.

I won't take it personal lol, But I assume he won't get any answers beyond what I posted in a non attacking way

on the launch screen where you click play, does it show a monitor icon or VR goggle Icon. May be that its showing monitor so its going straight into monitor.

I am hoping maybe someone can tell me what the reason is for DCS crashing anytime I try to use DLSS. With out DLSS I can run the game for hours in VR with no issues. I mean I even have decent FPS 70-85 FPS most of the time. I just figured I would try DLSS to see if I could get 90 all the time. But no matter what I have tried, as soon as I enter the three D world, It will either crash right away or will crash with in 5 mins. I have tried underclocking my GPU, not changing my GPU clocks from stock. I have went and removed reference in the register for OpenKneeboard, which broke other things lol, I even just tried cleaning out my FXO folder and still it crashes. I have a 4070TI with the latest drivers. I have even tried using the studio drivers instead of the Game ready ones and still crashes. Attached is my log. I see a lot of errors in there, but they seem to all be with the F15 plane. But this happens in all planes. Oh, and it doesn't matter if I try in non multithreading mode or MT mode. I have even tried the process lasso thing where you limit the cores. dcs.log dcs.log-20231122-204414.zip

I have the exact same card and can usually play for ever with no issues unless I turn on DLSS. Soon as I do that I will crash every time with in 10 mins. So, if you are playing with Dlss try turning that off and see how long you can play. I have not been able to figure out what causes DLSS to crash, I have tried with and without overclocking and no change.

The reason your ASL line is not matching up is because you are using MK82SE, drop them below 750 MSL and you will see that your line is where it needs to be. I believe i read that this is not intended but for now it only happens when using a re-tarted bomb with chutes or the durandals

Exactly the same for me. Funny thing is, I never had this issue until the last patch, now i am not able to even switch to the AG radar with out instant CTD. So something messed it up worse lol. As for cores I have not messed with that because I did not have an issue with wha they are set to now before.

press the castle switch in, another words go find the bind for cast depress and bind that. they make it sound like castle down then castle down again but its down then depress.

with the durandales you have to be less than 750 AGL. I posted this same bug in this fourm a few weeks back, and was told about the 750 AGL. Another words anything that is retareded needs to be dropped low in order for the line to work correctly. Is it intended this way? not sure but it is how it is

Running a G2 with an RTX 4070TI and I get 90FPS with openxr tools set to 100% and 1.0 PD in game. Fluid as ever. Also that is using high on most things with 2xmsaa. Once in awhile it will dip to 80 but for the most part its golden. Only really see a dip when using anything that is green screen. Like the Tpod or TSD on one of the screens above. Or if using NVG's.

oh i was, but it still shouldn't have hit as if the laser was firing?

I have had it happen a few times, that even though I go to the back seat and arm the laser, it will still say its safe even with master arm on, target designated and ready to go. So this time i figured what the heck and dropped the bombs anyhow. And no laser fired but....The bomb hit exactly where i was targeting. So I redesignated another target, and noticed that now the red laser arm was on and it said it in the Tpod. So seems that for some reason the Tpod will say the laser is safe, and the laser arm light wont be on, but the bombs still act as if the pod is firing the laser.

also do not remove the wheel chocks or disengage the breaks at all during the alignment. I removed the wheel chocks while it was going and it reverted to the very beginning and I had to restart the mission due to it hanging.

Thanks i saw that. Going to leave this here for now though as it may be a bug.

oh yes i was trying to use 107 durandles. I did not know you have to be below 750. Guess im off to try this again. TY Rain.

Seems when ever i try to use CDIP with BLU-107 durandles the Pipper stays attached to the horizon line and my FPM move down when im in a dive with a line attached to the Pipper. So, even if I say place the pipper on a spot on the ground, the bombs fall way short. Something is a miss with the CDIP.

I have had this same thing happen to me, I am thinking this is more of a bug. I designated a spot on the ground with Tpod, when out and around and the line stayed way off to the right side of hud, even though the Triangle was right in the center of the hud. Soon as the countdown got to zero nothing, bombs would come off because i wasnt on the Vertical line and no Horizontal line fell. This was after I had intially done a bombing run with no issue. So seems to happen, when you redesignate a target. I am also having the issue when I pick CDIP my pipper never goes below the horizon, even in a dive. The FPS does though with a line running from it too the pipper.

Yes, It was updated before I even bought the Plane. Something happened that messed up one of the files. Soon as I replaced the updater file it downloaded just fine.

i noticed yesterday the same thing, being i was having issues installing the new plane and had to keep restarting dcs it kinda sucked.

yeh i was able to get it to work but for what ever reason the binds dont seem to work correctly. one time i can swap from front to back and then back to front and the next time i get stuck in the back as it wont swap me back lol.

this was in a training mission Rudel_chw

Its suppose to be number 1 and number 2 but doesnt seem to work in VR

I tried using #1 and #2 on keyboard with nothing, so i then bound the switching to my hotas and still nothing. So not being able to switch in VR means i wont be able to turn on the Tpod or other items that need it back there.

fixed this by redownloading the updater.exe. replacing the one in the bin folder and running that. Then clicked download and for what ever reason it downloaded the module

fixed this by redownloading the updater.exe. replacing the one in the bin folder and running that. Then clicked download and for what ever reason it downloaded the module