Deleted133263User

First post updated : Recently Skyrim SE has been updated a few times, and additionally xEdit has now gone public with a release on Nexus of version 3.2.1, which has refined its record editing. Skyrim LE results are unaffected when using the new xEdit, so no need to reclean for oldrim Skyrim SE benefits quite a bit from recleaning, and the results / CRCs/ MD5 checksums are all now up to date in the OP for using xEdit v3.2.1

First post updated : Recently Skyrim SE has been updated a few times, and additionally xEdit has now gone public with a release on Nexus of version 3.2.1, which has refined its record editing. Skyrim LE results are unaffected when using the new xEdit, so no need to reclean for oldrim Skyrim SE benefits quite a bit from recleaning, and the results / CRCs/ MD5 checksums are all now up to date in the OP for using xEdit v3.2.1

First post updated : Recently Skyrim SE has been updated a few times, and additionally xEdit has now gone public with a release on Nexus of version 3.2.1, which has refined its record editing. Skyrim LE results are unaffected when using the new xEdit, so no need to reclean for oldrim Skyrim SE benefits quite a bit from recleaning, and the results / CRCs/ MD5 checksums are all now up to date in the OP for using xEdit v3.2.1

WTH is a gleam widget :D

AMD Spectre mitigation update news https://www.amd.com/en/corporate/security-updates#paragraph-290416

InSpectre has been updated Release #8 — Now shows whether an Intel microcode patch is (ever) available for Spectre. Intel has finished designing microcode update patches for its processors. On April 2nd, 2018, they announced that processors that have not yet been patches will never be patched. Their full statement is available in this PDF document. In that document, Intel specifies which of their many processors do have patches and which of their more recent processors will never receive updated firmware. Now that the industry has this information, this 8th release of InSpectre incorporates that list of CPUIDs and displays whether microcode firmware updates exist for the system's Intel CPU.

Looks like everyone wants a slice of this pie New service 1.1.1.1 https://1.1.1.1/ Also Steve Gibsons DNS Benchmark has been updated and taken 9.9.9.9 and 1.1.1.1 onboard as part of its default set for comparison with whatever you are using. https://www.grc.com/dns/benchmark.htm I think from now I will be testing 1.1.1.1 as Primary DNS server, and 9.9.9.9 as Secondary backup DNS server. 9.9.9.9 has served me well and has proved very reliable since I started this topic. Anyway before anyone asks if I work for the company or some crap .. Go read Cloudflares missions statements on 1.1.1.1 yourself and make up your own mind instead of listening to me blab :P

So long as this online tool does not puke out wild edits like the traditional CKs do, then there would also be no need for putting the finishing touches to the plugin with xEdit .. Cant see that being the case though, they would just get the CK adapted for the job and still have the same issues with it, plus probably introduce more bugs. So then cleaning your plugin of wild / dirty edits becomes a problem, Beth will not use community made tools, no matter how much they wish they could for correcting their own issues. Creating fake esm's for projects that need them would also not be possible, so the unofficial patches would be hamstrung. Probably a few other snags with the idea when it comes to any kind of patching too, and expanding on other peoples work in a community acceptable way with permissions etc.

They also have their own Forum here https://forum.kingdomcomerpg.com/ But thats probably more of a self help thing between other players If you want to make an official bug report with DXDiag report, and as detailled a description of where exactly you are getting CTDs send them an email and DXDiag attachment to : [email protected] But I wouldn't bother if you are using mods (presumably anyone participating in Nexus forums are here because they also use Nexus Mods for Kingdom Come). They need actual game related bug reports from vanilla games which have not seen any mods installed, not mod related reports. There are a lot of CTD issues being reported to the ether on Steam Discussions for Kingdom Come which often turn out to be mods which need updating to be compatible with the latest version of the game = Warhorse cannot reproduce such problems so the reports are just wasting peoples time. So if you have been using mods (and old configs), get your game back to vanilla state with no mods installed and start a new game. Work up to the point you can replicate the crash, then give a detailed report. Its the only way these things will get weeded out. Mods for this game include modified game files, which when installed replace (indirectly) the content of the original file. So if the modified file includes code from an older version of the game, and that file has been updated by the developers in a newer version of its patches, then by keeping the mods replacer files installed you are reverting fixes, to older code, and possibly causing a domino effect of issues with other parts of the game which now expect the fixes to be in place for everything to work correctly .. So anyone with mods installed can actually be causing issues themselves.

