Author Topic: RELEASE  (Read 12285 times)

0 Members and 1 Guest are viewing this topic.

Hyper

  • Administrator
  • Mission Commander
  • *****
  • Posts: 1231
RELEASE
« on: September 26, 2015, 03:12:56 PM »
Over the last week GoDaddy has migrated the website over to a different server. We had to back up the forum with and older version and data was corrupted and or lost.
I will go through this and other website / forum / game issues so please bear with me.


rditto48801

  • Mission Commander
  • *****
  • Posts: 149
  • Wait, this isn't Duna.
Re: RELEASE
« Reply #1 on: September 26, 2015, 06:30:20 PM »
Maybe that is why I ran into a 404 error in one place. The MC:C info page has an old forum link, http://hyperkat.com/litterbox.

Also, fyi, MC:F seems to have already yielding a number of effectively game breaking (and colonist killing) bugs myself and others have run into.
And in typical internet fashion, some people are slightly overreacting to said bugs. (or else the trolls are already showing up on the Steam forums for MC:F...)
Edit:
Correction, it looks like there is at least one troll on the loose on the Steam MC:F forum....
End edit

Where the heck does MC:F store its logs at?

Edit 2:
Holy crap MC:F's ratings on Steam are sliding downhill quick.
When you get the website issue dealt with, it looks like you have a fair bit of damage control to do.

Could this server move thing have caused a bad/corrupt/outdated version of MC:F to be uploaded to Steam?
« Last Edit: September 26, 2015, 07:51:24 PM by rditto48801 »
Boldly going forward, 'cause I can't find reverse.

Doctor Watson; Proving that being wrong means being one step closer to being right.

jebusno2

  • Private
  • **
  • Posts: 11
Re: RELEASE
« Reply #2 on: September 27, 2015, 09:38:36 AM »
I have a major bug when i try to start single player. the game just gives me a popup that says error reading png file:IDAT: CRC error. however when i validate files steam says nothing is wrong. What is going on? I have attached a screenshot of the error.

Hyper

  • Administrator
  • Mission Commander
  • *****
  • Posts: 1231
Re: RELEASE
« Reply #3 on: September 27, 2015, 10:42:00 AM »
It seems some data may have got corrupted, trying to work on the details now. The version I run here runs perfect, can't crash it on 5 different computers.
I understand the Map but is being worked around using low texture setting in the options dialog. Which would point to a bad PNG file. Once I get back healthy I will be going through and verifying the game / textures etc.
Also had different modes in there but the way steam saves data caused some issues on how I read and write the code.
As for this version being dummed down If you look into it more, player build sub modules are better quality so they produce more and break less.
Competition mode with NPC active will be put back in soon and the story modes are there just not completed. Room for updates as we planned each week something new added.
Bear with us till we get the corrupted art files dealth with...

Thanks, it will only get better from here...

rditto48801

  • Mission Commander
  • *****
  • Posts: 149
  • Wait, this isn't Duna.
Re: RELEASE
« Reply #4 on: September 27, 2015, 12:26:19 PM »
I got textures on lowest and have not had any map crashes sense.

So I only have three issues at the moment.
First, the fact the 'building' part of the power module is missing on my base after I built the life support module. The equipment still works at least, and the base is still powered.

Second, I got promoted to Specialist after a skill leveled up while doing farm stuff, got a message saying there was a reward incoming, and to report to the command center.
I went to the main base, talked to the base commander, and he just said the same old thing he always does. I didn't get any sort of item or any credits.
Is there a delay until the reward pops up? Or am I missing something?

Third. Tomatoes have a sell price of 0. And unless I missed them, they are not sold.
Edit: Of note, I had sold two tomatoes, not noticing the 0 value until I was hitting the sell button on the second one. I reloaded my game after a short break and both tomatoes were back in inventory... End Edit.

