Author Topic: Odd environment issue.  (Read 860 times)

Offline oakranger

  • Plutonium Member
  • *******
  • Posts: 8380
      • http://www.slybirds.com/
Odd environment issue.
« on: February 22, 2016, 07:21:04 AM »
Working on adjusting my settings while in the towar, exit out of the area and adjust the video setting then back into the area.  Sudden found my self in a rage party  :O (minus the people, twirling glow lights, alcohol, drugs).  My screen kept flashing day and night non-stop.  Glad I don't have seziurs.  :bolt:
Oaktree

56th Fighter group

Offline MrKrabs

  • Gold Member
  • *****
  • Posts: 2152
      • AH-Freebirds.com
Re: Odd environment issue.
« Reply #1 on: February 22, 2016, 08:22:07 AM »
Sounds like your video card throwing a fit  :headscratch:

DxDiag is always a must  :old:
The boiling pot is put away and the crab has gone back to sea...

Offline Chalenge

  • Plutonium Member
  • *******
  • Posts: 15179
Re: Odd environment issue.
« Reply #2 on: February 22, 2016, 11:47:47 AM »
This has been a common event when changing resolutions for me. A reboot usually fixes it.
If you like the Sick Puppy Custom Sound Pack the please consider contributing for future updates by sending a months dues to Hitech Creations for account "Chalenge." Every little bit helps.

Offline oakranger

  • Plutonium Member
  • *******
  • Posts: 8380
      • http://www.slybirds.com/
Re: Odd environment issue.
« Reply #3 on: February 22, 2016, 04:27:46 PM »
Quote from: MrKrabs link=topic=377878.msg5031962#msg5031962 date=1456150927

DxDiag is always a must  :old:
[/quote

It was working with ok FR around 40.  Just trying to test on what setting works best.   Umm,  how do I get my DxDiag?
Oaktree

56th Fighter group

Offline The Fugitive

  • Plutonium Member
  • *******
  • Posts: 17934
      • Fugi's Aces Help
Re: Odd environment issue.
« Reply #4 on: February 22, 2016, 04:31:46 PM »
[quote author=MrKrabs link=topic=377878.msg5031962#msg5031962 date=1456150927

DxDiag is always a must  :old:


It was working with ok FR around 40.  Just trying to test on what setting works best.   Umm,  how do I get my DxDiag?

To post a dxdiag,

Click on windows start and type into box dxdiag, at the top of that window click on the dxdiag to start program.

It may ask if you want to check for known drivers or such, click ok and let it run.

After a minute or two it will be done, on the bottom of the new window that opened toward the right side is a button that says "save all info", click it and save it as a ".txt" file on your desktop.... or someplace you can find it.

Close the dxdiag window (your done with it)

find and double click the new file you just made. Copy (click and drag) the top third of the information up to AND INCLUDING "Sound Devices".

Paste it in a post.

You only really need to show the first third, and if you try to post the whole thing it WILL exceed the limit on how much you can post in a single post.

Good Luck.

Offline oakranger

  • Plutonium Member
  • *******
  • Posts: 8380
      • http://www.slybirds.com/
Re: Odd environment issue.
« Reply #5 on: February 23, 2016, 12:22:58 AM »
------------------
System Information
------------------
      Time of this report: 2/23/2016, 16:18:49
             Machine name: LAPTOP-L9DRIHLF
         Operating System: Windows 10 Home 64-bit (10.0, Build 10240) (10240.th1.150819-1946)
                 Language: English (Regional Setting: English)
      System Manufacturer: LENOVO
             System Model: 80NY
                     BIOS: CECN43WW
                Processor: AMD FX-8800P Radeon R7, 12 Compute Cores 4C+8G  (4 CPUs), ~2.1GHz
                   Memory: 8192MB RAM
      Available OS Memory: 7128MB RAM
                Page File: 2245MB used, 6674MB available
              Windows Dir: C:\Windows
          DirectX Version: 12
      DX Setup Parameters: Not found
         User DPI Setting: Using System DPI
       System DPI Setting: 120 DPI (125 percent)
          DWM DPI Scaling: UnKnown
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
           DxDiag Version: 10.00.10240.16384 64bit Unicode
  DxDiag Previously: Crashed in DirectInput (stage 1). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information


Oaktree

56th Fighter group

Offline Bizman

  • Plutonium Member
  • *******
  • Posts: 9606
Re: Odd environment issue.
« Reply #6 on: February 23, 2016, 01:27:37 AM »
Oakranger, that was only the first chapter.

Please include the first third, down to and including "Sound Capture Devices".

Quote from: BaldEagl, applies to myself, too
I've got an older system by today's standards that still runs the game well by my standards.

Kotisivuni

Offline Chilli

  • Platinum Member
  • ******
  • Posts: 4278
Re: Odd environment issue.
« Reply #7 on: February 23, 2016, 03:19:42 AM »
------------------
System Information
------------------
      Time of this report: 2/23/2016, 16:18:49
             Machine name: LAPTOP-L9DRIHLF
         Operating System: Windows 10 Home 64-bit (10.0, Build 10240) (10240.th1.150819-1946)
                 Language: English (Regional Setting: English)
      System Manufacturer: LENOVO
             System Model: 80NY
                     BIOS: CECN43WW
                Processor: AMD FX-8800P Radeon R7, 12 Compute Cores 4C+8G  (4 CPUs), ~2.1GHz
                   Memory: 8192MB RAM
      Available OS Memory: 7128MB RAM
                Page File: 2245MB used, 6674MB available
              Windows Dir: C:\Windows
          DirectX Version: 12
      DX Setup Parameters: Not found
         User DPI Setting: Using System DPI
       System DPI Setting: 120 DPI (125 percent)
          DWM DPI Scaling: UnKnown
                 Miracast: Available, with HDCP
Microsoft Graphics Hybrid: Not Supported
           DxDiag Version: 10.00.10240.16384 64bit Unicode
  DxDiag Previously: Crashed in DirectInput (stage 1). Re-running DxDiag with "dontskip" command line parameter or choosing not to bypass information gathering when prompted might result in DxDiag successfully obtaining this information

Interesting.  The color portion was a part of your Dxdiag text?  Or did you happen to drag that in from your copy of another screen?

By the way, you could attach the entire file by clicking "+ Attachments and other options" mouse over just below your post reply, or as Bizman says copy at least down to sound devices.