Recommended Posts

It's still on preload for me, telling me that I need to wait until it's officially released! I'm in Korea, but that shouldn't matter. I have restarted Steam, but nothing. Any ideas?

EDIT: I just read that it won't unlock for Korea until the 12th! WTF? VPN!

EDIT: Actually, I don't want to risk mucking-up my Steam account. I guess I'll start Uncharted 3 today instead.

Played a bit when it unlocked last night on the PC.

Anyone else notice that with the mouse the mouse look is a bit odd, it looks left and right fine but if you try to look up and down it is a lot slower. Might have to jump into the config and see if X and Y sensitivity are set different.

5:03 AM, November 11th

Due to unforeseen bladder complications, I have been forced to take a break for the first time since starting over five hours prior. I am already experiencing what seem to be withdrawal symptoms, but I cannot be sure.

Since beginning the use of Skyrim, I seem to have put myself into an alternate universe - an imaginary land filled with elves, dragons, and magics. The experience has so far been positive, but occasional inconsistencies regularly throw me out and back into my own conscience. Another oddity is that I cannot seem to see my body when on Skyrim - my presence in the New World appears to be merely a set of arms.

I will now resume use of Skyrim and disembark once again on my journey.

Yeah, for those complaining about the mouse not working, it seemed to be the gamepad that was causing that for me. If I have my 360 controller in upon launching the game, it defaults to that and disables the mouse in-game. If I disable the controller in the game options, the mouse works fine and dandy. It would be nice if they left both working at the same time. I like to switch in games depending on what I am doing.

Why did you take a photo of your screen :) ?

I rage hard when people do that lol

Seriously I can't stand the ****ing combat. Either in first person or third person view, it's impossible to know whether you actually hit the enemy because there're no blood bleeding out and there's no hit markers.

If you can't tell you're hitting the enemy, maybe you shouldn't be playing... Seriously, do you play with the volume off?

Seriously I can't stand the ****ing combat. Either in first person or third person view, it's impossible to know whether you actually hit the enemy because there're no blood bleeding out and there's no hit markers.

:huh: there are lots of blood (blood splashes to the walls and all that) and the enemy body part bends when you hit them, and there are a lot of audio clues as well

Seriously I can't stand the ****ing combat. Either in first person or third person view, it's impossible to know whether you actually hit the enemy because there're no blood bleeding out and there's no hit markers.

I'm not a fan of the combat either. Hit somebody in the face with a sword and a hit sound plays. Where's the reaction to being stabbed in the face?

sigh... if that is true, the end is finally here. Consoles have killed the last bastion of good games.

Sorry consoles haven't done anything. If anyone, we should blame only the developers. They themselves are responsible for making their creations great or hopeless like most of the modern games.

Really annoyed by the fragility of playing as a mage. It's not like I expect to be able to stand there and take a lot of heat but I get 1-hit-killed CONSTANTLY with freaking Stoneflesh active on level 10 (expert difficulty). Gah.

lol, try a lower difficulty.