I recall all the work that went into MC:C, so I don't mind waiting, and working through the issues that can be worked around.
Although my next hurdle is to figure out what to do with a box of full of ore from a new auger, since it sort of skipped my mind that I can't process it if I can't use the main base ore processor. (maybe I should check that again since I got promoted... otherwise, time to focus on selling plant based foods...) Edit: n/m, found out I can just sell ore strait out of the ore box. End edit.

Will it work okay if I just put several hubs next to each other, so I can pack stuff like farms and whatnot close together to keep the base compact?

If I put down an empty module, can I upgrade it later to one of the other module types? Or is it stuck as being empty?

I am guessing stuff like waste containers were removed from the game.

Oh, here is the end of a log the last time I had the map crash. I had left the base, walked a short ways, checked map, and crash.

Code: [Select]
AIRLOCK
SOUND PROFILE InsideAmbientSound
LEFT MOUSE
SELECT OBJECT CALLED
CLEAR THE TARGET
LEFT MOUSE
SELECT OBJECT CALLED
USE TYPE 5
TAG A DOOR 300
BUILDING
OK 1
AIRLOCK
MAP AWAKE
CLEAR DOTS 64 65
CLOSE MAP CALLED
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(72,10): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(73,10): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(74,10): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(75,10): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(84,18): warning X3206: 'autogenUncondition_55070f7a': implicit truncation of vector type
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(85,18): warning X3206: 'autogenUncondition_55070f7a': implicit truncation of vector type
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(86,18): warning X3206: 'autogenUncondition_55070f7a': implicit truncation of vector type
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(87,18): warning X3206: 'autogenUncondition_55070f7a': implicit truncation of vector type
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(88,14): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(88,14): warning X3206: implicit truncation of vector type
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_DownSample_P.hlsl(88,11): warning X3550: array reference cannot be used as an l-value; not natively addressable, forcing loop to unroll
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_CalcCoC_P.hlsl(39,11): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_CalcCoC_P.hlsl(40,12): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(54,8): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(55,8): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(56,8): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(57,8): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(75,12): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(103,8): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(106,10): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(117,12): warning X3206: 'autogenUncondition_55070f7a': implicit truncation of vector type
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(117,10): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(131,14): warning X3205: conversion from larger type to smaller, possible loss of data
B:/Steam/steamapps/common/Mars Colony Frontier/shaders/common/postFx/dof/DOF_Final_P.hlsl(132,11): warning X3205: conversion from larger type to smaller, possible loss of data
LEFT MOUSE
SELECT OBJECT CALLED
CLEAR THE TARGET

Edit of edit:
Hyper, I am sending a PM regarding someone posting a link somewhere for an old MC Alpha.
« Last Edit: September 27, 2015, 12:58:40 PM by rditto48801 »
Boldly going forward, 'cause I can't find reverse.

Doctor Watson; Proving that being wrong means being one step closer to being right.

jebusno2

  • Private
  • **
  • Posts: 11
Re: RELEASE
« Reply #5 on: September 27, 2015, 12:50:07 PM »
I tried every setting on lowest and still got the exact same error message.

rditto48801

  • Mission Commander
  • *****
  • Posts: 149
  • Wait, this isn't Duna.
Re: RELEASE
« Reply #6 on: September 27, 2015, 01:10:53 PM »
I tried every setting on lowest and still got the exact same error message.
So you tried Verifying Integrity of Game Cache, but that didn't fix it?
If all else fails, maybe use the Delete Local Content for MC:F and then reinstall?

I did notice someone else on the Steam Forums having an unusual but possibly unrelated problem with loading missions, which makes me think of another thing.
Are you by any chance using the default player profile?
Boldly going forward, 'cause I can't find reverse.

Doctor Watson; Proving that being wrong means being one step closer to being right.

jebusno2

  • Private
  • **
  • Posts: 11
Re: RELEASE
« Reply #7 on: September 27, 2015, 01:32:18 PM »
The same error happened with a custom profile as with the default.

rditto48801

  • Mission Commander
  • *****
  • Posts: 149
  • Wait, this isn't Duna.