Edit : Disregard this post, I have just seen the issue where Tannin is already participating in a relevant discussion.

O_o the microsoft fix list for Spectre has grown quicker than expected https://support.microsoft.com/en-us/help/4090007/intel-microcode-updates When I posted that link 6 days ago they only had two processors covered with that Microsoft boot fix, so it is as they say expanding with more coverage the more Intel adds Spectre Microcode fixes to it. Shouldn't be too long before they have the majority of them done and we can all use that update. Though I think if my machine vendor comes out with the BIOS update I will probably still use that.

Go to 7 mins and 30 seconds in your video you are presenting as a backup to your claim that this is nonsense, and he says words to the effect of "even if all of this is possible" .. Thats not refuting the claims of CTS, his personal opinion is just making this seem unlikely because CTS have not provided any proof of concept code, which they have also stated Flashing the custom chip among the chipset is only one of the things they claim to have done, which in itself is not insignificant if it is true, it still represents a bad security risk, which imho is not to be sneezed at. Here's a video from someone who's opinion I trust .. Some of it may well turn out to be bogus or not so much of a concern, the company doing this may have some kind of grudge, but I dont think we can just put this down as nonsense .. Go to about 20 mins in on the Security Now podcast https://twit.cachefly.net/video/sn/sn0654/sn0654_h264m_864x480_500.mp4 Lets see what AMD have to say about this in due course Edit : Just found someone else seems to be sceptical too, suspecting stock manipulation https://www.theinquirer.net/inquirer/news/3028437/amd-ryzen-epyc-cpus-critical-flaws-linus-torvalds-fake But note that report ends with the following :

A bit off topic but a heads up .. AMD chipset users who escaped the Meltdown vulnerabilities (but some still need a bit of attention for the Spectre vulnerabilities apparently) have a new thing to be concerned with. If you have Ryzen or EPYC then there are some serious flaws (4 types including back doors implanted by a contracted company outside of AMD) which have been revealed (well not just revealed, the security firm made a dedicated website for it, and only gave AMD 1 days notice) AMD Flaws If you want to know why so little notice was given have a read here http://www.tomshardware.com/news/cts-labs-amd-ryzenfall-ryzen-epyc,36660.html

InSpectre has been updated to release #7 : https://www.grc.com/x/news.exe?cmd=article&group=grc.sqrl&item=18254&utag= Since that news group post was made the release has been uploaded at the link in the first post here.

I has news, very nice news. I am no longer keeping Adobe Photoshop and its damned subscription going .. Step asside Adobe and make way for : Affinity Photo, currently just shy of 50 of your english pounds - https://affinity.serif.com/en-gb/photo/ It was only available for Mac, but now is available for Windows, and its superb - Dont just take my word for it, here are some reviews .. http://www.techradar.com/reviews/pc-mac/software/graphics-and-media-software/image-editing-software/serif-affinity-photo-1295010/review https://www.softwarehow.com/affinity-photo-review/ And check this getting started video out, it has some features that are frankly amazing https://vimeo.com/channels/affinityphoto It imports .psd files Plugins : They are coming, a few are supported already but the main one we are interested in is .. Intel Texture Works plugin for all the new DDS texture formats .. Sadly at this time its on the developers to-do list, so could be a while. ---------------------------------------- So what to use to export those BC7 Linear fine textures in the meantime ? Save your texture image out as a lossless format ( say .png ) from Affinity Now please do not laugh, Paint.Net now supports all the new DDS formats if you use this plugin https://github.com/0xC0000054/pdn-ddsfiletype-plus Seriously, when you go to Paint.Net "Save As..", use the drop down menu to select DDS2 Now you can save textures and generate mipmaps in all the new Intel Texture Works formats, from Paint.Net. If the image you load is Lossless format, and you dont do any editing in Paint.Net, just save it out as whatever dds format you need and the whole procedure is as good as if you used Photoshop to edit and export your dds texture. Note, when Paint.Net saves the dds file, it will give it a file extension of .dds2, just rename it to .dds and it will work fine But also note, if you try to load up say a BC7 texture into Paint.Net, rename it to have a .dds2 extension again, and Paint.Net will now Load it. Paint.Net now comes with the above linked plugin as part of its standard installation ( in C: \ Program files \ Paint.net \ Filetypes \ ), but the GitHub page I think is getting updated faster than newer versions of Paint.Net, so manually overwriting the same three files with these is easy enough to do. So good resource file for your texture image, edit it with Affinity instead of Photoshop, save your image in a lossless format. Load it up in Paint.Net, then "Save as" DDS2, select your format, generate MipMaps etc. Rename the file name.dds ( removing the 2 )

