v1.0 Waypoint on Compass Goes Awry

[PR0_SNIPE]

OK, so here's the story about this one. This laptop is about 4-6 years old and on PR .981 it wouldn't play with everything on high (~4 fps) so I just kept everything on low and 100% view distance. So I decided to make a video and made everything on high and view distance on 50% so it'd look good. Little did I know that my computer could actually handle it now - which is FANTASTIC. Since changing everything to high (no anti aliasing and 100% view distance [~40 fps]) the waypoint on the compass has gone to somewhat the center of the screen. I look away to a different direction and its mapped to a certain area but moves up and down. Restarting PR, the SL changing the marker and trying different servers doesn't fix the problem. Its still there now. How can I fix this? (pics and system info below)

System Information
------------------
  Operating System: Microsoft Windows 7 Professional  (6.1.7601)
      Architecture: 64-bit
          Language: English (United States)
       Motherboard: Gateway         IMV            
         Processor: Intel(R) Core(TM)2 Duo CPU     P8400  @ 2.26GHz (Physical: 2, Logical: 2)
            Memory: 4.00 GB
      DIMM Modules: M1: 2.00 GB @ 1066 MHz
                    M2: 2.00 GB @ 1066 MHz
         Page File: 3.99 GB
    .NET Framework: 4.0

Display Information
-------------------
 Display Device(s): Generic PnP Monitor on NVIDIA GeForce 9800M GTS   
   Display Mode(s): 1920 x 1200 (32 bit) @ 60 Hz
    Driver Version: 9.18.13.2049 (320.49)
    Display Memory: 1024.00 MB
     Multisampling: 2, 4, 8
               DPI: 96 (100%)

Audio Information
-----------------
  Primary Playback: Speakers (4- Logitech G35 Headset)
 Primary Recording: Microphone (4- Logitech G35 Headset)
               EAX: True
           EAX 1.0: False
           EAX 2.0: True
           EAX 3.0: False
           EAX 4.0: False
           EAX 5.0: False
             X-RAM: False

Disk Information
----------------
      Install Path: C:\Program Files (x86)\EA GAMES\Battlefield 2
                    Free: 151.21 GB, Total: 288.09 GB, NTFS
          Mod Path: C:\Program Files (x86)\EA GAMES\Battlefield 2\mods\pr
                    Free: 151.21 GB, Total: 288.09 GB, NTFS
     Profiles Path: C:\Users\*\Documents\ProjectReality\Profiles
                    Free: 151.21 GB, Total: 288.09 GB, NTFS
    Update DL Path: C:\Users\*\AppData\Local\Project Reality\Project Reality BF2\Downloads
                    Free: 151.21 GB, Total: 288.09 GB, NTFS
   Update Log Path: C:\Users\*\AppData\Local\Project Reality\Project Reality BF2\UpdateLogs
                    Free: 151.21 GB, Total: 288.09 GB, NTFS

Game Information
----------------
      CD Key Valid: True
    Installed Mods: bf2, pr, pr_beta, xpack
       Current Mod: pr
       BF2 Version: BF2 1.5
        PR Version: 1.0.36.0
          Language: english
   Debug Available: False
     Large Address: True
Supported Hardware: None

Profile Information
-------------------
      Profile 0001: PR0_SNIPE
              Type: Online
 Last Used Profile: True
        View Intro: True
        Fullscreen: True
      Display Mode: 1920x1200@60Hz
Display Mode Valid: True
   Graphics Scheme: High
     Multisampling: Off
             VSync: False
   Terrain Quality: High
   Effects Quality: High
  Geometry Quality: High
   Texture Quality: High
  Lighting Quality: High
   Dynamic Shadows: High
    Dynamic Lights: High
 Texture Filtering: High
    Audio Provider: Software
    Provider Valid: True
     Audio Quality: High
               EAX: True

[Moszeusz6Pl]

Thanks for the report.

Are you telling that marker is moving up/down instead of right/left? From screens it look like that it's moving left/right, but is higher that it should be.

Did you change resolution? Try changing to previous and 800x600. Make screen in 800x600 if bug still occurs.

Was you modifying any files?

[ComedyInK]

Just to confirm I've had this happend too, been too lazy to fix it. when I quit game, I rage quit and ALT-F4 out, which I assume, sometimes leads the game to crash on the first startup.

I'll see what deleting the Cache folder does next time I hop on.

[Oskar]

Confirming, I have had this issue a couple of times as well. A game restart solved it every time for me.

[PR0_SNIPE]

Originally Posted by [R-DEV]Moszeusz6Pl

Thanks for the report.

Are you telling that marker is moving up/down instead of right/left? From screens it look like that it's moving left/right, but is higher that it should be.

Did you change resolution? Try changing to previous and 800x600. Make screen in 800x600 if bug still occurs.

Was you modifying any files?

The only thing I did to cause this was change from all low graphics with no anti aliasing and 100% view distance to all high with no anti aliasing and 50% view distance, then later changed that to 100% view distance. Didn't modify any files and I'll try deleting the cache and see if that helps.

I'll get more info the next time I play.

[PR0_SNIPE]

Got bad news...I tried loading the game on all low and then deleting the cache and loading all low and it was still there. (yes, I went through the shaders re-optimizing and all that upon loading a map for the first time) On all high its still there. So something other than the bf2 cache has been messed up when I first changed to all high. Here's a gif of what it looks like:



It seems to be stuck on 15 degrees no matter where the SL marker is put. Any direction.

[Forrest02]

memory.dll:thread 1796 is deallocating main thread memory is an error i get when i get this bug to, that and controls are disabled when this comes up to

[Moszeusz6Pl]

Thanks for more reports. Can you please post your system spec too, so we can determinate why it fixed itself for Oskar, and didn't for others, that can help solve this problem.

[PR0_SNIPE]

Great news!! I fixed it.

First I tried a full reinstall of PR. Didn't work. Then I reset my controls in the launcher and that fixed it!!

EDIT: The secondary controls had things like LEGACY in them before I reset it.

[Forrest02]

this is just a theroy of mine but i think this bug is prone to happen if you have a lot of back round programs running...every time i run multiple things in the back round the bug seems to happen on start up