Missile Prototype 5

Walt

Dalas120 A while back I suggested having EMP missiles briefly toggle the power (like a reboot) on all parts in their AOE, even if those parts aren't drained. Is this still an option? I think it would work really well with the EMP explosion animation.

Even parts like cannons and missile launchers that don't store batteries could still have their power toggled. I think this makes sense, since those parts have clearly visible computers that would be affected by an EMP.

I'm not opposed to this, and it would look cool to see the systems go offline temporarily. I'm not sure about the gameplay utility though.

I do have concerns about toggling power on pars that have not been drained -- that could potentially be confusing for the player.

Dalas120 Would this make sense to do for electrobolts as well? I'm not sure.

Might make electro-bolts too powerful against weapons? Depending on how long the hit weapon goes offline for, it could mean you could spam electrobolts that can just keep enemy weapons offline.

Dalas120 A loooonnggg time ago there was some talk about giving missiles an option to circle around an enemy and home in on a targeted part (instead of trying to fly through an enemy to hit the part). If this is possible, I think it would make sense to do. It would be particularly useful for EMP missiles so they could circle around and target an enemy's engines.

Way back when, I tried an experiment where missiles would circle around to approach at an angle depending on where the targeted part is relative to the center of the target ship. It didn't really work well, it was more annoying than helpful. I'm all for making missile circling a thing, but I think that'd require some sort of UI to allow the player to control the path, and I'm not really sure how that'd work.

Dalas120 Can missile range be varied based on angle? If so, that could provide a reasonable solution to autofired missiles outranging regular missiles - you could reduce missile fuel to match the max range fired straight forward, and make the range for any given angle roughly how far the fuel+guidance would let the missile go at that angle.

I suppose I could, but if autofired missile range is a problem, then I feel like the simpler solution is simply to give missiles a maximum range that they can be from the launcher.