Re: RELEASE
« Reply #8 on: September 27, 2015, 02:12:20 PM »
Then I am out of ideas, beyond uninstalling and reinstalling.
Boldly going forward, 'cause I can't find reverse.

Doctor Watson; Proving that being wrong means being one step closer to being right.

jebusno2

  • Private
  • **
  • Posts: 11
Re: RELEASE
« Reply #9 on: September 28, 2015, 04:23:28 AM »
Ok i reinstalled and i work i can get into single player but a new error has appeared the game works fine for a while and it appears to be random but after i open the map a few times one of those times will cause a run time error to appear and crash the game. Also when this happens the process appears to keep running in the task manager until i manually stop it.

jebusno2

  • Private
  • **
  • Posts: 11
Re: RELEASE
« Reply #10 on: September 28, 2015, 04:56:47 AM »
Sorry if this sounds dumb but how do you turn on the lights in player made bases?

rditto48801

  • Mission Commander
  • *****
  • Posts: 149
  • Wait, this isn't Duna.
Re: RELEASE
« Reply #11 on: September 28, 2015, 06:12:32 AM »
No clue. I've tried interacting with those little screens next to the doorways, but didn't notice anything happening.
I think they turn on by themselves in some cases. At least some modules have minimal lighting at night. The light outside of the airlock seems a bit on the dim side, the the main issue might just be the lights are not to bright in the first place.
Boldly going forward, 'cause I can't find reverse.

Doctor Watson; Proving that being wrong means being one step closer to being right.

jebusno2

  • Private
  • **
  • Posts: 11
Re: RELEASE
« Reply #12 on: September 28, 2015, 06:27:56 AM »
So no lighting like in Challenger? Also the map crash seems to happen anytime AFTER you accept a mission from the guy outside the base. Then if you validate the files and re-enter the game you arre in the same spot but have no eva gear and nothing in the missions tab on the pda.

rditto48801

  • Mission Commander
  • *****
  • Posts: 149
  • Wait, this isn't Duna.
Re: RELEASE
« Reply #13 on: September 28, 2015, 06:40:12 AM »
There are apparently lights, just no option to turn them on/off manually.
It wouldn't be to bad if the base wasn't so poorly lit in some areas.

A map crash? Have you set Textures to Lowest in PC Settings on the Main Menu?
The game seems to 'randomly' save different details, like player stats, inventory, rover location, etc. So when it crashes, it doesn't update stuff properly, and loads up 'older' data... which is hell at start, because the 'original' states are 0 food/water, no EVA power/O2, and no fuel in the Rover. And since the O2/Methane transport containers are apparently not in game, you likely get a 500 credit paper weight...

I've had a crash with interesting results. After restarting the game and loading the mission, I popped up where I was a minute before the crash, next to the repair bench when I repaired something for a repair part mission, with food/water of when I first got to the main base after returning from my base in the NE (so I had to buy more food since I ate at the main base after I got there), and after a long walk to my base NE (which took 35 O2/Power for EVA), I found my rover back at my base NE, with the fuel it had before my trip to the main base.

I've learned to 'save and quit' after getting major things done, even though it means restarting the game, just to be on the safe side. With Textures set at Lowest, I have not had any crashes when using the map.
(A 'quit to main menu' option would be nice)

@ Hyper, in case you missed it, I have been adding more bug report and suggestion type stuff to my post in the other thread.
http://hyperkat.com/scratchbox/index.php?topic=863.0
« Last Edit: September 28, 2015, 06:43:11 AM by rditto48801 »
Boldly going forward, 'cause I can't find reverse.

Doctor Watson; Proving that being wrong means being one step closer to being right.

jebusno2

  • Private
  • **
  • Posts: 11
Re: RELEASE
« Reply #14 on: September 28, 2015, 02:29:14 PM »
The thing im having trouble with at the moment is the stamina. It really runs down much to fast does the loss rate improve as you rank up or can it be changed to at least recover faster?