I have no problem with the difficulty. I do have a problem with the fact that a random mob in a cave 1 shots me while a dragon does not (and I've killed 5 dragons so far). Meh.

Also what they have done with the interface is just terrible. You see what magic is active on you through a freaking menu. I play on 2560x1440, I can handle more than 10 things on my screen when I'm looking at my inventory. I really hope modders will be able to fix this. Compared to this the Oblivion interface seems great (and I disliked that too). ****ing consoles.

This topic is now closed to further replies.
  • Posts

    • The machines are starting to fight back any way they can.
    • No news articles about the Arch Linux repo being majorly infected with malware?!?
    • Waymo recalls self-driving software after cars enter closed freeway work zones by Paul Hill Waymo, the self-driving car maker owned by Alphabet – the parent company of Google –, has recalled some of its fifth-generation Automated Driving Systems (ADS). It did so after some of its cars drove through closed construction zones. According to the National Highway Traffic Safety Administration (NHTSA), the affected vehicles were capable of driving through a closed freeway construction zone and continuing to drive at speed. The listing on the NHTSA website says that Waymo is currently developing a solution to fix this issue, but in the meantime, freeway driving is being restricted. Waymo will update its ADS software so that vehicles can detect when they can avoid entering construction zones. According to the Safety Recall Report, on April 20, 2026, Waymo’s Field Safety Committee began meetings reviewing an event from April 11, 2026, and five events from April 19, 2026, where Waymo’s autonomous vehicles didn’t recognize and drove past ramp closure signs into the pre-planned freeway construction zones. This took place in Phoenix, Arizona. Separately, on May 18, 2026, seven Waymo vehicles entered freeway lanes with active construction in the San Francisco Bay Area by driving between cones that were placed to show the lane was closed. On the back of both of these events, Waymo restricted freeway driving until it could address the issue. In June, Waymo’s Safety Board reviewed the issue and additional information related to ADS performances around construction zones; then, as a result, it decided to conduct a recall. This development is not good for Waymo as it adds to a growing list of technical hiccups its cars have experienced. Ultimately, it will lead to more scrutiny from lawmakers around the world who will be more cautious about letting autonomous vehicles on their roads without tighter regulation. For readers in areas where Waymo operates, does this news make you more wary about stepping into one of these vehicles?
    • I'm still on Windows 10 22H2 because I didn't want to deal with all the issues in Windows 11, so I waited almost a week before installing the latest Patch Tuesday update (KB5094127), I went ahead and did it, and it was a huge mistake—ever since then, my File Explorer has seen a performance drop of about 30% when transferring large files... Once again, Microsoft has outdone itself! This update cannot be uninstalled, either through the Control Panel (via Settings) or by accessing Advanced Startup Options. The only possible alternative would be to use system restore points, but I’d have to reinstall all app and driver updates (and there’s no guarantee it would work). Or there’s the “nuclear option” of a in-place repair without losing files or apps, but even then, all my customizations would be lost! Microsoft just can’t help but mess everything up! Way to go, Microsoft! But I still don’t want your c****y Windows 11!
    • Microsoft: Windows 11 could finally solve a major issue across AMD, Nvidia, and Intel GPUs by Sayan Sen While Microsoft has been trying to improve it, Windows 11 is definitely not flawless, as even today some issues are taking a year to publicly acknowledge. However, one area of trouble that may finally see much better results soon is graphics driver crashes. Work on graphics driver timeouts, also called Timeout and Detection Recovery (TDR), is not new as the latest WDDM 3.2 also has specific improvements regarding it. Windows Display Driver Model (WDDM) version 3.2 is supported on Windows 11 24H2 and 25H2. However, with the upcoming version 26H2, TDR crash diagnosis could go to the next level as Microsoft is introducing a new DirectX 12 API feature called "DirectX Dump Files". Similar to how system memory dump files work when a system crashes or freezes or encounters any such major issue, DirectX Dump Files (DDF) will essentially record a snapshot of the GPU execution right at the moment a graphics-related crash or hang or freeze occurs, so that developers can better understand and diagnoze these TDR and timeout detection errors. The dump will be available as a .dxdmp file for analysis and it will be a comprehensive dump file generated with detailed insights about the hardware, drivers, Windows, as well as the affected application. This should be another welcome change in this department. Earlier at GDC 2026, when the technology was first debuted, Microsoft had shared more details regarding it. The company had explained how DDF is designed to gather data from every layer of the graphics stack into a single file, eliminating the need for developers to manually correlate logs from multiple tools. As mentioned above, the dump can contain a lot of useful details like GPU hardware state information such as register values, shader program counters, page fault virtual addresses, shader memory data, and command buffers. Alongside that, it also captures DirectX runtime and kernel information, including D3D objects, pipeline state objects, device error data, adapter details, and CPU call stacks. Microsoft says the feature has been built around two primary use cases: retail device removals and local device removals. The former allows developers to collect crash information from end users' systems in the field, while the latter helps QA teams and developers investigate issues on test machines. Developers will also be able to include up to 2 MB of custom application data through new D3D12 APIs, providing additional context for troubleshooting. In addition, Microsoft is introducing three dump collection modes ranging from zero-overhead capture, which has no runtime performance impact on supported hardware, to higher-detail modes that collect more vendor-specific debugging data. On compatible Tier 2 hardware, zero-overhead dumps will be enabled by default, meaning developers may begin receiving useful crash diagnostics without making any code changes. The table below explains the three tiers: Tier Description NO_OVERHEAD Enables crash capture with no runtime cost and is suitable for broad deployment MEDIUM_OVERHEAD Provides a balance, capturing additional diagnostic data with moderate impact HIGH_OVERHEAD Collects the most detailed GPU and driver state available, enabling deeper investigation at the cost of higher runtime overhead In terms of availability, the company expects broader release to be around the fall of 2026, which should be right around the time when Windows 11 version 26H2 lands. Right now, DirectX Dump Files are available as a preview and currently, only AMD has the compatible AgilitySDK Developer Preview driver version 26.10.07.02. You can find the official announcement post here on Microsoft's website.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      599
    2. 2
      +Edouard
      190
    3. 3
      PsYcHoKiLLa
      79
    4. 4
      Michael Scrip
      77
    5. 5
      Steven P.
      70
  • Tell a friend

    Love Neowin? Tell a friend!