Dalas120 Also, if the last suggestion works, is it possible to have missiles use the same firing prediction algorithm as other weapons (so they'll fire early if an enemy is flying at you quickly)? The algorithm wouldn't have to worry about guidance, just about the target's speed, the missile's fuel, and the missile's range (at the predicted angle).

The problem is that the target prediction algorithm doesn't take acceleration or drag into consideration, which I may or may not be able to add (the drag in particular may be problematic). I'm already worried about this for nukes, and if I can't figure out the algorithm, I'll need to give nukes a bit of guidance to compensate.

Dalas120

Walt I'm not opposed to this, and it would look cool to see the systems go offline temporarily. I'm not sure about the gameplay utility though.

Right now, I don't see it being especially useful against anything but engines (though maybe someone will find a creative use). In the future, it might be a great way to break a tractor beam lock or to interrupt a charging blink drive.

Walt I do have concerns about toggling power on pars that have not been drained -- that could potentially be confusing for the player.

I think it makes sense given the EMP explosion animation, assuming it hasn't changed much since you posted it on discord. Any part caught in the yellow circle gets rebooted; any part hit by a lightning arc gets drained. Otherwise the yellow circle is nothing but a range indicator, which seems a little strange for an effect that cool.

Walt Might make electro-bolts too powerful against weapons? Depending on how long the hit weapon goes offline for, it could mean you could spam electrobolts that can just keep enemy weapons offline.

Yeah, that's a good point. It could be especially dangerous vs slow-firing weapons like cannons, since every time they get hit their cooldown will reset so they'll never get to fire, even if the reboot time is extremely short.

Though it would cost an excessive amount of micromanagement to make that work, and even then it would be much less effective vs anything except cannons.

Walt Way back when, I tried an experiment where missiles would circle around to approach at an angle depending on where the targeted part is relative to the center of the target ship. It didn't really work well, it was more annoying than helpful. I'm all for making missile circling a thing, but I think that'd require some sort of UI to allow the player to control the path, and I'm not really sure how that'd work.

Can this be done with the missile collision avoidance system? Maybe the missile will try to avoid every part of the enemy ship that's not between the targeted part and the ship circle? I'm not sure how that would behave.

Walt I suppose I could, but if autofired missile range is a problem, then I feel like the simpler solution is simply to give missiles a maximum range that they can be from the launcher.

I don't think this is ideal, because 1) it makes it very hard to use high-speed "bomber" designs, 2) it removes part of what makes missiles feel unique (the ability to chase a target) and 3) it feels weird. That being said my solution isn't ideal either. I'll think about this a bit more.

Walt

Dalas120 Can this be done with the missile collision avoidance system? Maybe the missile will try to avoid every part of the enemy ship that's not between the targeted part and the ship circle? I'm not sure how that would behave.

Maybe? I suspect missile collision avoidance would need to be improved.

Dalas120 I don't think this is ideal, because 1) it makes it very hard to use high-speed "bomber" designs, 2) it removes part of what makes missiles feel unique (the ability to chase a target) and 3) it feels weird. That being said my solution isn't ideal either. I'll think about this a bit more.

It'd be a bit arbitrary, but missile range could potentially be limited only when auto-fired.

falcon500

Walt Can point defense be able to shoot into low penetration-resistance areas and kill crew?

Dalas120

Walt It'd be a bit arbitrary, but missile range could potentially be limited only when auto-fired.

Yeah, maybe that's the best way to do it - it's definitely the simplest. It would be a little odd, but no more so than cannon shells vanishing.

Walt FWIW, factories have twice the priority as weapons. (Meaning, a half-powered factory has the same priority as an empty weapon.)

This doesn't seem to be working properly. On the prototype, testing a module with 1 small cannon, 1 ammo factory, 1 reactor, and 2 crew shows that the crew continues to bring ammo to the cannon even after the factory is completely out of power.

Walt And now, as of the 0.14.5 prototypes, there's a 10% priority penalty per tile of distance that the crew would have to walk to get to the new job. So if the missile launchers were far enough apart, the crew would usually only switch when they had literally nothing else to do.

This doesn't seem to work very well for missiles, which I think might be because missiles demand wildly variable number of crew as they fill up (a launcher could have 9 parts inside and only demand 3 crew). So crew often don't have jobs and start walking to a far-away launcher, except seconds after they leave a missile fires and a new job opens up.

At least I think that's what's happening, based on the test ship below. You can also see crew behaving badly when the ship starts empty.

image https://i.imgur.com/92GYvRl.png

Walt Yes for sure, that's how crew will self-balance when there are fewer crew than there are jobs. Without the scaling priorities, you could have 8 crew get assigned to one part and 0 to the other.

If one part is full (or nearly full), wouldn't it only be able to demand 1 or 2 crew at most? That would leave the other crew free to go and work on the other part - AFAIK the only way one part could get 8 crew and the other gets 0 is if they're both empty and all the crew are closest to the same part.

Scaling priorities can also cause (very minor) problems with parts that have charge-up time, like engines. If an engine module doesn't have enough power, all the engines flicker on and off instead of one engine staying on permanently (and having time to ramp up).

And another thought on crew: How do crew decide which factory/storage to go to? Currently, they often go to a farther-away factory even if the closer one is full of ammo (this is especially impactful for missiles). If it's too performance-intensive to always find the nearest non-empty factory, maybe crew could remember their last factory and prefer to go there?

falcon500

Walt I loved the old/new point defense features. Please don't weaken point defense!

falcon500

Walt can point defense target all physical projectiles? (cannon shots and missiles)

falcon500

please make missiles have half again as much damage.

Walt

Dalas120 This doesn't seem to be working properly. On the prototype, testing a module with 1 small cannon, 1 ammo factory, 1 reactor, and 2 crew shows that the crew continues to bring ammo to the cannon even after the factory is completely out of power.

I am unable to reproduce this problem, can I get a saved game or ship? I'm testing using this ship:

image https://i.imgur.com/MNIfSHG.png

Tell the cannon to auto-fire, and the factory will never come close to running out of power.

Dalas120 This doesn't seem to work very well for missiles, which I think might be because missiles demand wildly variable number of crew as they fill up (a launcher could have 9 parts inside and only demand 3 crew). So crew often don't have jobs and start walking to a far-away launcher, except seconds after they leave a missile fires and a new job opens up.

Yeah it doesn't work especially well with missile launchers for exactly the reason you suggest. The increased fire delay might help it a bit for the HE missiles, but the other types will still be a problem.

I've been planning to let weapons "anticipate" needing more ammo when they're actively firing at an enemy, which would request more ammo than the weapon actually has capacity for in the moment, which I think would be a big improvement here.

Dalas120 If one part is full (or nearly full), wouldn't it only be able to demand 1 or 2 crew at most? That would leave the other crew free to go and work on the other part - AFAIK the only way one part could get 8 crew and the other gets 0 is if they're both empty and all the crew are closest to the same part.

That seems like a pretty major exception though, no? Maybe uncommon for competitive PVP ships, but for casual ships I think that could be pretty common.

As an aside, if you want to experiment, priorities are pretty easy to configure by editing the Data/ships/priorities.txt file. You can just set the Low, High, and Empty priority levels to the same value and it should do as you suggest.

Dalas120

Walt I am unable to reproduce this problem, can I get a saved game or ship? I'm testing using this ship:

It looks like the problem is related to the distance between the factory and reactor. Here's a ship that causes the issue for me:

image https://i.imgur.com/3voIvx8.png

Walt Yeah it doesn't work especially well with missile launchers for exactly the reason you suggest. The increased fire delay might help it a bit for the HE missiles, but the other types will still be a problem.

I've been planning to let weapons "anticipate" needing more ammo when they're actively firing at an enemy, which would request more ammo than the weapon actually has capacity for in the moment, which I think would be a big improvement here.

Yeah, I think that would definitely help a lot. If crew end up bringing too much ammo is the extra lost?

IIRC crew can have their jobs interrupted as long as they're not carrying ammo - it would also help if crew would realize "I was going to that launcher but this one also needs crew and is a lot closer."

It might also help if missiles loaded one tube at a time, instead of randomly split between tubes. That way crew demand would vary much less, at least for missiles types that fit multiple projectiles in the barrel (mines(?) and HE).

Though, another option might be to leave crew kind of dumb (especially if making them smart costs a lot of performance/dev time) and expect players to hand-craft their AI with the upcoming configurable crew behavior. That would make mastering crew behavior more rewarding for the player (after all, what's the point of customizing crew behavior if crew are smart anyway), and would keep lots of emphasis on internal design and crew (which I think is one of cosmoteer's most unique parts).

Walt That seems like a pretty major exception though, no? Maybe uncommon for competitive PVP ships, but for casual ships I think that could be pretty common.

Wouldn't this also happen with scaling priorities though? If both parts are empty then they'd both have the same priority?

If multiple parts are completely empty then I don't think it's important for crew to split evenly - all that matters is that they get something up and running. As soon as one part starts to fill up then it can no longer demand as many crew, and some crew will be freed up for other parts even with even priorities.

Walt As an aside, if you want to experiment, priorities are pretty easy to configure by editing the Data/ships/priorities.txt file. You can just set the Low, High, and Empty priority levels to the same value and it should do as you suggest.

Thanks, I didn't realize that! I'll try it out and get back to you.

Walt

Dalas120 It looks like the problem is related to the distance between the factory and reactor. Here's a ship that causes the issue for me:

Okay yeah, it looks like the problem is being caused by the priority penalty applied to distance. Currently it's 10% per tile, which may be too high. Setting it to 0 in the priorities.txt file more-or-less fixes it.

Dalas120 If crew end up bringing too much ammo is the extra lost?

I think so? I don't know what else should happen with it. Maybe they should wait at the weapon for a bit to see if it uses any ammo before giving up and going someplace else.

Dalas120 it would also help if crew would realize "I was going to that launcher but this one also needs crew and is a lot closer."

I'll look into this, may or may not be easy to do.

Dalas120 It might also help if missiles loaded one tube at a time, instead of randomly split between tubes. That way crew demand would vary much less, at least for missiles types that fit multiple projectiles in the barrel (mines(?) and HE).

I think I can do this fairly easily by making the priority of each missile tube increase as it fills up instead of decrease.

Dalas120 Though, another option might be to leave crew kind of dumb (especially if making them smart costs a lot of performance/dev time) and expect players to hand-craft their AI with the upcoming configurable crew behavior. That would make mastering crew behavior more rewarding for the player (after all, what's the point of customizing crew behavior if crew are smart anyway), and would keep lots of emphasis on internal design and crew (which I think is one of cosmoteer's most unique parts).

I think this is the long-term correct answer, though exactly how much control players should have, I'm not sure yet.

Dalas120 Wouldn't this also happen with scaling priorities though? If both parts are empty then they'd both have the same priority?

Priority is calculated based on the amount of anticipated ammo, not the amount of ammo actually stored. So the moment a crew gets assigned to deliver ammo to a weapon, that weapon's priority will decrease a bit for the purposes of assigning additional crew to it.

Dalas120 If multiple parts are completely empty then I don't think it's important for crew to split evenly - all that matters is that they get something up and running.

I'm not sure I agree with this. (Though I'm not sure I disagree either.) I'm a little concern that a player will see all their crew run to fill up one weapon and ignore the other, which could be confusing.