The only thing that ever worked for that was doing the mini quest in the Soul Cairn - But you need to go back to a save prior to entering the Soul Cairn for the first time <- There is no way around this, the problem starts somewhere in the Soul Cairn, so to be sure you dont start it go back to before you entered there. Then before you leave the Soul Cairn, find Jiub. Complete his quest to gather all of his pages. Now you can continue the game and should not have the r6025 bug. It was the most annoying problem I ever had with Skyrim - See this topic And that was the only sure fire method of stopping it : Now for Skyrim SE, I have a new machine (which we believe can be relevant), and I have not done the Soul Cairn thing yet ( too busy restarting the game testing so many things to get anywhere near there so far :) ), so I doubt if I can advise as to whether it will occur or not. But from what I have seen around the various forums and Bazaars .. Nobody has experienced it in SSE yet. And SSE is a far more stable experience altogether especially with USSEP installed.

@MadPaddy But Tannin is not reinventing the wheel W.R.T MO, ElPresidente is doing MO2. Tannin is doing Nexus Mod Manager 2, in the form of Vortex. Anyone expecting Vortex to be MO2 is looking at the wrong Mod Manager.

Made a topic over on AFK Mods in case there is any feedback over there from peeps who do not frequent here .. https://afkmods.iguanadons.net/index.php?/topic/5177-relz-vortex-mod-manager/ ( And I have refrained from tainting it with my personal bias towards Wrye Bash to handle everything :P ) Congrats on release Tannin and Dark0ne, I will be trying it within a few weeks (just to see at least if my old mods with both Wizards for Wrye Bash, and FOMod scripting for MO / NMM .. Now actually still work ok with Vortex too).

Im just glad I am not a manufacturer of computers, have a look at the following couple of long lists of models which MSI have been working on .. https://www.msi.com/news/detail/rKUC2bI3D7-qQwKu2sMknN64chmZ522Lud9g_cONY0PNhahW-TFJ96dI7K7NA9rKUsihP5smlrCseaHQstFxJw~~ .. But they will have to do all of those again, and then work on the rest afterwards. That will be the same for everyone, the amount of time and effort being spent on this is tremendous. And now they all need doing again. Intel needs to get this right, lot of pressure, but hell what a time to make another mistake. ------------------ I heard mention somewhere that linux machines can implement the microcode fix for Spectre very easily, its just a case of dropping the microcode file in a special location in the OS (something \ etc \) .. And Windows (if Microsoft would do it) could be capable of doing this too. When the machine boots up, the file is loaded for use automatically by the BIOS. So no BIOS update necessary, its as simple as copy / paste. ------------------ And one more snippet of info heard - Only Windows 10 will get Meltdown OS fixes which do not affect performance so much as older Windows will be affected, so thats probably why my machine does not seem to be affected in any way that I can detect, apart from it being a relatively new machine, its received a better fix than will be given to say a machine with Windows 7. ------------------ Google Chrome v64 onwards ( And Chromium obviously ) has a new Flag which apparently helps with Meltdown exploits designed to use Java script via your Browser through hijacked 3rd party IFrames ( remember how Nexus used to unwittingly deliver Malware via some of its adverts and for the longest time Site admin did not know how widespread a problem it was ?, same mechanisms for delivery can now be blocked by this new flag in Chrome ) Type the flags url in the address bar, search for Isol, personally I'm going to try out Strict Site Isolation ..

