-
Posts
84 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Bingo41
-
Thanks to both you gentlemen, I tried both methods and they worked. Bill Clark
-
In the attached image I have a bunch of information that shows up in the HUD I would like to delete. Any suggestion on how to get rid of this, not even sure what it is? Bill Clark
-
[REPORTED]Stennis Carrier Lights Do Not Work at Night
Bingo41 replied to Bingo41's topic in Object Bugs
Kang, I set the time to 23:59, and red runway lights did not come on. The green lights outlining the entire carrier deck are lighted, but no runway lights. They should work at this late hour. Bill Clark -
Hi, I have been unable to turn on the lights at night on the Stennis Carrier. Using Freq 127.5 and stating "Inbound" does not turn on the lights. I thought this used to work? Bill Clark
-
A few months back I remember hearing that there was a fix in progress for a bug or limit on frame rates because of scenery issues. Whatever happened to that effort? Bill Clark
-
DutchCoolHand, Thanks for your response. I have done the same thing in the past as you have with mouse clicks. I just wonder what the underlying cause of this issue is? It is sure frustrating! However, I have the check box selected "Cursor Confined to Game Window," in the VR section of the options menu, which prevents the mouse from leaving the desktop monitor window? Possibly, the fixes that Wags mentioned recently to modifying the various scenery packages to improve VR, may fix this issue.........its a hope I have? BTW - my headset is the Oculus Rift CR1 I picked up in early 2018. Bill Clark
-
Hi, Sometimes when flying in VR, my keyboard is locked out, none of the key presses work. My HOTAS Cougar is setup to send key presses, and it is locked out as well. The axis still work, however. The only thing that appears to work is CTL ALT DEL. Any ideas on what may be causing this? Bill Clark
-
F-18 Crash in VR Here are the log files from my Crash in the F-18………….the crash occurred after 10:34 min/sec of flight. The length of time can be random prior to crash. It will crash consistently 100% of the time. Bill Clark dcs.log-20180803-201919.zip dcs.zip
-
Sandman, Yes I tried ALT + c, and it didn't help. I finally did a cleanup and repair and that solved my problem with the mouse. Bill Clark
-
Sandman, Mine has the issue 100% of the time. Bill Clark
-
Hi, For whatever reason, when I press F2, and I attempt to pan around the outside of the F-18, the view remains fixed. However, when selecting the A-10C, I can pan around the outside of this plane when I press F2. It appears this issue only applies to the F-18? Bill Clark
-
Hi All, Looks like I am back, unfortunately update 2.5.1 did not fix my crash issue. Both 2D and VR modes crash after a few minutes. Unlike before in 2.5.0, I could set Deferred Shading and Vsync to ON and DCS would not crash. However, under version 2.5.1, if Vsync is ON, the sim now crashes as Deferred Shading is built in and can’t be turned off. So my workaround no longer works. Basically DCS is no longer playable with 2.5.1. Attached are a couple of log files. There are other new log file types that appear to be new with 2.5.1, let me know if you would like these uploaded? Bill Clark dcs.log-20180425-204841.zip
-
Joy_Button Commands not working for guns and ordinance
Bingo41 replied to Bingo41's topic in DCS: F-86F Sabre
Rudel, Yes, I run in Emulation Mode. You are correct about all the JOY_BUTTONS................I will fix them. Thanks a lot, don't know why I assumed that...........just tested on the Foxy Joystick tester to confirm. Bill Clark -
Below, I posted this is the Crash Forum, but thought the VR test information might be useful to some of you who fly VR. ------------------------------------------------------------------------------------------------- Up until recently I was able to run DCS in VR and 2D modes very flawlessly, that is, until this issue cropped up. I have no idea what happened? Currently, I am running P3D version 4.1 with both “Native” VR and the 3rd party add-on FlyInside without any issues….it runs really well, so there is nothing wrong with my VR. What I have done is collect some information (FPS and Video Memory used versus 3 different scenarios) that find is unusual: DS = Deferred Shading VS = Vsync FPS = Frame Rate for VR VID = Video Memory consumed MB DS ON, OFF, ON VS ON, OFF, OFF FPS 30, 45 or 90, 45 VID 12,410, 8,498, 12,559 Comments: 1) The only scenario that crashes is when Deferred Shading is ON and Vsync is OFF. 2) The other two scenarios work without crashing. 3) When DS and VS are OFF the video RAM numbers look reasonable as do the frames, the other two situations exceed my 1080TI memory of 11GB……what causes this? I hope the Developers are working on a patch or update to fix this. And as a workaround for VR, I can fly with either DS and VS turned ON, or just turn off DS. Bill Clark
-
Hi, I have a Cougar HOTAS that is working well for other DCS aircraft, but not the F-86. I have assigned JOY_BTN1 and JOY_BTN2 to my dual trigger, and I have assigned JOY_BTN3 to the weapons release button on my Cougar HOTAS Joystick. These three exact Joy_BTN's work for the F-5, for example. The trigger only fires a single shot (JOY_BTN1 or JOY_BTN2) and the bomb release button (JOY_BTN3) does not launch the rockets. The key press for the trigger is the "space bar" and and the weapons release can be done by "RALT + SPACE." These key presses do work. Bill Clark
-
Flappie, Up until recently I was able to run DCS in VR and 2D modes very flawlessly, that is, until this issue cropped up. I have no idea what happened? Currently, I am running P3D version 4.1 with both “Native” VR and the 3rd party add-on FlyInside without any issues….it runs really well, so there is nothing wrong with my VR. What I have done is collect some information (FPS and Video Memory used versus 3 different scenarios) that find is unusual: DS = Deferred Shading VS = Vsync FPS = Frame Rate for VR VID = Video Memory consumed MB DS ON, OFF, ON VS ON, OFF, OFF FPS 30, 45 or 90, 45 VID 12,410, 8,498, 12,559 Comments: 1) The only scenario that crashes is when Deferred Shading is ON and Vsync is OFF. 2) The other two scenarios work without crashing. 3) When DS and VS are OFF the video RAM numbers look reasonable as do the frames, the other two situations exceed my 1080TI memory of 11GB……what causes this? I can’t see where my video card is producing too much FPS, and it certainly is not enough when Deferred Shading and Vsync are ON. As to accessing this hidden NVidia panel, the only thing that I can think of is Nvidia Inspector? I hope the Developers are working on a patch or update to fix this. And as a workaround for VR, I can fly with either DS and VS turned ON, or just turn off DS. Bill Clark
-
Flappie, I flew in VR with Deferred Shading ON with SYNC turned OFF, and after a short period of time it crashed. With Deferred Shading ON and SYNC ON, VR works with the following caveat, there is a jerkiness that wasn't there before when I had SYNC turned off. This is sort of a workaround for now, but not what I had prior where it was super smooth! Bill Clark
-
Yes, a constant reminder to be a "good boy," Heh, Heh! Bill
-
Flappie, With both Deferred Shading and VSYNC checked I was able to fly for 30 minutes without a crash. Because I fly primarily in VR, I'm not absolutely sure you can check VSYNC box and expect VR to work. I'll will check that out later today or tomorrow. However, VSYNC seems to fix the crash situation in 2D mode on my particular system. I am still curious about the difference Deferred Shading has on video RAM usage? Bill Clark
-
-
Flappie, Will give your suggestion a try this afternoon.............had to deal with company all weekend! BTW - this "Warn" thing keeps popping up every time I post, can you fix this permanently? Bill Clark
-
Hi All, I did an experiment and collected what I think may be interesting data. Attached is an image of my current DCS settings with Deferred Shading turned OFF. However, at the beginning of this thread, when I had Deferred Shading turned ON, I was getting a crash 100% of the time. Typically, the sim would crash somewhere between 1:48 minutes and 3.12 minutes when I was flying free-flight Instant Missions. However, when I turned OFF Deferred Shading, I was able to fly at least one of these Instant Missions for 30 minutes before I terminated the mission. Presumably I could have continued much longer. I also collected the following data for both Deferred Shading ON and Off: Deferred Shading Off: Video Memory = 8,742 MB Frame Rate – Between 160 and 170 FPS Deferred Shading ON: Video Memory = 12,4280 MB Frame Rate – Between 70 and 80 FPS By the way, I have a GTX 1080 TI with 11GB of RAM and my system Ram is 32GB. So I was quite surprised, given my current settings, that the video RAM exceeded my 1080TI capacity. I will play around with my settings to reduce the video RAM usage below the GTX 1080TI 11GB threshold to see if I can run with Deferred Shading ON? What do you all think? Bill Clark
-
Hi, Where is the FOV setting, in DCS or an Nvidia setting? Bill Clark
-
Hi Moderators, I see a 0% Warning under my name................what does that mean, did I do something wrong? Bill Clark
-
Flappie, One of the problems for us flight simulation guys, is that this hobby is a very small niche compared to the rest of the gaming world. I believe the only people who may have had a limited success of working directly with Nvidia is Lockheed Martin with their P3D version. Being a large aerospace company may help. Getting the attention from Nvidia who focuses on the main stream games is tough? I keep hoping that the DCS developers next release will fix this issue. I have rolled my system back to my older Nvidia driver 388.59, which worked before. I use Macrium Reflect to create a disc or SSD image as the way I back up my installed sims. @Bingo41: Weird. As I was playing IL2-BoK yesterday, the game crashed showing the same DXGI device removed error. It seems like nVidia screwed up with their latest drivers. Still, I haven't seen this error in DCS so far. Bill Clark