Dalas120 As soon as one part starts to fill up then it can no longer demand as many crew, and some crew will be freed up for other parts even with even priorities.

But what if it never gets filled up? What if you have two weapons, one with 5 crew assigned and one with 0, and the weapon with 5 crew is firing and using enough ammo that it never fills up. The other weapon never gets to shoot. This might be fine or even preferable from a ship optimization standpoint, but I think it's unintuitive.

Dalas120

Walt I think so? I don't know what else should happen with it. Maybe they should wait at the weapon for a bit to see if it uses any ammo before giving up and going someplace else.

I'm not sure. Under a situation where ammo is heavily constrained but there's lots of free crew (e.g. mine launcher just swapped to HE), it would probably make sense to put the ammo back in storage somewhere. Under other situations it would make sense to abandon the ammo and take another job (e.g. HE just swapped to mines). And under other situations it would make sense to wait (continually firing cannon, shield that's being shot at).

Probably the best solution is just to have them abandon the ammo and do something else. That's consistent and easy for the player to understand.

Now that I think about it, maybe it's actually not a good idea to let weapons anticipate demand. While it would definitely lead to better crew AI, it would probably be confusing for players to predict. And I think one of the most important things in a building/simulation game like this is for players to fully understand all the mechanics (especially once players get to alter crew behavior). Right now it's pretty simple - a weapon can demand as many crew as it has empty ammo slots for.

Then again, I have no idea what's planned for configurable crew behavior (other than what it says on the trello) so maybe this wouldn't be an issue at all.

Walt I think this is the long-term correct answer, though exactly how much control players should have, I'm not sure yet.

Personally, I think it might make sense to integrate this with boarding. If there was some kind of system/UI that could work for supplying parts, defending boarders, and boarding enemy ships that would make things a lot simpler for players to learn, and probably simpler to develop too.

Walt The other weapon never gets to shoot. This might be fine or even preferable from a ship optimization standpoint, but I think it's unintuitive.

Yeah, that makes sense.

Dalas120

Walt A quick question about missile parts: Based on the graphics you currently have, how many missile parts of each type can each factory, storage, and launcher hold? And how many parts does it take to make a missile?

Dalas120

Dalas120 Now that I think about it, maybe it's actually not a good idea to let weapons anticipate demand.

Dalas120 Then again, I have no idea what's planned for configurable crew behavior (other than what it says on the trello) so maybe this wouldn't be an issue at all.

Now that I think about it again - this probably isn't the time to be worrying too much about future features. If crew AI changes aren't too hard to make and will benefit 0.14.5, then I'm all for it.

Walt

Dalas120 While it would definitely lead to better crew AI, it would probably be confusing for players to predict. And I think one of the most important things in a building/simulation game like this is for players to fully understand all the mechanics (especially once players get to alter crew behavior). Right now it's pretty simple - a weapon can demand as many crew as it has empty ammo slots for.

Maybe the amount that a weapon can anticipate could be configurable by the player, but defaults to zero so that it's intuitive for new players.

Dalas120 Personally, I think it might make sense to integrate this with boarding. If there was some kind of system/UI that could work for supplying parts, defending boarders, and boarding enemy ships that would make things a lot simpler for players to learn, and probably simpler to develop too.

My current thinking is that clicking the "Crew" button will enter into a separate mode (a la build & paint) where you can left-click to select crew and right-click to assign them to a specific room. Assigning a regular crew to a room means man/supply that room. Once boarding is added, assigning combat soldiers (probably a different type of crew, or at least specially-equipped crew) to a room means defend it (if on a friendly ship) or attack it (if on an enemy ship).

Dalas120 A quick question about missile parts: Based on the graphics you currently have, how many missile parts of each type can each factory, storage, and launcher hold? And how many parts does it take to make a missile?

Launchers, factories, and storages are all the same:

HE: 12 parts (3 missiles)
EMP: 9 parts (1 missile)
Nuke: 12 parts (1 missile)
Mines: TBD, probably 4-6 mines (1 part per mine)

Dalas120

Walt HE: 12 parts (3 missiles)
EMP: 9 parts (1 missile)
Nuke: 12 parts (1 missile)
Mines: TBD, probably 4-6 mines (1 part per mine)

Thanks! Do you mind if I work on some possible damage/production/cost numbers for balance?

Also, do launchers, factories, and storages need to be the same, or is that just the way it is now? Maybe an EMP storage could have 18 parts, for example.

Walt

Dalas120 Do you mind if I work on some possible damage/production/cost numbers for balance?

Be my guest!

Dalas120 Also, do launchers, factories, and storages need to be the same, or is that just the way it is now? Maybe an EMP storage could have 18 parts, for example.

There's no technical reason they need to be the same, but since stored missile parts are shown graphically as the entire constructed missile, I'm not sure how I would fit 2 EMP missiles in a single storage room. In theory I could change the graphics for stored missile parts, though that'd be a bunch of work and might make it a bit less clear.

Dalas120

Walt Prototype 5 crash:

Log: https://www.mediafire.com/file/r4q4iz2gx4pxkiq/log_2019-01-13_22_59_23.txt/file

Save Game: https://www.mediafire.com/file/05zdiore7sr1d05/crash.savedgame/file
Cancel target on the missile launcher to get it to crash.

This is a pretty old crash so it might already be fixed.

Walt

Dalas120 Yup already fixed, thanks!

fion9x3owns

For WALT, i aprreciate your work but...

System.AggregateException: Произошла одна или несколько ошибок. ---> System.InvalidOperationException: Нулевой объект должен иметь значение.

в System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)

