rome2.dll

Company
The Creative Assembly Ltd
Description

Total War Rome II

Version
2.2.0.0
Architecture
32 bit
Threat Score
0 %
Original size
26697.5 Kb
Download size
13595.9 Kb
MD5
a71c4fde82e92954f8f97595194b0089
SHA1
3d3e03fd6773e260aa00b213a8d21b392caf23b7
SHA256
ac6208fb800890a5cebb2944433d9ed9f768b06851119b3f3624bddcc5acec5d
entry_point


	 start date: %s

      (LINE %d) error near character %d %S

   Start date: %s

   Unable to load public key

'(error with no message)

(%S)(%S) is too close to the sea bed and will ground at the start of the battle

A nonrecoverable error occurred.

Alliance %d: Alliance Start Size = %d,

 End Alliance Size = %d

An error has occurred

An unknown d3d9 error occurred!

At start of open_handler

BEnable unlimited video memory allocation

Battle AI Debug Display/Enable for Selected Unit Only

Buffer error in compressed datastream in %s chunk

CData error in compressed datastream in %s chunk

Comments must start with /

Define Restart Interval %u

Determines how much have to scroll to enable tacmap

Did a war start between this faction and another faction this turn?

Distance that waypoint start has to move before snapping rather than smoothely moving to

Enable Blood effects

Enable Direct Resource Access

Enable Distortion Effect buffer

Enable Halloween visuals

Enable Screen Space Ambient Occlusion buffer

Enable Steam Update Thread

Enable all shrouds (or one faction,

 if specified)

Enable async cache~loading of textures

Enable async load of textures

Enable async update of textures

Enable battle camera shake effects

Enable delay load of textures

Enable grass

Enable head tracking

Enable lua profiling

Enable on-screen keyboard for touch

Enable tesselation

Enable texture manager cache

Enable thread affinity

Enable touch controls

Enable trees

Enable verbose texture manager reporting

Enable vignette

Enable/disable debug display of start and endpoint of movement extent spline segments

Enable/disable debug display of start and endpoint of zoc spline segments

Engine crew pulling on rope and making it taut between start and end times

Error Retrieving Profile

Error Trigger

Error accept()ing server connect

Error in error handling

Error in the SSH layer

Error in user chunk

Error loading CRL file: %s

Error loading module %s from file %s:

Error loading module '%s' from file '%s':

Error reading absolute_timings

Error reading blur_size

Error reading end_fade_to_black

Error reading facing

Error reading focal_distance

Error reading focal_length

Error reading fov

Error reading position_offset

Error reading shot_type

Error reading sleep_time

Error reading start_fade_to_black

Error reading subject_type

Error reading target_offset

Error reading transition_method

Error reading transition_time

Error setting certificate verify locations,

 continuing anyway:

Error setting certificate verify locations:

Error signaled by ssl ctx callback

Error while connecting to chat with the Twitch SDK: %s

Error while initialising chat with the Twitch SDK: %s

Error while initializing the Twitch SDK: %s

Error while processing content unencoding: %s

Error while processing content unencoding: Unknown failure within decompression software.

Error while reading a bank

Error while reading the manifest file (line: %d)

Error while requesting authorisation with the Twitch SDK: %s

Error while setting calculating max resolution: %s

Error while setting stream info: %s

Error while setting up logs for Twitch SDK: %s

Error while shutting down the Twitch SDK: %s

Error while starting to stream: %s

Error while stopping to stream: %s

Error while submitting frame to stream: %s

Error while waiting for server connect

Expecting start state

Fired for every character at the start of their turn

Fired once at the start of conflict

Fired once at the start of deployment

Fired when the an agent is unable to be created through script

Got an error writing an RTP packet

HTTP error before end of send,

 stop sending

Internal error clearing splay node = %d

Internal error removing splay node = %d

Ioctl callback returned error %d

Is the context faction besieging the specified settlement? Intended for use with faction start of turn event.

Is the port blockaded by the local faction,

 and did it start in the last round?

Is the port blockaded,

 and did it start in the last round?

Loop or previous error loading module '%s'

Lua error: Unable to execute error handler

Neither enable or disable specified

NrVKxBoth enable and disable specified

Output file write error --- out of disk space?

P=error reading battle_type

Position where impact originates

 start time is the time of impact

Position where projectile is created

 start time is the time of projectile spawn

Range to enemy to start checking for refusals

SOCKS5 read error occurred

SOCKS5: error occurred during connection

SSL: Unable to open issuer cert (%s)

SSL: Unable to read issuer cert (%s)

SSL: unable to obtain common name from peer certificate

SSL_write() return error %d

Seek callback returned error %d

Set the specified population class in the specified region to be ina  rebellion state at the start of the next turn

Start Logging

Start Of Frame 0x%02x: width=%u,

 height=%u,

 components=%d

Start Of Scan: %d components

Start Timer: %d

Start Week,

 Start Year,

 End Week,

 End Year (Inclusive)

Start Year,

 End Year (Inclusive)

Start allowed in the Running and Done states

Start date

Start distance

Start of BATTLE_ENV constructor

Start of Image

Start state required

Stuff in vertices before trying to start it

Syntax error in telnet option: %s

System error %d

Test to see if the current calendar year and week in year is within the years and weeks specified.  Week should be 0 <

= week <

 48.  start <

= current <

= end

Test to see if the current calendar year is within the years specified.  start <

= current <

= end

The requested address is a broadcast address,

 but the appropriate flag was not set. Call setsockopt with the SO_BROADCAST socket option to enable use of the broadcast address.

The socket's local address is already in use and the socket was not marked to allow address reuse with SO_REUSEADDR. This error usually occurs during execution of the bind function,

 but could be delayed until this function if the bind was to a partially wildcard address (involving ADDR_ANY) and if a specific address needs to be committed at the time of this function.

