LookoutPoint Posted June 11, 2019 Share Posted June 11, 2019 (edited) Hi, I'm using GECK NV v1.4 with Extender v0.18 and 4GB/NVSE Patcher v1.0.NVSE is v5.1b4 and I'm running GECK via shortcut (nvse_loader.exe -editor).GECKCustom.ini (https://pastebin.com/8w8eGM4s) changed bUseMultibounds=1 and bAllowMultipleMasterLoads=1The GECK loaded up and is showing the Extender v0.18.When I select a mod to load everything seems to be ok. But when I want to render a Interior or a worldspace the GECK crashes to desktop.Here is my EditorWarnings.log (without lod output): https://pastebin.com/MdBQH4mTIt seems there are meshes missing. These should be in the bsa files. o_Onvac.log: 11233011 _ NewVegasAntiCrash GECK.exe 11233011 _ 03310000 07050000 nvac.dll 11233011 _ 02E50000 05010040 nvse_editor_1_4.dll 11233011 _ 77240000 0A004563 ntdll.dll nvse_editor.log: NVSE editor: initialize (version = 5.1.4 04002060 01D5209CD9B835A0) imagebase = 00400000 fallout root = D:\SteamLibrary\steamapps\common\Fallout New Vegas\ config path = D:\SteamLibrary\steamapps\common\Fallout New Vegas\Data\NVSE\nvse_config.ini nvse_loader.log: nvse loader 05010040 01D5209CD9A2C09F launching editor procPath = D:\SteamLibrary\steamapps\common\Fallout New Vegas\GECK.exe launching: GECK.exe (D:\SteamLibrary\steamapps\common\Fallout New Vegas\GECK.exe) dwSignature = FEEF04BD dwStrucVersion = 00010000 dwFileVersionMS = 00010004 dwFileVersionLS = 00000206 dwProductVersionMS = 00010004 dwProductVersionLS = 00000206 dwFileFlagsMask = 0000003F dwFileFlags = 00000000 dwFileOS = 00040004 dwFileType = 00000001 dwFileSubtype = 00000000 dwFileDateMS = 00000000 dwFileDateLS = 00000000 version = 0001000400000206 using slow nogore check normal exe hook call addr = 00C62BC1 load lib addr = 00D2318C dll = D:\SteamLibrary\steamapps\common\Fallout New Vegas\nvse_editor_1_4.dll main thread id = 12188 remote memory = 001C0000 old winmain = 00445900 launching The game itself is runing fine without any known problems. What steps could I do to make my GECK NV run again.I'm open and thankful for suggestions. Greetings Edited June 11, 2019 by FalloutHog Link to comment Share on other sites More sharing options...
dubiousintent Posted June 11, 2019 Share Posted June 11, 2019 Anytime the game "Crashes to the Desktop" (CTD) it's typically going to generate an error message in the Windows Eventlog. Please see the "Windows Error Messages" section of the wiki "How to read most Bethesda game error logs" article. Based upon that sequence of events, I'm going to guess you are going to find "Windows Exception code: 0xc0000005". The "Faulting Application" is often the victim of another program rather than the actual culprit, making it virtually impossible for the user to trace the source. Any recent update since the last time it was working correctly is suspect, as are viruses even if you have anti-virus (AV) running. Run AV from multiple sources when checking for infections. There are a number of free online scanners on the internet (though they are all going to try to sell you their services after the first time).You may need to exclude GECK from "Data Execution Protection (DEP)" and configure " Windows Defender Exploit Guard (WDEG)". Please see "Issue - NVSE - fails to load after update KB4058043 to Win10 FCU v1709" under the 'Solutions to Starting the game problems' section of the wiki "Fallout NV Mod Conflict Troubleshooting" article. (Just replace references to "FNV" with "GECK".)Try turning off any unnecessary background processes, such as "anti-virus" or "anti-malware" programs (unneeded if you are running your game in "offline" mode once you have scanned since the last connection), multiplayer "overlays" like "OverWolf" (this is single-player after all), the Steam overlay, etc., at least on a temporary basis to see if they are interfering. There are also tools (often called "Game Boosters") to help you determine "unnecessary when offline" Windows services you can temporarily shut down.-Dubious- Link to comment Share on other sites More sharing options...
LookoutPoint Posted June 12, 2019 Author Share Posted June 12, 2019 Thx for your response.There is a log when GECK is crashing. It's in german but the structure is the same: Name der fehlerhaften Anwendung: Geck.exe, Version: 1.4.0.518, Zeitstempel: 0x4e0415d8 Name des fehlerhaften Moduls: Geck.exe, Version: 1.4.0.518, Zeitstempel: 0x4e0415d8 Ausnahmecode: 0xc0000417 Fehleroffset: 0x0085e948 ID des fehlerhaften Prozesses: 0x2420 Startzeit der fehlerhaften Anwendung: 0x01d521532d5ed333 Pfad der fehlerhaften Anwendung: D:\SteamLibrary\steamapps\common\Fallout New Vegas\Geck.exe Pfad des fehlerhaften Moduls: D:\SteamLibrary\steamapps\common\Fallout New Vegas\Geck.exe Berichtskennung: d8c1d040-f27d-48b5-9329-4711cf84b2e1 Vollständiger Name des fehlerhaften Pakets: Anwendungs-ID, die relativ zum fehlerhaften Paket ist: I tried to load the GECK without NVSE or the 4gb patch but it still crashed when I load a cell.But some cells are working. I can load them and see everything. But other (also vanilla) cells won't load without a crash.Tried to deactivate the G-Data Internetsecurity, compatability modes on nvse_loader and geck.exe, run as administrator, without steam but no change.I did the DEP and the WDEG thing but still crashes. Maybe a broken mesh, but i dont have any problems ingame. :psyduck:Any other ideas? Link to comment Share on other sites More sharing options...
dubiousintent Posted June 12, 2019 Share Posted June 12, 2019 The exception code "0xc0000417" usually means you have a misconfigured or corrupted system file. Please see the "How to fix 0xc0000417 Error?" article. An alternative article is "Fix The exception unknown software exception (0xc0000417) occurred in the application". But basically they all come down to "revert to a previous system restore point". You should check with the "GECK Extender" team to see if they are compatible with the German version of the game. I've seen other issues with the German "no gore" version that indicate there are some code differences. -Dubious- Link to comment Share on other sites More sharing options...
LookoutPoint Posted June 16, 2019 Author Share Posted June 16, 2019 (edited) I did some tests and one thing is interesting: An old copy of my fnv installation from 2014 with geck + power up works like a charm. No red exclamations in interiors. I can open the mods I can't open because of ctd on my current installation.So it seems to be not a problem with steam, corrupt system files, firewall etc. but with my current fallout nv installation.My old fvn installation is without ttw and with less / older nvse files.Maybe I just need to add things from my current installations to a backup of my 2014 installation one by one to see what the problem is. btw. I have an austrian version. Thats german / austrian language and gore. Need to do some tests. Any advises? Edited June 16, 2019 by FalloutHog Link to comment Share on other sites More sharing options...
dubiousintent Posted June 17, 2019 Share Posted June 17, 2019 Regional versions are important information. Not often, but sometimes it really does make a difference, especially the "German no-gore" version. Suggest for developing and testing, you create an downloaded "English language" regional version of the game dedicated to that purpose. I don't know but doubt the GECK as downloaded is prepared for an Austrian OS environment. However, if that was the language used for your previous install, then it shouldn't matter. Except you formerly were using "PowerUp". The replacement for that is "GECK Extender", but I don't know if that might not be your problem. No idea if there are issues with it and "other than English" language versions of the game. Try replacing "Extender" with "PowerUp". TTW (as I understand it) has very large ESM files. Test without TTW, and if you only have issues with it, ask on their support forum. -Dubious- Link to comment Share on other sites More sharing options...
LookoutPoint Posted June 18, 2019 Author Share Posted June 18, 2019 (edited) I don't have any news so far but one question.The 2014 version does not have red exclamations on interiors the 2019 version does have them (only in geck).TTW has changed the bsa files and I checked, that I have the sarchivelists from the ttw faq page in my geckcustom.ini.Red Exclamations are missing meshes. But why is geck not showing them?The game itself does not have that problem and will show all meshes correctly. But with the same interior in geck the mesh is missing. For example the 1stPersonPoolCue, the LamplightChandelier, OutfitPrewarSpring2 or the Clock01. They are working ingame but not in geck. is there any archive invalidation just for geck or an ini-setting? The geckcustom.ini seems to be correct, because the 2014 version works (and is using the same geckcustom.ini in the mygames folder). :unsure: EDIT: Ok i think i know why. TTW have changed the bsa and the clock01 is no longer in fallout - meshes.bsa or fallout - meshes2.bsa but in taleoftwowastelands - meshes.bsaThats why the game loads them because ttw is a loaded plugin and the geck dont show them because the activated mod does not know TTW and the bsa files. EDIT 2: Ok and that seems to be the problem for my crash. The not mentioned ttw.bsa in geckcustom.ini.I just tried opening a few interiors and exteriors and no red exclamations and no ctd while loading. Tested this even with extender 0.19.Will do some tests and report then here.Just curios why the ttw faq don't mentioned it: https://taleoftwowastelands.com/faq#INISettings and why the game itself dont need this entry in any ini-file. Edited June 18, 2019 by FalloutHog Link to comment Share on other sites More sharing options...
dubiousintent Posted June 19, 2019 Share Posted June 19, 2019 That's some interesting test results. Thanks for reporting back. As for "why not": possibly because the TTW FAQ appears to focus upon getting it to play rather than helping mod authors to work with it in the GECK. You would have to ask that team. The GECK is not intended to be "intuitive" or "anticipate" your needs in the same manner as the game. Because it is an "tool", it only loads files that you select, with the exception of those with an associated "*.nam" extension. This appears to be by design, I expect for reasons similar to how you worked out your problem. The "geckcustom.ini" is a recent addition with the "GECK Extender". At the moment that team's focus is on adding features rather than documentation. -Dubious- Link to comment Share on other sites More sharing options...
Recommended Posts