Creation kit зависает на initializing windows
System specs
MacOS X Mountain Lion 10.8.3 (Playing through wine 1.7.0 I’m guessing that might have something to do with the error)
Memory 8 GB 1600 MHz DDR3
256 gig hard drive
2.4 GHz Intel Core i7
Graphics: Nividia GeForce GT 650M 1024 MB
Problem: After much messing around I finally got the creation kit to half open (huge pain in the ass in and of itself) but after clicking away they error messages (Streaming SIMD extension not supported and XAudio2 error) I always gets stuck on initializing windows I usually wait anywhere from 5-15 min for it to open, but have waited as long as an hour, perhaps a bit over, with no results, just that watch thing.
What I have tried (If I can even remember it all):
Downloading the porting teams bottled app for opening a no-steam crack of the creation kit (only way I could get it to open at all, otherwise consistently got either a ‘not enough memory for application’ error or the version control error even though version control was already set to 0 in the SkrimEditor ini. or it just kept trying to get me to install iVidi plugin 1.3 over and over again, where it would install but never finish the post installation)
Tried setting the code up to use a local network for version control (and created the directories necessary (i.e. creating a /merging in the
/Skyrim/ folder folder with ConstructionSetNetwok containing [WhoCanMerge] *return* 1=EASCH *return* EASCH=1 a copy of the data folder containing the elms and a /VersionBackup folder) created a SkyrimEditorPrefs.ini containing [WhoCanMerge] return EASCH=1)
Tried doing the mac update and restarting
Checked whether wine had Direct X components installed (it has d3dx9_#.dll’s which is Direct X 9) tried terminal command line reinstallation of the drivers via winetricks (having seperate issues with that, my newer version of wine doesn’t come with winetricks, and I installed wget command line without too much trouble which is working but «sudo cp wine tricks /usr/bin» is still returning an error message on DYLD environment. (use/bin/sudo) sudo is setuid or setgid, so if anyone has any advice on fixing this terminal error that might assist me in either solving the problem or narrowing down my options) (have also tried installing XCode 4.something and the sperate command line tools, with no affect on the sudo error). hence currently unable or rather unaware of how to reinstall or update Direct X drivers on wine 1.7.0. I have an older version of wine that came with winetricks and tried updating the direct X drivers and opening the creation kit with that version of wine to no avail
tried installing and unistalling TESVEditor
tried adding the code for multiple masters just in case that was the issue
in SkyrimEditor.ini under Papyrus (same editations where recommended to fix a memory error with skyrim itself so thought I’d try them in the Editor ini)
changed iMinMemoryPageSize to 10000
changed iMaxMemoryPageSize to 500000
changed iMaxAllocatedMemoryBytes to 180000000
All of these to no avail
Any help would be greatly appreciated, thanks all for reading.
Creation kit зависает на initializing windows
Q-2: Ставлю галочку у плагина в Data Files, но она сразу пропадает или не сохраняется.
A: Чаще всего это происходит по нескольким причинам(чаще всего 3-я и 2-я):
1) путь к игре в реестре, редко, но бывает:
Нажимаем Пуск->Выполнить(CTRL+R), вводим regedit, нажимаем Enter.
Откроется редактор рееста, идем по пути:
[HKEY_LOCAL_MACHINE/SOFTWARE/Bethesda Softworks/Skyrim/]Находим значение в Installed Path, проверяем актуальность для нашей папки с игрой, здесь бывает не верный путь.
Если не нашли значение по данному пути, попробуйте найти здесь
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Bethesda Softworks\Skyrim]
2) В Мои Документы в My Games->Skyrim в файле SkyrimPrefs.ini в секции [Launcher] нужно указать:
bEnableFileSelection=1
или так
bEnableFileSelection=1
bShowAllResolutions=1
uLastAspectRatio=1
3) Банально из-за русских названий файла плагина/русских букв в нём, здесь достаточно сменить название файла на латиницу.
Q-5: У созданного NPC темное лицо, что делать (темная текстура лица, сделанная в CK не сохраняется).
A: Распространенный баг!
1) Выберите в списке Actors окна Object Window всех NPC, которых вы добавили в плагине (у которых темное лицо)
2) нажмите CTRL + F4, вас спросят об экспорте face gen data. На процедуру может уйти какое-то время, в зависимости от количества актеров. После выполнения процедуры, в окошке появится статус Done.
3) Теперь у мода появятся свои nif и dds файлы, которые, при публикации мода нужно загружать вместе с esp файлом. Если мод для себя, то нет проблем)
Текстуры будут в папке: Data\textures\actors\Character\FaceGenData\FaceTint\название_мода.esp\
модели в папке: Data\meshes\actors\Character\FaceGenData\FaceTint\название_мода.esp\
Внимание! Категория должна быть выбрана именно Actors, т.к. в категории All данные горячие клавиши не работают.
Q-6: При компиляции скриптов и фрагментов скриптов — может появляться ошибка вроде:
Cannot use import folder
В новой версии редактора, скрипты были помещены в архив Scripts.rar, поэтому в Creation Kit не может найти исходники для компиляции.
Добрый день товарищи модостроители!
Я такой же, как и вы — любитель модмейкер, строитель и просто безумец желающий создать свой плагин на базе TES Skyrim.
До этого работал и интересовался TES Oblivion вполне успешно :thumbsup: , но вот пожелал создать свой мир в TES Skyrim.
Но вот беда.
Даже не начав погружение в мир создателей миров и могущественных плагинов, я не могу его создать! =(
Долго думал, почему НИЧЕГО не происходит при сохранении и наконец в 20 раз пересмотрев Creator.ini файл прописал в графе MESSAGES нули, чтобы ошибки были видны.
И вот такая картина у меня получается:
хотя никаких диалоговых окон у меня нет. Прошу помочь пожалуйста уважаемые, мне очень хочется создать свой плагин))
я могу через скайп или TeamViewer показать вам свой монитор и вы сами всё увидите. Помогите пожалуйста кто знает, что нужно сделать, чтобы закрыть эти диалоговые окна? Реально всё перепробовал.
Поставил репак от R.G механики!
Creation Kit stuck on «initializing windows», please help!
#1
I posted this on the steam community forums more than a week ago, and still no replies, hopefully someone here can help:
System specs
MacOS X Mountain Lion 10.8.3 (Playing through wine 1.7.0 I’m guessing that might have something to do with the error)
Memory 8 GB 1600 MHz DDR3
256 gig hard drive
2.4 GHz Intel Core i7
Graphics: Nividia GeForce GT 650M 1024 MB
Problem: After much messing around I finally got the creation kit to half open (huge pain in the ♥♥♥ in and of itself) but after clicking away they error messages (Streaming SIMD extension not supported and XAudio2 error) I always gets stuck on initializing windows I usually wait anywhere from 5-15 min for it to open, but have waited as long as an hour, perhaps a bit over, with no results, just that watch thing.
What I have tried (If I can even remember it all):
Downloading the porting teams bottled app for opening a no-steam crack of the creation kit (only way I could get it to open at all, otherwise consistently got either a ‘not enough memory for application’ error or the version control error even though version control was already set to 0 in the SkrimEditor ini. or it just kept trying to get me to install iVidi plugin 1.3 over and over again, where it would install but never finish the post installation)
Tried setting the code up to use a local network for version control (and created the directories necessary (i.e. creating a /merging in the
/Skyrim/ folder folder with ConstructionSetNetwok containing [WhoCanMerge] *return* 1=EASCH *return* EASCH=1 a copy of the data folder containing the elms and a /VersionBackup folder) created a SkyrimEditorPrefs.ini containing [WhoCanMerge] return EASCH=1)
Tried doing the mac update and restarting
Checked whether wine had Direct X components installed (it has d3dx9_#.dll’s which is Direct X 9) tried terminal command line reinstallation of the drivers via winetricks (having seperate issues with that, my newer version of wine doesn’t come with winetricks, and I installed wget command line without too much trouble which is working but «sudo cp wine tricks /usr/bin» is still returning an error message on DYLD environment. (use/bin/sudo) sudo is setuid or setgid, so if anyone has any advice on fixing this terminal error that might assist me in either solving the problem or narrowing down my options) (have also tried installing XCode 4.something and the sperate command line tools, with no affect on the sudo error). hence currently unable or rather unaware of how to reinstall or update Direct X drivers on wine 1.7.0. I have an older version of wine that came with winetricks and tried updating the direct X drivers and opening the creation kit with that version of wine to no avail
tried installing and unistalling TESVEditor
tried adding the code for multiple masters just in case that was the issue
in SkyrimEditor.ini under Papyrus (same editations where recommended to fix a memory error with skyrim itself so thought I’d try them in the Editor ini)
changed iMinMemoryPageSize to 10000
changed iMaxMemoryPageSize to 500000
changed iMaxAllocatedMemoryBytes to 180000000
All of these to no avail
Oh and I’ve tried reenabling and redisabling dwrite.dll in WineConfig (disabling it was necessary to view the text of any steam windows, but I ran it with dwrite enabled just to check if disabling it had somehow messed up the creation kit, but no, that wasn’t it either)
Final note: my wireless network is highly censored (I’m in something called a sober living, long story) anyway, just about any program other than safari/firefox/google chrome are unable to access the internet. Steam is able to view webpages through it for very basic functions like accessing the workshop and uploading my achievements, but otherwise is blocked. THis is highly frustrating, but since I’m using the no-steam crack for the creation kit, I would highly doubt that this is affecting my creation kit. but you never know, just incase it somehow requires internet, thought that I’d post that detail.
Any help would be greatly appreciated, thanks all for reading.