в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AcquireTarget() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 367

в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AdjustAim(Time dt) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 211

в Cosmoteer.Ships.Parts.Weapons.WeaponManager.MicroUpdate(FixedUpdater microUpdater, SimRoot sim) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\WeaponManager.cs:строка 330

в Cosmoteer.Ships.MicroUpdateableShipComponent.Cosmoteer.Simulation.IMicroUpdateableSimObject.MicroUpdate(FixedUpdater microUpdater, SimRoot sim) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\MicroUpdateableShipComponent.cs:строка 159

в Cosmoteer.Simulation.SimRoot.<>cDisplayClass178_0.<ParallelMicroUpdate>b0(Int32 i) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1242

в System.Threading.Tasks.Parallel.<>cDisplayClass17_0`1.<ForWorker>b1()

в System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)

в System.Threading.Tasks.Task.<>cDisplayClass176_0.<ExecuteSelfReplicating>b0(Object )

--- Конец трассировки внутреннего стека исключений ---

в System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)

в System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)

в System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action1 body, Action2 bodyWithState, Func4 bodyWithLocal, Func1 localInit, Action`1 localFinally)

в System.Threading.Tasks.Parallel.For(Int32 fromInclusive, Int32 toExclusive, Action`1 body)

в Cosmoteer.Simulation.SimRoot.ParallelMicroUpdate(IMicroUpdateableSimObject[] array, Int32 startIndex, Int32 count) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1235

в Cosmoteer.Simulation.SimRoot.MicroUpdate() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1089

в Halfling.Timing.FixedUpdater.Update(Time deltaTime, Action action) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Timing\FixedUpdater.cs:строка 111

в Halfling.Scene.Dim2.SceneRoot.Update() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Scene\Dim2\SceneRoot.cs:строка 701

в Cosmoteer.Simulation.SimRoot.Update() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 592

в Cosmoteer.Game.GameRoot.Update(StateMethodInvoker updateParent) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Game\GameRoot.cs:строка 1196

в Halfling.Application.AppStateEx.Halfling.Application.IAppState.Update(StateMethodInvoker updateParent) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\AppStateEx.cs:строка 211

в Halfling.Application.Director.CallUpdate() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:строка 920

в Halfling.Application.Director.DoUpdate() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:строка 804

в Halfling.Application.Director.<GetRunIterator>d__83.MoveNext() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:строка 335

в Halfling.Application.Bases.GenericApp.<ApplicationMainIterator>d__48.MoveNext() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Bases\GenericApp.cs:строка 279

в Halfling.Windows.D3D11.D3D11Window.RunGameLoop(String[] args, IEnumerable`1 iterator) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingPlatformWDX\Windows\D3D11\D3D11Window.cs:строка 890

