I logged onto test this morning , The 1st thing I did was rift to RK , I had no issues even while using my flying mount. Then I rifted to OT using my flying mount I had no issues , Then I rifted back to RK and 15 sec after rifting in I CDT , Below is the VGClient.log in the Bin/log folder. After posting the log I logged back into VG. I was in RK had no issues then I rifted to Pota. Never lost my Griffon while chunking , I usually lose it at Location -50282,102358,36162 in skrilien point (-10,-8) coming into or out of that chunk line on live server. I then rifted back to RK with in 15 sec after rifting in I CTD. Ping rate was about 20 to 50 below what i normally get on live. FPS was avg. 175 my settings are maxed. 2013-05-02 18:24:26 1367511866 1 4 4300922457 Logging initialized. 2013-05-02 18:24:26 1367511866 2 4 4300922465 Init: Name subsystem initialized 2013-05-02 18:24:26 1367511866 3 4 4300922465 Init: Detected: Microsoft Windows Vista 6.1 (Build: 7601) 2013-05-02 18:24:26 1367511866 4 4 4300922466 Init: Version: 1.166.1.136960 2013-05-02 18:24:26 1367511866 5 4 4300922466 Init: Compiled: May 1 2013 18:01:43 2013-05-02 18:24:26 1367511866 6 4 4300922466 Init: Threadsafe Core: No 2013-05-02 18:24:26 1367511866 7 4 4300922466 Init: Base directory: C:\Users\Public\Sony Online Entertainment\Installed Games\Vanguard\bin\ 2013-05-02 18:24:26 1367511866 8 4 4300922466 Init: Character set: Unicode 2013-05-02 18:24:26 1367511866 9 4 4300922476 Init: Object subsystem initialized 2013-05-02 18:24:26 1367511866 10 4 4300922477 Init: Computer: HALPC 2013-05-02 18:24:26 1367511866 11 4 4300922477 Init: User: Hal 2013-05-02 18:24:26 1367511866 12 4 4300922477 Init: CPU Page size=4096, Processors=12 2013-05-02 18:24:26 1367511866 13 4 4300922477 Init: CPU Detected: GenuineIntel 2013-05-02 18:24:26 1367511866 14 4 4300922477 Init: CPU Features: MMX SSE SSE2 SSE3 2013-05-02 18:24:26 1367511866 15 4 4300923077 Init: CPU Speed=3202.071255 MHz 2013-05-02 18:24:29 1367511866 16 4 4300925346 Init: WMI: cpu: Intel(R) Core(TM) i7-3930K CPU @ 3.20GHz | ID: GenuineIntel Family 6 Model 2D Stepping 7 2013-05-02 18:24:29 1367511866 17 4 4300925347 Init: WMI: Display: NVIDIA GeForce GTX 670 -1 MB 1680 x 1050 @ 59 mHz 2013-05-02 18:24:29 1367511866 18 4 4300925347 Init: WMI: Motherboard: ASUSTeK COMPUTER INC. P9X79 2013-05-02 18:24:29 1367511866 19 4 4300925347 Init: WMI: OS: Microsoft Windows NT 6.1 2013-05-02 18:24:29 1367511866 20 4 4300925347 Init: WMI: Model: System manufacturer System Product Name 2013-05-02 18:24:29 1367511866 21 4 4300925347 Init: WMI: CPU - Logical: 32 | Physical: 1 | Frequency: 3.201 gHz | L1 Cache: 32k code 32k data | L2 Cache: 256k | L3 Cache: 12288k | Bus Freq: 100 mHz 2013-05-02 18:24:29 1367511866 22 4 4300925347 Init: WMI: Memory: -49 MB @ 1600 MHz | Free: 1863 MB 2013-05-02 18:24:29 1367511866 23 4 4300925347 Init: Memory total: Phys=16726480K Pagef=0K Virt=33451100K 2013-05-02 18:24:29 1367511866 24 4 4300925347 Init: Working set: 32000 / 159000 2013-05-02 18:24:29 1367511866 25 4 4300925347 Init: Process Info: Peak Memory Used: 40724 Working Set: 40724 PageFile: 67100 2013-05-02 18:31:08 1367511866 938 4 4301324885 Sending BECOME_PC message. 2013-05-02 18:31:09 1367511866 939 4 4301325152 DevNet: Client received: JOINED 2013-05-02 18:31:09 1367511866 940 4 4301325152 DevNet: Client received: JOINED 2013-05-02 18:31:09 1367511866 943 3 4301325635 Warning: Failed to load 'Psionicist_Weapon_MSounds': Can't find file for package 'Psionicist_Weapon_MSounds' 2013-05-02 18:31:09 1367511866 944 3 4301325636 Warning: Failed to load 'Psionicist_Weapon_MSounds': Can't find file for package 'Psionicist_Weapon_MSounds' 2013-05-02 18:31:15 1367511866 945 4 4301331707 DevNet: Client received: RUSE GUID=6C92E9D646493E31238F508899D879CE FLAGS=1 SIZE=12298401 GEN=1 FNAME=Ra1_P1_C1_windmills_mesh.usx 2013-05-02 18:31:15 1367511866 946 4 4301331852 DevNet: Client received: RUSE GUID=2C57A4024477038A3E7171AAFC6C2D31 FLAGS=1 SIZE=6597 GEN=1 FNAME=PropsSounds.uax 2013-05-02 18:31:15 1367511866 947 4 4301332113 DevNet: Client received: RUSE GUID=2DB6E9884F4F485BAEED5E8EC170D6CC FLAGS=1 SIZE=6493894 GEN=1 FNAME=Ra1_P1_C1_Grid_Keep02_mesh.usx 2013-05-02 18:31:18 1367511866 948 3 4301334558 Warning: Type mismatch in VSize of Texture: file 1, class 2 2013-05-02 18:31:18 1367511866 949 3 4301334559 Warning: Type mismatch in VBits of Texture: file 2, class 1 2013-05-02 18:31:20 1367511866 950 4 4301337004 DevNet: Client received: RUSE GUID=1672434642A89CEB2F593480F67A0872 FLAGS=1 SIZE=6427420 GEN=1 FNAME=Ra1_P1_C1_Grid_Farm01_mesh.usx 2013-05-02 18:31:20 1367511866 951 2 4301337030 Critical: ASyncLoadTexture 2013-05-02 18:31:20 1367511866 952 2 4301337030 Critical: ASyncLoadTexture 2013-05-02 18:31:20 1367511866 953 2 4301337030 Critical: UNormalBitmapMaterial:reCache 2013-05-02 18:31:20 1367511866 954 2 4301337030 Critical: UNormalBitmapMaterial:reCache 2013-05-02 18:31:20 1367511866 955 2 4301337030 Critical: FDynamicActor::IsRenderable 2013-05-02 18:31:20 1367511866 956 2 4301337030 Critical: FDynamicActor::IsRenderable 2013-05-02 18:31:20 1367511866 957 2 4301337030 Critical: VgSceneTreeNode::IsActorVisible 2013-05-02 18:31:20 1367511866 958 2 4301337030 Critical: VgSceneTreeNode::IsActorVisible 2013-05-02 18:31:20 1367511866 959 2 4301337030 Critical: VgSceneTreeNode::GetDynamicActorPVNodes 2013-05-02 18:31:20 1367511866 960 2 4301337030 Critical: VgSceneTreeNode::GetDynamicActorPVNodes 2013-05-02 18:31:20 1367511866 961 2 4301337030 Critical: RenderLevels::BuildVisibleNodeList 2013-05-02 18:31:20 1367511866 962 2 4301337030 Critical: RenderLevels::BuildVisibleNodeList 2013-05-02 18:31:20 1367511866 963 2 4301337030 Critical: VgPlanetScene::RenderLevels 2013-05-02 18:31:20 1367511866 964 2 4301337030 Critical: VgPlanetScene::RenderLevels 2013-05-02 18:31:20 1367511866 965 2 4301337030 Critical: (Pos=-66975.20,-1503.90,48650.70) 2013-05-02 18:31:20 1367511866 966 2 4301337030 Critical: (Pos=-66975.20,-1503.90,48650.70) 2013-05-02 18:31:20 1367511866 967 2 4301337031 Critical: UGameEngine:raw 2013-05-02 18:31:20 1367511866 968 2 4301337031 Critical: UGameEngine:raw 2013-05-02 18:31:20 1367511866 969 2 4301337031 Critical: UWindowsViewport::Repaint 2013-05-02 18:31:20 1367511866 970 2 4301337031 Critical: UWindowsViewport::Repaint 2013-05-02 18:31:20 1367511866 971 2 4301337031 Critical: UWindowsClient::Tick 2013-05-02 18:31:20 1367511866 972 2 4301337031 Critical: UWindowsClient::Tick
while i was in Skrilien point i noticed this oddity. (only happens on Test server )if you point your griffon to the ground , you will see some graphic "spikes" jetting up at you. it only happen if you are:in the air ,in 3thd person view and have pointed the mount to the ground. not sure if the pic will come up, here the original link https://skydrive.live.com/?cid=285121789cefd5ff&id=285121789CEFD5FF!3042
I've seen that happen on Live before as well... Cant remember what setting it was I turned off to make it stop happening though
That is not from new net code as it happens in live too. I get it to happen most easily when I do something in twin plateaus in Cragwind Ridge. For some reason that place causes worst graphics problems in the game for me.
Could you post that screenshot and provide any additional information to help us reproduce the issue (currently we can't). Edit - Nevermind. We've actually found what the issue is and we're getting to it. Never thought being too fast would be a problem. =P
Logged on test on Friday to test RK , I logged out in Khal the night before, ported to RK ran to the entrance of the fort an CTD. when I reentered the game in RK fort , within 15 sec I CTD. This after noon (sat) I logged onto test in RK made it to the rift without CTD. the log is the same as I posted above I ported to SK to test the graphics bug I posted about. I normally turn all of the Rendering off due to graphic bugs I've found on live servers. so I was checking on test to see it I had them off and they where. but when I tried to repeat the bug today I couldn't repeat it. so it might have been I glitch on my end. Overall I've seen an improvement in ping rates(east coast US) and FPS. I tested in NT city and was able to run though there without hitching. Cheers
Noticed an issue that was preventing any of my accounts from deleting toons to make room for new toons.
Thanks, Dosi. We've updated test with some logging to help track down the crash bug. We know it's related to textures having a certain out-of-range value. Whenever you crash, look over your crash log for a line that looks something like this: Code: Warning: Invalid Texture LODSET: Texture p1_c2_stone_sandstone_mixed01n from Package P1_c2_stone_shaders.Shaders with LodSet 103 So far, the most common places are Renton Keep, Tursh, and Tehatamani Harbor (hence the above sandstone texture). Post your warning line here so that we can better identify the real issue. Edit - Thanks, Micstruth. I'll look into that.
Guild chat, and join / creating a chat channel doesnt work /1 and /2 are not linked to region chat somehow
Some updates: Just this morning I finished up fixing the summonplayer bug (which was also happening for rifting and recalling to a different chunk). Down chunks will now prevent a player from entering them (back to the normal where it would knock you back and say "invalid chunk"). We're still working on one last client crash bug related to a bad art asset. We're also doing some raid-testing soon (pretty much now) to test server performance during raids. The above fixes will get pushed after the raid testing.
Fixed in this afternoon's patch (coming to you in the next few minutes). Couldn't repro the /1 and /2 mapping to region and auction issue. Let me know if this issue persists and I'll take a closer look at it.
did mention this to wigin, but he might have lost it in the tell spam. all mobs we killed in our 2 raid days were invalid target for looting, and had no loot for us.
Not sure if this was mentioned, but the client crash in Renton Keep was fixed. We had a corrupt texture package on the patcher that needed fixed. We've also identified the raid issues and are fixing them now. In additional, we are adding more logging to track any other similar issues that need to be addressed. We will be looking for some additional focused Testing on Test Server on Wed.
