Rev.12087: game doesn't run properly anymore
-
- Trader
- Posts: 25
- Joined: Mon Mar 24, 2008 10:11 pm
Rev.12087: game doesn't run properly anymore
Hi,
I just updated my svn version and the game became unplayable. When i run it, it starts without splashscreen and in window-mode. I can look around the docked base, but when i start the ship none of the controls are working. I first thought it's an issue with a config file and so I chmod u+w all files to permit write access and reran the setup-program, but that didn't helped either. Any ideas?
Edit:
I have to say, i didn't compile the game by myself but just used the precompiled version in data4.x/bin
I just updated my svn version and the game became unplayable. When i run it, it starts without splashscreen and in window-mode. I can look around the docked base, but when i start the ship none of the controls are working. I first thought it's an issue with a config file and so I chmod u+w all files to permit write access and reran the setup-program, but that didn't helped either. Any ideas?
Edit:
I have to say, i didn't compile the game by myself but just used the precompiled version in data4.x/bin
-
- The Shepherd
- Posts: 5841
- Joined: Fri May 13, 2005 8:37 pm
- Location: Ottawa
- Contact:
That's the widows build then is it not could you post stdout.txt and stderr.txt from that bin folder.
Enjoy the Choice
Enjoy the Choice
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
-
- Trader
- Posts: 25
- Joined: Mon Mar 24, 2008 10:11 pm
here they are....
I changed my local path.. so don't wounder it really IS the windows-version that i want
in the error-logs there is something about a nova-class ship... in-game i'm on a planet, i've never seen before. I can't see a ship, but the computer tells me, i own a blank nova-class ship... never seen or heard of before neither in nor outgame
Edit: pic of planet attached...
I changed my local path.. so don't wounder it really IS the windows-version that i want
in the error-logs there is something about a nova-class ship... in-game i'm on a planet, i've never seen before. I can't see a ship, but the computer tells me, i own a blank nova-class ship... never seen or heard of before neither in nor outgame
Edit: pic of planet attached...
You do not have the required permissions to view the files attached to this post.
-
- The Shepherd
- Posts: 5841
- Joined: Fri May 13, 2005 8:37 pm
- Location: Ottawa
- Contact:
from the behavior you describe and those logs it appears that it is running one of the test missions not the default main_menu_mission possible corruption data side is my first call.
Enjoy the Choice
Enjoy the Choice
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
-
- Trader
- Posts: 25
- Joined: Mon Mar 24, 2008 10:11 pm
okay..... i took the launcher and changed the scenario to main_menu.mission. I'm not on the planet, but on the startingbase and have a LLama instead of Nova, but all other problems are still present...
the Llama is named llama.begin, is completely unequippted and is not displayed in the hanger. When i start with that thing, i'm not able to steer it. I'm not even able to turn off the initial bordcomputer-helpscreen by pressing Shift-M
the Llama is named llama.begin, is completely unequippted and is not displayed in the hanger. When i start with that thing, i'm not able to steer it. I'm not even able to turn off the initial bordcomputer-helpscreen by pressing Shift-M
-
- Bounty Hunter
- Posts: 182
- Joined: Sat Jul 21, 2007 5:14 am
- Location: Western MA
iv seen this imame before
Multiple config or a corrupted config file will do this look in the data directory and find the config file that matches the svn ver ie 12087 your playing delete the rest
Bill
Bill
Machine: P4 prescott 3.2 Ghz, 2Gb ddr ram, 2 80g seagate sata drives in raiad stripe config nvidia 6600 gt oc card sidwinder pro FF2
-
- The Shepherd
- Posts: 5841
- Joined: Fri May 13, 2005 8:37 pm
- Location: Ottawa
- Contact:
Part of your problem is using launcher with the in game menu now it just confuses things it really should be deleted and as whatch1 mentioned your old config and or saves also have an effect.I always start a new exe version with a clean .vegastrike folder to minimize problems.
Enjoy the Choice
Enjoy the Choice
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
-
- Developer
- Posts: 2150
- Joined: Mon Apr 23, 2007 1:17 am
- Location: Pennsylvania
- Contact:
this problem is most definitely caused by a crapped out data4.x config file. It occurs when you update and someone made a commit that updates the config file in the data4.x repository
WE _NEED_ to get the user config files working so vssetup doesn't write to the default data4.x config file.
WE _NEED_ to get the user config files working so vssetup doesn't write to the default data4.x config file.
Ed Sweetman endorses this message.
-
- Lead Network Developer
- Posts: 2560
- Joined: Sun Jan 12, 2003 9:13 am
- Location: Palo Alto CA
- Contact:
You can just delete the vegastrike.config file in your data4.x folder
The do a "svn update" and it will restore that configuration to the defaults.
The config file is very likely in a SVN conflicted state which has a bunch of "<<<<" characters in it and will make the engine to do weird stuff (at the moment it tries to keep running with whatever guesses it has at the configuration)
The do a "svn update" and it will restore that configuration to the defaults.
The config file is very likely in a SVN conflicted state which has a bunch of "<<<<" characters in it and will make the engine to do weird stuff (at the moment it tries to keep running with whatever guesses it has at the configuration)
-
- Developer
- Posts: 2150
- Joined: Mon Apr 23, 2007 1:17 am
- Location: Pennsylvania
- Contact:
-
- Developer
- Posts: 2150
- Joined: Mon Apr 23, 2007 1:17 am
- Location: Pennsylvania
- Contact:
the proper fix is to not write to data4.x's vegastrike.config file.
Writing the config file will change after 0.5. Since we'll have an options class, with all the options in the game, we'll be able to write a config file with all options accounted for. With any luck, later on we'll have a vssetup that makes hand editing the config file a thing of the past.
Writing the config file will change after 0.5. Since we'll have an options class, with all the options in the game, we'll be able to write a config file with all options accounted for. With any luck, later on we'll have a vssetup that makes hand editing the config file a thing of the past.
Ed Sweetman endorses this message.
-
- Trader
- Posts: 25
- Joined: Mon Mar 24, 2008 10:11 pm
that won't fix the problem, because as long as the file remains in the repository there will be conflicts between the config of the comitter and the config of the updater, no matter if it's edited by hand or by setup.safemode wrote:the proper fix is to not write to data4.x's vegastrike.config file.
Writing the config file will change after 0.5. Since we'll have an options class, with all the options in the game, we'll be able to write a config file with all options accounted for. With any luck, later on we'll have a vssetup that makes hand editing the config file a thing of the past.
-
- Bounty Hunter
- Posts: 182
- Joined: Sat Jul 21, 2007 5:14 am
- Location: Western MA
Config files
I've been playing long enough to ma an observation
during the svn update in windows multple config fieles arive in conflict with one another the end up with names cofig.12078 for example but not replacing the current working file when most recently i've seen multiple numbered config file i then delete my current config file and remame the current numbered file to match the the deleted one so the config file matches the data set
Is this the correct procedure?
or am i blowing smoke
Bill
during the svn update in windows multple config fieles arive in conflict with one another the end up with names cofig.12078 for example but not replacing the current working file when most recently i've seen multiple numbered config file i then delete my current config file and remame the current numbered file to match the the deleted one so the config file matches the data set
Is this the correct procedure?
or am i blowing smoke
Bill
Machine: P4 prescott 3.2 Ghz, 2Gb ddr ram, 2 80g seagate sata drives in raiad stripe config nvidia 6600 gt oc card sidwinder pro FF2
-
- The Shepherd
- Posts: 5841
- Joined: Fri May 13, 2005 8:37 pm
- Location: Ottawa
- Contact:
There is also my particular solution to this I don't run the game in my svn repository but in a separate exported copy so the repo stays clean at all times.
Enjoy the Choice
Enjoy the Choice
my box::HP Envy i5-6400 @2Q70GHzx4 8 Gb ram/1 Tb(Win10 64)/3 Tb Mint 19.2/GTX745 4Gb acer S243HL K222HQL
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
Q8200/Asus P5QDLX/8 Gb ram/WD 2Tb 2-500 G HD/GF GT640 2Gb Mint 17.3 64 bit Win 10 32 bit acer and Lenovo ideapad 320-15ARB Win 10/Mint 19.2
-
- Lead Network Developer
- Posts: 2560
- Joined: Sun Jan 12, 2003 9:13 am
- Location: Palo Alto CA
- Contact:
that way works, but I find it much easier to do a "svn revert vegastrike.config" or on windows, right click on it in Tortoise and go to SVN and Revert.
What safemode was talking about was that this should and will be changed after the release.
The conflicts won't affect people who download the released software since it won't change.
What safemode was talking about was that this should and will be changed after the release.
The conflicts won't affect people who download the released software since it won't change.
-
- Developer
- Posts: 2150
- Joined: Mon Apr 23, 2007 1:17 am
- Location: Pennsylvania
- Contact:
vegastrike.config wont be a problem after 0.5 is done because we're moving to a user-based config file setup. where vssetup only writes to a seperate config file, and only reads the default config file to get defaults in the case that the user wants to reset the config to defaults, or the user's config file doesn't yet exist.
In this way, the default config file (only one in repository) wont ever change unless we are making changes to the default configuration. vssetup wont be able to do that, so testing and playing (which does currently write to vegastrike.config in data4.x) wont have any affect on the repository's files.
In this way, the default config file (only one in repository) wont ever change unless we are making changes to the default configuration. vssetup wont be able to do that, so testing and playing (which does currently write to vegastrike.config in data4.x) wont have any affect on the repository's files.
Ed Sweetman endorses this message.