в Halfling.Application.Bases.GenericApp.ApplicationMain(String[] args) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Bases\GenericApp.cs:строка 195

в Cosmoteer.GameApp.Main(String[] args) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\GameApp.cs:строка 145

---> (Внутреннее исключение #0) System.InvalidOperationException: Нулевой объект должен иметь значение.

в System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)

в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AcquireTarget() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 367

в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AdjustAim(Time dt) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 211

в Cosmoteer.Simulation.SimRoot.<>cDisplayClass178_0.<ParallelMicroUpdate>b0(Int32 i) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1242

в System.Threading.Tasks.Parallel.<>cDisplayClass17_0`1.<ForWorker>b1()

в System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)

в System.Threading.Tasks.Task.<>cDisplayClass176_0.<ExecuteSelfReplicating>b0(Object )<---

01/15/2019 03:36:36 | Logging successful initialized.

01/15/2019 03:36:36 | .NET Runtime Version: 4.0.30319.42000

01/15/2019 03:36:36 | Running as a 64-bit process.

01/15/2019 03:36:36 | Local: ru-RU

01/15/2019 03:36:36 | Language: ru-RU

01/15/2019 03:36:36 | Cosmoteer version missile_prototype5

01/15/2019 03:36:36 | Майкрософт Windows 10 Домашняя для одного языка 64-разрядная 10.0.17134

01/15/2019 03:36:36 | Intel(R) Core(TM) i5-7300HQ CPU @ 2.50GHz (4 logical processors)

01/15/2019 03:36:36 | 12169,3 MB RAM

01/15/2019 03:36:36 | NVIDIA GeForce GTX 1050 (25.21.14.1616) (02.10.2018)

01/15/2019 03:36:36 | 4095,0 MB VRAM

01/15/2019 03:36:36 |

01/15/2019 03:36:37 | Loaded app settings.

01/15/2019 03:36:37 | Mixpanel Distinct ID: 48137160CA641309C04CCCBA7339E8B7

01/15/2019 03:36:37 | Process is now DPI-aware.

01/15/2019 03:36:37 | Setup default cursor.

01/15/2019 03:36:37 | Using display adapter 0

01/15/2019 03:36:37 | Created DXGI factory.

01/15/2019 03:36:37 | Adapter #0: NVIDIA GeForce GTX 1050

01/15/2019 03:36:37 | Output #0: Generic PnP Monitor (1920x1080)

01/15/2019 03:36:37 | Adapter #1: Intel(R) HD Graphics 630

01/15/2019 03:36:37 | Adapter #2: Microsoft Basic Render Driver

01/15/2019 03:36:37 | Updated Windows form configuration for resizable windowed.

01/15/2019 03:36:37 | Created Windows form.

01/15/2019 03:36:37 | Direct3D Feature Level: Level_11_0

01/15/2019 03:36:37 | Created Direct3D 11 Device.

01/15/2019 03:36:37 | Created swap chain: 1022x1033.

01/15/2019 03:36:37 | Created window.

01/15/2019 03:36:37 | Created clock.

01/15/2019 03:36:37 | Created graphics manager.

01/15/2019 03:36:37 | Created XAudio2 device.

01/15/2019 03:36:37 | Created audio manager.

01/15/2019 03:36:37 | Created input manager.

01/15/2019 03:36:37 | Created default font.

01/15/2019 03:36:37 | Initial app state is 'MainMenu'

01/15/2019 03:36:37 | Initial application settings:

01/15/2019 03:36:37 | LastGameVersion:

01/15/2019 03:36:37 | InitState: MainMenu

01/15/2019 03:36:37 | Language:

01/15/2019 03:36:37 | LockCursor: True

01/15/2019 03:36:37 | EdgePanMode: Analog

01/15/2019 03:36:37 | EdgePanSpeed: 15

01/15/2019 03:36:37 | KeyboardPanSpeed: 15

01/15/2019 03:36:37 | KeyboardZoomSpeed: 10

01/15/2019 03:36:37 | KeyboardRotSpeed: 90°

01/15/2019 03:36:37 | EnableMouseWheelZoom: True

01/15/2019 03:36:37 | InvertMouseWheelZoom: False

01/15/2019 03:36:37 | MouseWheelZoomSpeed: 1,12

01/15/2019 03:36:37 | MouseWheelZoomAtCursor: True

01/15/2019 03:36:37 | StickyFocus: True

01/15/2019 03:36:37 | DpiScaleMode: Dpi100

01/15/2019 03:36:37 | AnimateBackgrounds: True

01/15/2019 03:36:37 | FancyParticles: True

01/15/2019 03:36:37 | UncompressedTextures: False

01/15/2019 03:36:37 | AllowShipDeselection: False

01/15/2019 03:36:37 | CtrlSelectsParts: True

01/15/2019 03:36:37 | EnableCollisionAvoidance: True

01/15/2019 03:36:37 | PreferBlueprintMode: False

01/15/2019 03:36:37 | BlueprintAutoPause: True

01/15/2019 03:36:37 | ShowInvalidBlueprints: True

01/15/2019 03:36:37 | BuildAutoFocus: True

01/15/2019 03:36:37 | BuildAutoRotate: True

01/15/2019 03:36:37 | BuildAutoInteriors: True

01/15/2019 03:36:37 | PaintAutoFocus: True

01/15/2019 03:36:37 | PaintAutoRotate: True

01/15/2019 03:36:37 | PaintAllowOverwrite: True

01/15/2019 03:36:37 | PaintMirrorEnabled: False

01/15/2019 03:36:37 | PaintMirrorAxis: Vertical

01/15/2019 03:36:37 | RepairAutoFocus: True

01/15/2019 03:36:37 | RepairAutoRotate: False

01/15/2019 03:36:37 | BuildAllowOverwrite: True

01/15/2019 03:36:37 | BuildAutoDoors: True

01/15/2019 03:36:37 | BuildEnforceCrewAccess: True

01/15/2019 03:36:37 | BuildMirrorEnabled: False

01/15/2019 03:36:37 | BuildMirrorAxis: Vertical

01/15/2019 03:36:37 | RowsOfParts: 1

01/15/2019 03:36:37 | GrabLeavesCorridors: True

01/15/2019 03:36:37 | RepairAutoDoors: True

01/15/2019 03:36:37 | AutoHireCrew: True

01/15/2019 03:36:37 | PartToolTips: True

01/15/2019 03:36:37 | AutoSave: True

01/15/2019 03:36:37 | AutoSavesToKeep: 10

01/15/2019 03:36:37 | QuickSavesToKeep: 10

01/15/2019 03:36:37 | AutoSaveInterval: 600

01/15/2019 03:36:37 | SaveLostShips: True

01/15/2019 03:36:37 | LostShipsTokeep: 10

01/15/2019 03:36:37 | FtlAutoSave: True

01/15/2019 03:36:37 | ShowOnShipIndicators: True

01/15/2019 03:36:37 | ShowZoomedOutBlibs: True

01/15/2019 03:36:37 | ShowOffScreenBlips: True

01/15/2019 03:36:37 | PingNearbyEnemies: True

01/15/2019 03:36:37 | AutoPauseOnLostFocus: True

01/15/2019 03:36:37 | ScreenShake: True

01/15/2019 03:36:37 | ShowMidpointFocusWidget: True

01/15/2019 03:36:37 | VersionCheckMode: Stable

01/15/2019 03:36:37 | EnableMetrics: True

01/15/2019 03:36:37 | PreferBorderlessWindowToggle: False

01/15/2019 03:36:37 | MasterVolume: 1

01/15/2019 03:36:37 | EffectsVolume: 1

01/15/2019 03:36:37 | InterfaceVolume: 1

01/15/2019 03:36:37 | ShowTutorials: True

01/15/2019 03:36:37 | AutoFtlJump: False

01/15/2019 03:36:37 | PaintSchemes: System.Collections.Generic.List`1[Cosmoteer.Ships.PaintScheme]