The start of round for this slot

The start of turn for this slot

The time to forward predict being hit

 to start skirmishing

The virtual circuit was reset by the remote side executing a hard or abortive close. For UPD sockets,

 the remote host was unable to deliver a previously sent UDP datagram and responded with a 'Port Unreachable' ICMP packet. The application should close the socket as it is no longer usable.

The virtual circuit was reset by the remote side executing a hard or abortive close. The application should close the socket as it is no longer usable. On a UPD-datagram socket this error would indicate that a previous send operation resulted in an ICMP 'Port Unreachable' message.

Triggers dismembering at the start time

Twitch error log set to use: %S

Unable to create an SSL structure

Unable to disable tech - no tech record found for '%s'

Unable to dump given function

Unable to enable tech - no tech record found for '%s'

Unable to find Construction System Behaviour for '%s'

Unable to generate a unique filename

Unable to get ModuleFileName

Unable to parse FTP file list

Unable to parse token length

Unable to read the CSeq header: [%s]

Unable to receive SOCKS5 sub-negotiation response.

Unable to receive initial SOCKS5 response.

Unable to send initial SOCKS5 request.

Unable to set private key file: '%s' type %s

Unable to use client certificate (no key found or wrong pass phrase?)

Undocumented error - A connection attempt failed because the connected party did not properly respond after a period of time,

 or the established connection failed because the connected host has failed to respond.

Undocumented error - A message sent on a datagram socket was larger than the internal message buffer or some other network limit,

 or the buffer used to receive a datagram was smaller than the datagram itself.

Undocumented error - A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. By calling shutdown a partial close of a socket is requested,

 which is a signal that sending or receiving,

 or both have been discontinued.

Undocumented error - A socket operation was attempted to an unreachable host.

Undocumented error - An attempt was made to access a socket in a way forbidden by its access permissions. An example is using a broadcast address for sendto without broadcast permission being set using setsockopt(SO_BROADCAST). Another possible reason for the WSAEACCES error is that when the bind function is called (on Windows NT 4 SP4 or later),

 another application,

 service,

 or kernel mode driver is bound to the same address with exclusive access. Such exclusive access is a new feature of Windows NT 4 SP4 and later,

 and is implemented by using the SO_EXCLUSIVEADDRUSE option.

Undocumented error - An existing connection was forcibly closed by the remote host. This normally results if the peer application on the remote host is suddenly stopped,

 the host is rebooted,

 the host or remote network interface is disabled,

 or the remote host uses a hard close. This error may also result if a connection was broken due to keep-alive activity detecting a failure while one or more operations are in progress. Operations that were in progress fail with WSAENETRESET. Subsequent operations fail with WSAECONNRESET.

Undocumented error - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full.

Undocumented error - Some invalid argument was supplied (for example,

 specifying an invalid level to the setsockopt function). In some instances,

 it also refers to the current state of the socketfor instance,

 calling accept on a socket that is not listening.

Undocumented error - The attempted operation is not supported for the type of object referenced. Usually this occurs when a socket descriptor to a socket that cannot support this operation is trying to accept a connection on a datagram socket.

Undocumented error - The requested address is not valid in its context. This normally results from an attempt to bind to an address that is not valid for the local computer. This can also result from connect,

 sendto,

 WSAConnect,

 WSAJoinLeaf,

 or WSASendTo when the remote address or port is not valid for a remote computer (for example,

 address or port 0).

Undocumented error - The system detected an invalid pointer address in attempting to use a pointer argument of a call. This error occurs if an application passes an invalid pointer value,

 or if the length of the buffer is too small. For instance,

 if the length of an argument,

 which is a sockaddr structure,

 is smaller than the sizeof(sockaddr).

Undocumented error - This error is returned from operations on nonblocking sockets that cannot be completed immediately,

 for example recv when no data is queued to be read from the socket. It is a nonfatal error,

 and the operation should be retried later. It is normal for WSAEWOULDBLOCK to be reported as the result from calling connect on a nonblocking SOCK_STREAM socket,

 since some time must elapse for the connection to be established.

Undocumented error - Too many open sockets. Each implementation may have a maximum number of socket handles available,

 either globally,

 per process,

 or per thread.

Undocumented error - Typically,

 only one usage of each socket address (protocol/IP address/port) is permitted. This error occurs if an application attempts to bind a socket to an IP address/port that has already been used for an existing socket,

 or a socket that was not closed properly,

 or one that is still in the process of closing. For server applications that need to bind multiple sockets to the same port number,

 consider using setsockopt (SO_REUSEADDR). Client applications usually need not call bind at all connect chooses an unused port automatically. When bind is called with a wildcard address (involving ADDR_ANY),

 a WSAEADDRINUSE error could be delayed until the specific address is committed. This could happen with a call to another function later,

 including connect,

 listen,

 WSAConnect,

 or WSAJoinLeaf.

Unknown SSL protocol error in connection to %s:%ld 

Unknown error %d (%#x)

Unrecognised start state '

Unrecoverable error in call to nameserver

Views/Battle Cinematic Event/Enabled/Enable All

Voice_chat_enable <

bool>



WARNING! About to preprocess %S,

 but this is not writeable!  Check it out of perforce then ignore this error to continue.

Weapon bone is displayed between start and end times

 set value to weapon bone index

Weapon bone is spliced relative to hip between start and end times

 set value to weapon bone index

Weapon bone is spliced relative to left hand between start and end times

 set value to weapon bone index

Weapon bone is spliced relative to right hand between start and end times

 set value to weapon bone index

Wildcard - START of %s

Last update: 16/11/2024