Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - ai_enabled

#1681
Modding info / Re: New with Steam Version
December 01, 2014, 01:40:35 AM
I do small fix for this issue and get this log:
Parsing errors:
*1) "btc.mpk\data\items\hulls\hull_avalanche.xml":
    1) Already parsed xml object with ID=hull_aurora
*2) "btc.mpk\data\items\hulls\hull_avalanche_mk2.xml":
    1) Already parsed xml object with ID=hull_avalanche
*3) "btc.mpk\data\items\hulls\hull_banshee.xml":
    1) Already parsed xml object with ID=hull_avalanche_mk2
*4) "btc.mpk\data\items\hulls\hull_banshee_mk2.xml":
    1) Already parsed xml object with ID=hull_banshee
*5) "btc.mpk\data\items\hulls\hull_boomerang.xml":
    1) Already parsed xml object with ID=hull_banshee_mk2
*6) "btc.mpk\data\items\hulls\hull_crab.xml":
    1) Already parsed xml object with ID=hull_boomerang
*7) "btc.mpk\data\items\hulls\hull_death_bringer.xml":
    1) Already parsed xml object with ID=hull_crab
*8) "btc.mpk\data\items\hulls\hull_dio_i.xml":
    1) Already parsed xml object with ID=hull_death_bringer
*9) "btc.mpk\data\items\hulls\hull_falcon.xml":
    1) Already parsed xml object with ID=hull_endeavor
*10) "btc.mpk\data\items\hulls\hull_freighter.xml":
    1) Already parsed xml object with ID=hull_fang
*11) "btc.mpk\data\items\hulls\hull_freighter_npc.xml":
    1) Already parsed xml object with ID=hull_freighter
*12) "btc.mpk\data\items\hulls\hull_hammer.xml":
    1) Already parsed xml object with ID=hull_freighter_npc
*13) "btc.mpk\data\items\hulls\hull_hds_i.xml":
    1) Already parsed xml object with ID=hull_hammer
*14) "btc.mpk\data\items\hulls\hull_hive.xml":
    1) Already parsed xml object with ID=hull_heretic
*15) "btc.mpk\data\items\hulls\hull_hph_c.xml":
    1) Already parsed xml object with ID=hull_hive
*16) "btc.mpk\data\items\hulls\hull_pers_i.xml":
    1) Already parsed xml object with ID=hull_orca
*17) "btc.mpk\data\items\hulls\hull_pest_red.xml":
    1) Already parsed xml object with ID=hull_pest_brown
*18) "btc.mpk\data\items\hulls\hull_pirate_platform.xml":
    1) Already parsed xml object with ID=hull_pest_red
*19) "btc.mpk\data\items\hulls\hull_sea_i.xml":
    1) Already parsed xml object with ID=hull_pirate_platform
*20) "btc.mpk\data\items\hulls\hull_turret_platform.xml":
    1) Already parsed xml object with ID=hull_shuttle
*21) "btc.mpk\data\items\hulls\hull_turret_xengatarn.xml":
    1) Already parsed xml object with ID=hull_turret_platform
*22) "btc.mpk\data\items\hulls\hull_violator.xml":
    1) Already parsed xml object with ID=hull_turret_xengatarn
*23) "btc.mpk\data\items\hulls\hull_zeus_i.xml":
    1) Already parsed xml object with ID=hull_violator


This is because we changed "hulls" folder structure, and now your hulls definitions do not override same hulls from core mod as they're have different paths now. And game failed to load same hull from two different folders. Please relocate your hulls definitions to the same sub-folders as we do in core.mod.

The fixed server will be available with the next build for Steam.
#1682
Modding info / Re: New with Steam Version
November 30, 2014, 09:22:47 PM
Hammish, ok, I will investigate the issue.
#1683
Quote from: kyokei on November 30, 2014, 02:27:56 AM
I'll continue here... AI next issue :)

https://cloud.kunix.org/public.php?service=files&t=4458dcd923f49f49e6a7d5fc4667a111

let me know what you need, here are the player logs:

https://cloud.kunix.org/public.php?service=files&t=4f522eca9dd4cfd882fb38e10dc8e811
Is the game working now except this issue? How often this issue happens?
Please try to increase the MSAA setting to x4 and set the UI anti-aliasing to "MSAA" mode. This may help.
#1684
Quote from: kyokei on November 29, 2014, 11:06:48 AMWell whatever I try I can't get it to work... any other tips?
I have some ideas, sent you a PM.

