Résultats de la recherche

Can someone extract the sound of Azaries purring/trilling (as happens a few times in the prologue, like when using flame breath) so I can set it as my notification sound? It is adorable.

Haha

Bolec a écrit :

hey is it possible to turn off auto aim when we play with controller ?

I will add this option in next update

I think you'll like Arknights: Endfield

Rimbecano a écrit :

There is no "terrain improvements" category in the help interface

Mildly agree. I wouldn't mind adding this.

Eventually, you just memorize all improvements on common terrains.
Rare stuff ice or seas, like Penguins or Corals, you can look up case-by-case.

Rimbecano a écrit :

No build times for improvements seem to be listed anywhere ...
It is not clear if build times are terrain dependent.

Yes, they are terrain-dependent.

• All improvements cost 5 worker-turns on most 1-MP terrain: plains, tundra, etc.
  
• IIRC, 5 turns in Forest
  
• 8 turns on Hills, maybe also Swamps
  
• 12 turns on Mountains, Desert

The harder the terrain, the longer they take.

Rimbecano a écrit :

"Roads/highways improve movement speed" ... is entirely unclear.

Agreed. But the bigger issue is no new updates since Apr 12.
We had 12 updates in 3 months, and then 0 in 3.3 months (to mid-August).

Anyways:

• Roads give -1 MP cost, to a minimum of 1.0 MP cost, and +5% Gold to cities.
  So a Mountain that costs 3.0 MP will cost 2.0 MP.
  But a Plains that costs 1.0 still costs 1.0.
  
• Highways give -2 MP cost, to a minimum of 0.5 MP cost, and +10% Gold to cities.
  So a Plains that costs 1.0 now costs 0.5, which speeds up all units by 2.0x.
  Yes, this means Catapult zooms down Highways at 4 hexes per turn.
  Griffin Riders fly over Highways at 6 hexes per turn. (Yes, flight benefits from roads)
  
• Road build cost also depends on both terrain in the 2 adjacent hexes.
  
  • 3 turns for easy 1-MP terrain (Plains, etc.)
    
  • 5 or 6 turns for a Plains-Forest road leg (in either direction)
    
  • 8 turns for a Hills-Hills road
    
  • 12 turns for a Snow-Snow road
    

That won't fit into a tooltip.
I agree that it should be in the Help somewhere.

But there are more urgent things to fix first, e.g. most of naval combat.
I'd rather dev return and do those first.

ken said" don't like auto mechanics, but since cars are now so computerized that working on your care is almost impossible, I have to use auto mechanics."

Jim recommends the Xtool to solve all automotive issues.
It makes working on a car simplistic.

It's got three big problems: turn rate, reload and overheating. Those three make it next to useless because it's not firing too much of the time

I have the same issue here I had 500+ fps in game and now it had reached maximum 200
I6-12700 , 3070ti

jesus christ when are you guys releasing the peterbilt tuning?!?!?!

paulbierley a écrit :

john.glossop a écrit :

Mods will continue to crash the game until CO release the asset editor.

What makes you think that ?. I see no reason why a release of the asset editor would prevent mods from crashing the game. I also see no reason why not releasing it would be the cause of any crashes.

Sorry, I was being lazy. What is really needed is an API, or Application Programming Interface, which is a piece of software that sits BETWEEN the application and the game and acts as a "gatekeeper" to prevent 3rd party (in our case) mods, from trying to pass invalid data to the app (game) and causing undesirable outcomes (CRASH!!!). I assumed (wrongly, perhaps) that a full blown Asset Editor would include an API to protect the core logic and data, but of course, the way that CO/PDX handles such things tends to be as simply, and cheaply, as possible, hence the crashes.
Games such as MSFS (all iterations since modding started) have used an API as the interface between the game, and third party developers, which is the reason why MSFS has thousands of addons (mods) developed by many different 3rd party developers from big, multi-national conglomerates, down to back yard dev teams run by rank amateurs who didn't have much knowledge of the interface they were working with. I was part of one or the teams that developed airline schedules and plane models for MSFS, from '98 to X, and we never caused a crash of the game, because the SDK was backed up by an effective API that prevented us from doing so. The only thing that would happen if we tried to pass something invalid to th sim was that the API would reject it, and we wouldn't get the results that we expected. No crashes, no drama.