Apparently more Intel Fu .. https://arstechnica.com/gadgets/2018/01/new-windows-patch-disables-intels-bad-spectre-microcode-fix/ .. And Microsoft updates will now detect and disable any already applied bad microcode fixes, presumably until a better one comes along. ​​​​​​​ :facepalm:

Version #6 is now released. " Release #6 — Worked around a Microsoft bug and more . . . Users of an earlier version of Windows 10 (version 1703 ‑ the non-Fall Creator's Update) reported that InSpectre did not believe that their system had been patched for the Spectre vulnerability. Upon analysis, a bug was discovered in that version of Windows which affected the way 32-bit applications, such as InSpectre, viewed the system. This was apparently fixed in the later “Fall Creator's Update” (version 1709) but not in the earlier version. A 64-bit “probe” was added to the 6th release of InSpectre to work around this bug in version 1703 so that InSpectre would accurately reflect any system's true protection. And, while we were at it, the language presented in the summary was changed from “vulnerable” to “protected” so that “YES” was the good answer and “NO!” was the bad answer. :)"

Go to 1hr 31 in the podcast discussing it = https://twit.tv/shows/security-now/episodes/646?autostart=false Personally I havent had any noticeable slow down at all, and thats running my MSI machine in comfort mode instead of sports mode. All current games I have dont need it to be running at full power on both CPU and GPU, so I can run it cool until the next gen games come along then I will need to let this machine shine a bit more by letting it run at higher frequency and a little warmer .. By which time whatever performance I get out of it will be the new norm for me, and game settings will be tweaked accordingly. Gamers generally have above average machines anyway, which from what I have heard will hardly be affected by these measures... .. But then, even if they are, they can now disable and re-enable the fixes whenever required by using InSpectre

Ookay mea culpa, I am such a horrible person, and stand in fear of your tirade of corrections (apologies if there is anything grammatically wrong here :rolleyes: ) https://xkcd.com/386/ Edit : PS "Calm your tits" was not directed at yourself (hence the dividing line splitting up the response ----- ), but if the cap fits .. Any chance of getting back on topic now mister angry ?, or are my questions @Tannin going to go past on yet another page of useless arguing ?

@IanPatt Hi, will try to keep this short, but if you want a long winded post on the same subject refer to this post on STEP Forum Can SKSE be made to wait a little longer for SKSE plugins to load. In the case where the Steam Client is NOT being loaded as part of Windows startup, if we launch SKSE64 2.06 from a desktop icon, the chain loading of everything that needs to load (including booting up the steam client) seems to be not initiating PapyrusUTIL v3.4 in my case, quick enough for DynDOLOD to have it ready by the time its plugin loads in game. (I am guessing the sequence of events, and taking a bit of a stab in the dark as to the probable cause .. But if I already have the steam client running before I load SKSE64, then there are no issues and DynDOLOD finds PapyrusUTIL resources are in place and loads fine) Edit : Looking at the Logs - If Steam Client is not running when I launch SKSE64, then only two logs are created SKSE64_Loader.log and .. SKSE64_Steam_Loader.log If Steam Client is already running, then a further log is created .. SKSE64.log But if the steam client is not already running then this third log does not get created And, the SKSE64_Steam_Loader.log when there is no Steam Client pre-loaded, looks like this .. skse64 loader 02000060 (steam) 01D393E0D09049AC 6.2 (9200)loader base addr = 00007FFC7D590000exe base addr = 00007FF63E540000found iat at 00007FF63FA62898original thunk 00007FFC8D2B1000patched iat

+ One more for @Tannin Could you please NOT include a warning about Fake esm (ie an .esp flagged as .esm) - Nexus Mod Manager still does this apparently and its a PITA. The amount of times this comes up in the Unofficial Patch comments from people not understanding it and requesting advice from the Unofficial patch team is ridiculous. Its a valid modding technique, and in the case of the unofficial patches is necessary.