EPDGaffney Posted January 30, 2018 Share Posted January 30, 2018 (edited) So, I know that I've tried this in the past and concluded that it didn't work. I am now running the GECK with NVSE, which I wasn't last time I tried, and for all I know this has something to do with that or the JIP plug-in for NVSE that is 'installed' as well, or it could be related to the Windows 10 updates since my last attempt. I personally right-clicked on my GECK-NVSE shortcut, chose Properties, went to the Compatibility tab, clicked Change settings for all users, chose Windows 7, and hit OK. I loaded up the editor and things look normal for the first time since upgrading to Windows 10. http://prntscr.com/i7j72c Edit: Clarifying for people that may have no idea what I'm on about, I'm referring to the bug in Windows 10 that squishes all your condition/topic columns against the left side and makes them appear to be invisible. It happens in Windows 8 as well but is tied to an update in Windows 8 and is removable, whereas in Windows 10 it is part of the OS itself. Edited January 30, 2018 by EPDGaffney Link to comment Share on other sites More sharing options...
dubiousintent Posted January 31, 2018 Share Posted January 31, 2018 That bug would be 'Issue: GECK is missing text in fields' in the wiki "Fallout NV Mod Conflict Troubleshooting" guide or the wiki "Getting started creating mods using GECK" article? Didn't realize that at first. If so, that is good news and I'll add it. -Dubious- Link to comment Share on other sites More sharing options...
EPDGaffney Posted January 31, 2018 Author Share Posted January 31, 2018 Exactly. Now, I see you've put Service Pack 1 for Windows 7, and the odd thing is that at least for me, it just says Windows 7 and specifies no more than that, but if I wanted to choose Vista for example, it has several versions. A YouTube user claimed Windows 7 was the one, so I tried it and it works. I also don't know that it would or wouldn't work for regular GECK without NVSE. I kind of think it would and that something else has changed since one of the Windows 10 updates, but I'm not basing that on a whole lot of facts, just my guess. Link to comment Share on other sites More sharing options...
dubiousintent Posted January 31, 2018 Share Posted January 31, 2018 (edited) Whether or not a "Service Pack version" is listed seems to vary by the release of Windows and updates. I included it for completeness, and because it may help some with an older version. I'm reasonably sure that the GECK is what needs the "compatibility" setting. I set mine directly on the GECK.exe itself. Hmm. Actually I have it set to "Vista SP2", but then I am still running Win7. Think I'll update that "Issue:" to mention both. -Dubious- Edited January 31, 2018 by dubiousintent Link to comment Share on other sites More sharing options...
EPDGaffney Posted January 31, 2018 Author Share Posted January 31, 2018 My GECK worked gorgeous on Windows 7, so it mayn't matter much what you set it to on your system, but Windows 10 rained blows on my New Vegas experience, and most older software in general. Every once in a while I find something I like about this OS (new Task Manager comes to mind), and I'm hopeful that 'upgrading' will pay off in future, but I can't say I'd recommend it at the moment. Link to comment Share on other sites More sharing options...
EPDGaffney Posted January 31, 2018 Author Share Posted January 31, 2018 (edited) So...my GECK has reverted despite still having compatibility mode set as it was when it briefly worked correctly. I suppose list it as a 'lead' or something. Never mind, it still works fine as long as I don't open an AI Package's conditions, and then all Condition columns become squished for any form you open. Also, as a test, I switched it to Vista SP2 and it's working apart from that. Meaning Perks, Effects, and Dialogue condition columns work perfectly if you don't open an AI Package. Thinking about it, I may have been working a lot with AI Packages when I tried compatibility mode last time, so maybe that was the only change; that I wasn't now. Edited January 31, 2018 by EPDGaffney Link to comment Share on other sites More sharing options...
dubiousintent Posted January 31, 2018 Share Posted January 31, 2018 (edited) Bummer. My guess then is that the problem still exists for any part of the GECK that uses similar "list form" controls with multiple columns. Something about how that control in the "AI Package" screen is implemented is causing a bug affecting them all. I'll update that "Issue:" again. -Dubious- Edited February 1, 2018 by dubiousintent Link to comment Share on other sites More sharing options...
madmongo Posted January 31, 2018 Share Posted January 31, 2018 I intentionally downgraded one of my computers to Windows 7 just so that I could use the GECK and Blender 2.49b without any issues. Link to comment Share on other sites More sharing options...
EPDGaffney Posted January 31, 2018 Author Share Posted January 31, 2018 Blender 2.49b works perfectly as far as I've seen, though I probably wouldn't know the difference and would just assume they hadn't made the improvements I'm used to in later versions. But nothing super buggy seems to happen anyhow. Link to comment Share on other sites More sharing options...
madmongo Posted February 1, 2018 Share Posted February 1, 2018 In Blender 2.49b on Windows 10 if you press B to block select it leaves annoying lines over the screen while you do the selecting. The block select still works though. It's just a minor annoyance but it bugs me. I haven't run across any other problems with 2.49b on Windows 10. Link to comment Share on other sites More sharing options...
Recommended Posts