Quote from: Valkor on November 29, 2014, 07:57:18 PMIt isn't random for me, every single time I click + it will crash.
That's good for debugging! I've sent you a PM.
#1685
Modding info / Re: New with Steam Version
November 29, 2014, 10:49:35 PM
Quote from: Hammish on November 29, 2014, 11:38:14 AM
Also, with new patch I'm not able to actually launch BTC now
Hello! In case of a strange errors/unhandled exceptions always send us a log, screenshot and the mod itself please - because it's 100% our fail.
So please upload the mod somewhere and send me a PM with link.
Regards!
#1686
Quote from: kyokei on November 29, 2014, 01:23:23 AM
What happens is that steam says I am playing VoidExpanse but no screen ever opens, and then steams says I am play no game anymore.
When I click play it shows for 1 sec the screen preparing to play VE and then it disappears.
I am redownloaded, verified integrity etc
I've tested the game now on my Mac for several hours and yes, I reproduced this issue. I need to say the Unity is so unstable on Mac... usually it works (especially if the game started without any problem - then it usually works flawlessly, that's why I think the game was stable enough...), but freezes happens often upon quit, or process remains opened after quit (but no window/screen present). The only way to fix it now - kill "VoidExpanse" process from the Process Monitor application and start it again from Steam.
BTW, we decided to remove the "retina" mode on Mac as it requires "old fullscreen overlay" Unity setting, which is incompatible with Steam overlay features, and you cannot switch on another applications while playing (this also became a very big problem if the game freezes!). Shame on Unity they're still not supporting retina resolutions on "windowed" Unity setting on Mac... in Windows it works right of the box (and with much better FPS).
Hope we can improve stability on Mac in next build.
#1687
Quote from: Valkor on November 29, 2014, 01:04:28 AM
http://pastebin.com/8mLkf2NP
Good to know! Here ya go! Unfortunately I don't see anything that looks like a stack trace in that. I haven't played since the aforementioned crash.
Hmm, looks like some kind of "random" bug, we can't reproduce it whatever we do... If it happens again, please send us logs and screenshots of any exception/stacktrace message.
BTW, I noticed FPS is horrible low - have you tried decreasing the screen resolution? At 1280x720 it should run much better. Also playing with the frame limit (V-Sync) setting may greatly improve performance - on Mac & Linux the V-Sync is often broken, reducing FPS too much... so better to keep the frame limit setting on "60 FPS" (or "30 FPS" for not-so-new laptops to reduce excessive heat).
#1688
Quote from: Valkor on November 28, 2014, 05:42:44 AMTotally playable! Until I go to distribute stat points. Crashes as soon as I hit the + next to a skill.
http://pastebin.com/2cshS8TF
Other than that no problems so far!
Thanks for reporting! How often the crash happens? Could you upload the client log please? The log file you've provided is the local game server log and it doesn't contain any crash information. The client log located somewhere at ~/.config/unity3d/ (Player.log file, unfortunately we're unable to write it into "Logs" folder yet).
#1689
Quote from: kyokei on November 28, 2014, 03:31:01 PM
Can't get the game started on my mac, can you remind me where to find the logs on Mac?
It is located at "~/Library/Logs/Unity/" file Player.log. No problems running the game on my MacBook Retina.

FlessenGreendart, thanks for reporting! Some quests are still broken, we decided to push this update to verify the other reported issues has been fixed.
"Test character name" is very strange issue, will try to reproduce and fix it.
#1690
Quote from: FlessenGreendart on November 27, 2014, 03:39:41 PMHey, quick crash report for you
Thanks for reporting! Fixed!

Is seems we've fixed all reported issues, including Linux build freezes problems. Going to release new Steam test build today!
#1691
Quote from: Valkor on November 24, 2014, 09:43:37 PMFound the actual logs!
Thank you for logs. Issue reproduced. We're working on fix.
#1692
Quote from: Tchey on November 23, 2014, 01:16:52 AMTrying the Steam Version for the first time, on Win7 64 bits computer now.
Hello! Thanks for reporting about issues and posting screenshots!
It's very strange that game runs the game server in console window (it should be hidden). Do you have this problem with the last stable build, downloaded from AtomicTorch.com?

Could you please run game until it crashes and upload the game logs somewhere? Logs located in two folders:
1. "E:\Steam\steamapps\common\VoidExpanse\Logs" (we need the whole folder, it contains all server logs);
2. "E:\Steam\steamapps\common\VoidExpanse\VoidExpanse_Data\output_log.txt" (we need only this file, it contains a client log from the last launch).
Regards!
#1693
Quote from: FlessenGreendart on November 24, 2014, 05:02:16 PM
A few bugs and things I've noticed
Thanks for reporting! All issues will be fixed soon. The Notifications UI also will be redesigned to complete UI revamp.
Regards!
#1694
Quote from: Valkor on November 24, 2014, 06:39:27 PM
mngrif@kosh:~/.local/share/Steam/SteamApps/common/VoidExpanse$ ls -la
total 17536
drwxr-xr-x  5 mngrif mngrif     4096 Nov 24 05:26 .
drwxr-xr-x 22 mngrif mngrif     4096 Nov 24 05:48 ..
-rwxr-xr-x  1 mngrif mngrif       87 Nov 24 05:23 .launch_args
drwxr-xr-x  2 mngrif mngrif     4096 Nov 24 05:23 Mods
-rwxr-xr-x  1 mngrif mngrif      180 Nov 24 05:24 readme.txt
drwxr-xr-x  2 mngrif mngrif     4096 Nov 24 05:26 Server_Mono
-rwxr-xr-x  1 mngrif mngrif        0 Nov 24 05:26 steam
-rwxr-xr-x  1 mngrif mngrif        9 Nov 24 05:25 version.txt
-rwxr-xr-x  1 mngrif mngrif 17918104 Nov 24 05:26 VoidExpanse
drwxr-xr-x  7 mngrif mngrif     4096 Nov 24 05:26 VoidExpanse_Data


Permissions are correct, Steam can write here just fine.
Hello! For any Unity3D game the log files located at ~/.config/unity3d/ folder. Could you please run the game again until it crashes again and share the log with us. Thanks!
#1695
Quote from: Falknothor on November 21, 2014, 09:12:50 AMMining speed (+45%), Mining amount (+50%) and the mining experience bonus (+100%) are not working as they should.
Thanks for reporting! We've located the issue and fixed it.
Regards!