Jump to content

Recommended Posts

Posted

I'm having a problem with my network config. file after a fresh install this information appears in the Config/network/config file. An everything works great. However, after a online session the file changes (see below).

-- This file was automagically generated. Edit with care. :)

gameTimeout = 30;

maxPacketSize = 500;

playerName = "Shotgun";

idleTimeout = 120;

stats {

enable = true;

file = "Temp/mp_log.txt";

};

chat {

height = 95;

delay = 10000;

};

serverFiles = {

[1] = "./Bazar/Names.lua";

[2] = "./Bazar/Racks.lua";

[3] = "./Bazar/Types.lua";

[4] = "./Config/Weapons/Guns.lua";

[5] = "./Config/Weapons/DrawInfo.lua";

[6] = "./Config/Weapons/Bombs.lua";

[7] = "./Config/Planes/Pylons.lua";

[8] = "./Config/Planes/Damage.lua";

[9] = "./Config/Planes/AIControl.lua";

[10] = "./Config/Export/Config.lua";

[11] = "./Config/View/Server.lua";

[12] = "./Config/View/Labels.lua";

[13] = "./Config/World/World.lua";

[14] = "./Config/Network/stats.lua";

};

configList = {

["xDSL 2048/2048 Kbit/s"] = {

downstream = 256000;

upstream = 256000;

};

["LAN 10 Mbit/s"] = {

downstream = 500000;

upstream = 500000;

};

["Modem 56.6K"] = {

downstream = 5000;

upstream = 3000;

};

["xDSL 128/128 Kbit/s"] = {

downstream = 16000;

upstream = 16000;

};

["Modem 33.6K"] = {

downstream = 3000;

upstream = 1000;

};

["LAN 100 Mbit/s"] = {

downstream = 5000000;

upstream = 5000000;

};

["xDSL 1024/128 Kbit/s"] = {

downstream = 128000;

upstream = 16000;

};

["xDSL 256/128 Kbit/s"] = {

downstream = 32000;

upstream = 16000;

};

};

client {

syncPing = 1;

type = "xDSL 128/128 Kbit/s";

livePing = 15;

port = 10308;

server = "";

serverList = {

[1] = "";

};

};

server {

type = "xDSL 256/128 Kbit/s";

name = "LockOn Server";

maxPlayers = 7;

port = 10308;

pingUpdate = 30;

interface = "All interfaces";

};

 

After flying online the Config/Network/Config file changes to this; for some unkown reason.

 

-- This file was automagically generated. Edit with care. :)

gameTimeout = 10;

maxPacketSize = 500;

playerName = "unknown";

idleTimeout = 120;

stats {

enable = false;

file = "";

};

chat {

height = 299;

delay = 0;

};

serverFiles = {

};

configList = {

};

client {

syncPing = 1;

type = "";

livePing = 15;

port = 10308;

server = "";

serverList = {

};

};

server {

type = "";

name = "";

maxPlayers = 32;

port = 10308;

pingUpdate = 30;

interface = "";

};

 

The kill information remains on the screen when this happen, currently the only way to fix ii is to reinstall the config. file. Any help would be appreciated.

 

 

Spoiler:

MSI Z790 Carbon WIFI, i9 14900KF, 64GB DDR4, MSI RTX 4090, VKB STECS Mk ll throttle, VKB Gunfighter Ultimate MCG Pro w/200mm Extension, Winwing Orion Rudder Pedals W/damper, Wingwin Monitors/MFD's, UTC MK II Pro, Virpil TCS Plus Collective, MSI 34" QD-OLED @240Hz monitor, Samsung 970 Pro M2 2TB (for DCS), Playseat Air Force Seat, KW-980 Jetseat, Vaicom Pro, Tek Creations panels and controllers.

 

Posted

Replace it with the original file. This has happened to me and several others. To my knowledge, a reason why it happens has never been discovered. If it changes back, keep replacing it.

Posted

The problem is this portion:

 

chat {

height = 95;

delay = 10000;

};

 

The height defines the distance from the top of your screen where the chat line appears, and delay is the time period how long the message will stay on the screen until it disappears.

 