01/15/2019 03:36:37 | DefaultBuildTool: Grab

01/15/2019 03:36:37 | DefaultDecalTool: Grab

01/15/2019 03:36:37 | TutorialPageStates: System.Collections.Generic.Dictionary`2[System.String,Cosmoteer.Tutorials.TutorialPageState]

01/15/2019 03:36:37 | PlayerColor:

01/15/2019 03:36:37 | EnemyColor:

01/15/2019 03:36:37 | NeutralColor:

01/15/2019 03:36:37 | MiniviewInCombatMode: Auto

01/15/2019 03:36:37 | MiniviewNotInCombatMode: Auto

01/15/2019 03:36:37 | MiniviewLockRotation: False

01/15/2019 03:36:37 | MiniviewSize:

01/15/2019 03:36:37 | ShowInteriors: False

01/15/2019 03:36:37 | AlwaysShowCommandWidgets: False

01/15/2019 03:36:37 | PreferShipRelativeAttackAngle: False

01/15/2019 03:36:37 | PreferWorldRelativeFollowAngle: False

01/15/2019 03:36:37 | ShipLibraryLargeIcons: False

01/15/2019 03:36:37 | AdHocFormations: False

01/15/2019 03:36:37 | BreakFormationToAttack: True

01/15/2019 03:36:37 | DisplayAllShips: False

01/15/2019 03:36:37 | ShowAdvancedCommands: False

01/15/2019 03:36:37 | EnabledMods: System.Collections.Generic.HashSet`1[System.String]

01/15/2019 03:36:37 | DeleteFileOnStartup:

