Testing environment for non-mod changes

Post here if you want to help developing something for FAF.

Re: Testing environment for non-mod changes

Postby nine2 » 14 Oct 2015, 12:24

- delete your log file
- delete your git repository
- get the git repository again (so that its clean and working)
- run it
- if it breaks post your entire log file


i guess its possible that dev branch is broken...

edit: i dont think its broken, but i have a github rating of -100 so you never know
nine2
Councillor - Promotion
 
Posts: 2416
Joined: 16 Apr 2013, 10:10
Has liked: 285 times
Been liked: 515 times
FAF User Name: Anihilnine

Re: Testing environment for non-mod changes

Postby Korbah » 14 Oct 2015, 15:15

Thx for getting back to me


I've re-extracted fa-develop from the github repository and unzipped it:
(here: C:\ProgramData\FAForever\bin\fa-develop)

I've followed the instructions again from this thread: viewtopic.php?f=3&t=192

I've got a custom shortcut with this as it's target:
C:\ProgramData\FAForever\bin\ForgedAlliance.exe /init "init_dev.lua" /log Korbah_mod_log.txt /EnableDiskWatch

I've remade a fresh init_dev.lua
-> here's a paste with the correct repository reported in the first line: http://pastebin.com/index/pksA3tky

Here's the error message I get when I run the shortcut:
http://pastebin.com/index/9thNHcD6

I've deleted the logs in: C:\ProgramData\FAForever\logs
When I run the shortcut no new logs are generated
Korbah
Avatar-of-War
 
Posts: 225
Joined: 01 May 2012, 16:27
Has liked: 7 times
Been liked: 12 times
FAF User Name: Korbah

Re: Testing environment for non-mod changes

Postby nine2 » 14 Oct 2015, 16:26

edit your init_dev.lua and change the first word to "dev_path" (not "DevPath")

otherwise:
its weird to put it inside C:\ProgramData\ - why? because of permissions
I'd move it to somewhere like c:\myfolder\fa-develop
you could try changing your shortcut to use init_faf.lua. this would make sure the rest of your shortcut isnt causing trouble, eg: working folder
nine2
Councillor - Promotion
 
Posts: 2416
Joined: 16 Apr 2013, 10:10
Has liked: 285 times
Been liked: 515 times
FAF User Name: Anihilnine

Re: Testing environment for non-mod changes

Postby Korbah » 14 Oct 2015, 17:07

thx for the reply


I've edited init_Dev.lua as you suggested - still doesn't work


I can use init_faf.lua to correctly start without issues - obviously I'm not accessing the repository files though.

I moved the repository files out of c:\programdata, edited init_Dev.lua to point at them - still doesn't work. unhandled exception again. I've also moved the shortcut into the new directory and it still doesn't work.



Not sure what I'm doing wrong
Korbah
Avatar-of-War
 
Posts: 225
Joined: 01 May 2012, 16:27
Has liked: 7 times
Been liked: 12 times
FAF User Name: Korbah

Re: Testing environment for non-mod changes

Postby nine2 » 14 Oct 2015, 17:21

the init_dev file you had originally had a critical error in it... maybe there were others. copy and paste from the readme on github then just change the path
nine2
Councillor - Promotion
 
Posts: 2416
Joined: 16 Apr 2013, 10:10
Has liked: 285 times
Been liked: 515 times
FAF User Name: Anihilnine

Re: Testing environment for non-mod changes

Postby Korbah » 14 Oct 2015, 22:40

I've copied the init_Dev.lua content from here: /viewtopic.php?p=87570 as instructed. It still doesn't work. I've no idea what I'm doing wrong as I seem to have gone through step-by-step the instructions.

Latest error message:

Unhandled exception:

attempt to get as string a nil value
stack traceback:

Program : C:\ProgramData\FAForever\bin\ForgedAlliance.exe
Cmd line arguments : /init init_dev.lua /log Korbah_mod_log.txt /EnableDiskWatch

Callstack:
Unknown symbol (address 0x008d462c)

Last 100 lines of log...

info: checking C:\Users\William\Documents\My Games\Gas Powered Games\Supreme Commander Forged Alliance\mods
info: checking C:\Users\William\Documents\My Games\Gas Powered Games\Supreme Commander Forged Alliance\maps
info: checking C:\ProgramData\FAForever\bin\..\user\My Games\Gas Powered Games\Supreme Commander Forged Alliance\mods
info: checking C:\ProgramData\FAForever\bin\..\user\My Games\Gas Powered Games\Supreme Commander Forged Alliance\maps
Korbah
Avatar-of-War
 
Posts: 225
Joined: 01 May 2012, 16:27
Has liked: 7 times
Been liked: 12 times
FAF User Name: Korbah

Re: Testing environment for non-mod changes

Postby nine2 » 15 Oct 2015, 00:57

Change your init file to point at an empty folder, which is valid.
If it crashes there is a problem with your init
Else there is something wrong with your github copy of repo
nine2
Councillor - Promotion
 
Posts: 2416
Joined: 16 Apr 2013, 10:10
Has liked: 285 times
Been liked: 515 times
FAF User Name: Anihilnine

Re: Testing environment for non-mod changes

Postby Korbah » 15 Oct 2015, 14:28

It crashes when I point it at an empty folder - I think there's a problem with init_dev.lua. Init_faf.lua works fine - but obviously cannot allow realtime editing

I've remade init_Dev.lua several times with copypasta from the instructions as a fresh file and it still doesn't work. I've redownloaded github repository. Is there a chance the init_dev.lua is no longer compatible with faf?
Korbah
Avatar-of-War
 
Posts: 225
Joined: 01 May 2012, 16:27
Has liked: 7 times
Been liked: 12 times
FAF User Name: Korbah

Re: Testing environment for non-mod changes

Postby nine2 » 15 Oct 2015, 15:26

Unlikely. I used the one from github readme - u used one from forum.
nine2
Councillor - Promotion
 
Posts: 2416
Joined: 16 Apr 2013, 10:10
Has liked: 285 times
Been liked: 515 times
FAF User Name: Anihilnine

Re: Testing environment for non-mod changes

Postby nine2 » 15 Oct 2015, 15:27

Post your file
nine2
Councillor - Promotion
 
Posts: 2416
Joined: 16 Apr 2013, 10:10
Has liked: 285 times
Been liked: 515 times
FAF User Name: Anihilnine

PreviousNext

Return to Contributors

Who is online

Users browsing this forum: No registered users and 1 guest