The values

 

chat {

height = 299;

delay = 0;

};

 

will bring the message line into the middle of your screen and as the delay is set to 0, it will stay forever.

 

This is a known bug in FC, and the only cure ist to edit the file to the correct values, and then make it write protected .

We had this prob several times in our squad, occasionally with no specific reason, FC just does it from time to time. The write protection solved it for us.

kind regards,

Raven....

[sigpic]http://www.crc-mindreader.de/CRT/images/Birds2011.gif[/sigpic]

Posted
The problem is this portion:

 

chat {

height = 95;

delay = 10000;

};

 

The height defines the distance from the top of your screen where the chat line appears, and delay is the time period how long the message will stay on the screen until it disappears.

 

The values

 

chat {

height = 299;

delay = 0;

};

 

will bring the message line into the middle of your screen and as the delay is set to 0, it will stay forever.

 

This is a known bug in FC, and the only cure ist to edit the file to the correct values, and then make it write protected .

We had this prob several times in our squad, occasionally with no specific reason, FC just does it from time to time. The write protection solved it for us.

 

 

I reviewed the previous posts on the problem with the messages staying on the screen forever, and learned to replaced the values to 95 and 10000 which solved that problem temporary, but having to repeatedly to do this is a pain and a inconvenience everytime you want to go online.

 

 

Spoiler:

MSI Z790 Carbon WIFI, i9 14900KF, 64GB DDR4, MSI RTX 4090, VKB STECS Mk ll throttle, VKB Gunfighter Ultimate MCG Pro w/200mm Extension, Winwing Orion Rudder Pedals W/damper, Wingwin Monitors/MFD's, UTC MK II Pro, Virpil TCS Plus Collective, MSI 34" QD-OLED @240Hz monitor, Samsung 970 Pro M2 2TB (for DCS), Playseat Air Force Seat, KW-980 Jetseat, Vaicom Pro, Tek Creations panels and controllers.

 

Posted
The problem is this portion:

 

chat {

height = 95;

delay = 10000;

};

 

The height defines the distance from the top of your screen where the chat line appears, and delay is the time period how long the message will stay on the screen until it disappears.

 

The values

 

chat {

height = 299;

delay = 0;

};

 

will bring the message line into the middle of your screen and as the delay is set to 0, it will stay forever.

 

This is a known bug in FC, and the only cure ist to edit the file to the correct values, and then make it write protected .

We had this prob several times in our squad, occasionally with no specific reason, FC just does it from time to time. The write protection solved it for us.

 

 

How do you write protect this file? I'll give that a try :book:

 

 

Spoiler:

MSI Z790 Carbon WIFI, i9 14900KF, 64GB DDR4, MSI RTX 4090, VKB STECS Mk ll throttle, VKB Gunfighter Ultimate MCG Pro w/200mm Extension, Winwing Orion Rudder Pedals W/damper, Wingwin Monitors/MFD's, UTC MK II Pro, Virpil TCS Plus Collective, MSI 34" QD-OLED @240Hz monitor, Samsung 970 Pro M2 2TB (for DCS), Playseat Air Force Seat, KW-980 Jetseat, Vaicom Pro, Tek Creations panels and controllers.

 

Posted
Right-click on it and, in the Properties dialogue box that opens, look at the bottom line:: Attributes: "Read only". Checkmark it. Don't checkmark "Hidden".

 

Rich

 

Thanks a million! :thumbup:

 

 

Spoiler:

MSI Z790 Carbon WIFI, i9 14900KF, 64GB DDR4, MSI RTX 4090, VKB STECS Mk ll throttle, VKB Gunfighter Ultimate MCG Pro w/200mm Extension, Winwing Orion Rudder Pedals W/damper, Wingwin Monitors/MFD's, UTC MK II Pro, Virpil TCS Plus Collective, MSI 34" QD-OLED @240Hz monitor, Samsung 970 Pro M2 2TB (for DCS), Playseat Air Force Seat, KW-980 Jetseat, Vaicom Pro, Tek Creations panels and controllers.

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...