01/15/2019 03:36:37 | DefaultGameMode:

01/15/2019 03:36:37 | DefaultCreativeModeMapSize: 0

01/15/2019 03:36:37 | DefaultBountyModeDifficulty: 0

01/15/2019 03:36:37 | DefaultBountyModeMapSize: 0

01/15/2019 03:36:37 | DefaultBountyModeStarterShip: 0

01/15/2019 03:36:37 | MPShipColorMode: RandomPerPlayer

01/15/2019 03:36:37 | MPBlipColorMode: FriendAndFoe

01/15/2019 03:36:37 | MPShowDamagePoints: True

01/15/2019 03:36:37 | CustomRulesets: System.Collections.Generic.Dictionary2[System.String,System.Collections.Generic.List1[Cosmoteer.CustomRuleset]]

01/15/2019 03:36:37 | AutoPortForwarding: True

01/15/2019 03:36:37 | DisplayPublicIP: True

01/15/2019 03:36:37 | PreferLAN: False

01/15/2019 03:36:37 | DefaultServer: 0

01/15/2019 03:36:37 | ShowNewsOnStartup: True

01/15/2019 03:36:37 | ReadNewsArticles: System.Collections.Generic.HashSet`1[System.String]

01/15/2019 03:36:37 | ShowNewsAlerts: True

01/15/2019 03:36:37 | HiddenNewsAlerts: System.Collections.Generic.HashSet`1[System.String]

01/15/2019 03:36:37 | Starting main game loop...

01/15/2019 03:36:37 | Enabled mods:

01/15/2019 03:36:41 | Loaded language 'en'.

01/15/2019 03:36:46 | Resized swap chain: 1022x1041

01/15/2019 03:36:46 | Loaded game rules.

01/15/2019 03:36:57 | Game pushed onto stack.

01/15/2019 03:36:57 | Game mode is: CreativeGameModeManager

01/15/2019 03:38:17 | Memory usage at time of crash: 1 191 006 208

01/15/2019 03:38:17 | Application state stack at time of crash:

01/15/2019 03:38:17 | Cosmoteer.Game.GameRoot

01/15/2019 03:38:17 | Cosmoteer.Gui.TitleScreen

01/15/2019 03:38:17 | FPS at time of crash: 49,65305

01/15/2019 03:38:17 | Running processes at time of crash: aswidsagent, audiodg, AvastSvc, AvastUI, chrome, conhost, Cosmoteer, csrss, ctfmon, DiscSoftBusServiceLite, DTShellHlp, dwm, explorer, fontdrvhost, GameBar, ibtsiva, ICEsoundService64, Idle, igfxCUIService, igfxEM, IntelCpHDCPSvc, IntelCpHeciSvc, LockApp, lsass, mbbService, Memory Compression, Microsoft.Photos, MSASCuiL, nvcontainer, NVDisplay.Container, NVIDIA Share, NVIDIA Web Helper, nvsphelper64, NvTelemetryContainer, PresentationFontCache, RAVBg64, Registry, RtkNGUI64, RuntimeBroker, SearchIndexer, SearchProtocolHost, SearchUI, SecurityHealthService, sedsvc, services, SettingSyncHost, SgrmBroker, ShellExperienceHost, sihost, SkypeApp, SkypeBackgroundHost, SkypeBridge, smartscreen, smss, spoolsv, svchost, System, taskhostw, TuneupSvc, TuneupUI, unsecapp, uTorrent, utorrentie, wininit, winlogon, WmiPrvSE, WUDFHost,

01/15/2019 03:38:17 | System.AggregateException: Произошла одна или несколько ошибок. ---> System.InvalidOperationException: Нулевой объект должен иметь значение.

01/15/2019 03:38:17 | в System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)

01/15/2019 03:38:17 | в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AcquireTarget() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 367

01/15/2019 03:38:17 | в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AdjustAim(Time dt) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 211

01/15/2019 03:38:17 | в Cosmoteer.Ships.Parts.Weapons.WeaponManager.MicroUpdate(FixedUpdater microUpdater, SimRoot sim) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\WeaponManager.cs:строка 330

01/15/2019 03:38:17 | в Cosmoteer.Ships.MicroUpdateableShipComponent.Cosmoteer.Simulation.IMicroUpdateableSimObject.MicroUpdate(FixedUpdater microUpdater, SimRoot sim) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\MicroUpdateableShipComponent.cs:строка 159

01/15/2019 03:38:17 | в Cosmoteer.Simulation.SimRoot.<>cDisplayClass178_0.<ParallelMicroUpdate>b0(Int32 i) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1242

01/15/2019 03:38:17 | в System.Threading.Tasks.Parallel.<>cDisplayClass17_0`1.<ForWorker>b1()

01/15/2019 03:38:17 | в System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)

01/15/2019 03:38:17 | в System.Threading.Tasks.Task.<>cDisplayClass176_0.<ExecuteSelfReplicating>b0(Object )

01/15/2019 03:38:17 | --- Конец трассировки внутреннего стека исключений ---

01/15/2019 03:38:17 | в System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions)

01/15/2019 03:38:17 | в System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken)

01/15/2019 03:38:17 | в System.Threading.Tasks.Parallel.ForWorker[TLocal](Int32 fromInclusive, Int32 toExclusive, ParallelOptions parallelOptions, Action1 body, Action2 bodyWithState, Func4 bodyWithLocal, Func1 localInit, Action`1 localFinally)

01/15/2019 03:38:17 | в System.Threading.Tasks.Parallel.For(Int32 fromInclusive, Int32 toExclusive, Action`1 body)

01/15/2019 03:38:17 | в Cosmoteer.Simulation.SimRoot.ParallelMicroUpdate(IMicroUpdateableSimObject[] array, Int32 startIndex, Int32 count) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1235

01/15/2019 03:38:17 | в Cosmoteer.Simulation.SimRoot.MicroUpdate() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1089

01/15/2019 03:38:17 | в Halfling.Timing.FixedUpdater.Update(Time deltaTime, Action action) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Timing\FixedUpdater.cs:строка 111

01/15/2019 03:38:17 | в Halfling.Scene.Dim2.SceneRoot.Update() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Scene\Dim2\SceneRoot.cs:строка 701

01/15/2019 03:38:17 | в Cosmoteer.Simulation.SimRoot.Update() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 592

01/15/2019 03:38:17 | в Cosmoteer.Game.GameRoot.Update(StateMethodInvoker updateParent) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Game\GameRoot.cs:строка 1196

01/15/2019 03:38:17 | в Halfling.Application.AppStateEx.Halfling.Application.IAppState.Update(StateMethodInvoker updateParent) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\AppStateEx.cs:строка 211

01/15/2019 03:38:17 | в Halfling.Application.Director.CallUpdate() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:строка 920

01/15/2019 03:38:17 | в Halfling.Application.Director.DoUpdate() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:строка 804

01/15/2019 03:38:17 | в Halfling.Application.Director.<GetRunIterator>d__83.MoveNext() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Director.cs:строка 335

01/15/2019 03:38:17 | в Halfling.Application.Bases.GenericApp.<ApplicationMainIterator>d__48.MoveNext() в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Bases\GenericApp.cs:строка 279

01/15/2019 03:38:17 | в Halfling.Windows.D3D11.D3D11Window.RunGameLoop(String[] args, IEnumerable`1 iterator) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingPlatformWDX\Windows\D3D11\D3D11Window.cs:строка 890

01/15/2019 03:38:17 | в Halfling.Application.Bases.GenericApp.ApplicationMain(String[] args) в C:\Users\Walt\Documents\Code\Cosmoteer\Halfling\HalflingCore\Application\Bases\GenericApp.cs:строка 195

01/15/2019 03:38:17 | в Cosmoteer.GameApp.Main(String[] args) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\GameApp.cs:строка 145

01/15/2019 03:38:17 | ---> (Внутреннее исключение #0) System.InvalidOperationException: Нулевой объект должен иметь значение.

01/15/2019 03:38:17 | в System.ThrowHelper.ThrowInvalidOperationException(ExceptionResource resource)

01/15/2019 03:38:17 | в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AcquireTarget() в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 367

01/15/2019 03:38:17 | в Cosmoteer.Ships.Parts.Weapons.TurretWeapon.AdjustAim(Time dt) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Ships\Parts\Weapons\TurretWeapon.cs:строка 211

01/15/2019 03:38:17 | в Cosmoteer.Simulation.SimRoot.<>cDisplayClass178_0.<ParallelMicroUpdate>b0(Int32 i) в C:\Users\Walt\Documents\Code\Cosmoteer\Source\Simulation\SimRoot.cs:строка 1242

01/15/2019 03:38:17 | в System.Threading.Tasks.Parallel.<>cDisplayClass17_0`1.<ForWorker>b1()

01/15/2019 03:38:17 | в System.Threading.Tasks.Task.InnerInvokeWithArg(Task childTask)

01/15/2019 03:38:17 | в System.Threading.Tasks.Task.<>cDisplayClass176_0.<ExecuteSelfReplicating>b0(Object )<---

01/15/2019 03:38:17 |

01/15/2019 03:38:17 | Actual data hash: de19dd784dea5f892fd254cbd82c5e55

01/15/2019 03:38:17 | Expected data hash: de19dd784dea5f892fd254cbd82c5e55

01/15/2019 03:38:20 | Error successfully reported. Thank you!

01/15/2019 03:38:20 | Director received exit call.

01/15/2019 03:38:20 | Disposed default font.

01/15/2019 03:38:20 | Disposed XA2AudioManager device.

01/15/2019 03:38:20 | Disposed audio manager.

01/15/2019 03:38:20 | Disposed clock.

01/15/2019 03:38:20 | Disposed input manager.

01/15/2019 03:38:20 | Disposed graphics manager.

01/15/2019 03:38:20 | Disposed swap chain.

01/15/2019 03:38:20 | Disposed Direct3D device.

01/15/2019 03:38:20 | Disposed DXGI factory.

01/15/2019 03:38:20 | Closed Windows form.

01/15/2019 03:38:20 | Director received exit call.

01/15/2019 03:38:20 | Disposed window.

01/15/2019 03:38:20 | Disposed platform interface.

01/15/2019 03:38:20 | Closing log output file...

SHIT HAPPENS