Should have left it as was station and star stuttering is now not so livable as before.
Last edited:
Patch Notes Update Powerplay Update 1.3.08 Incoming - 10.30 BST
- Thread starter Michael Brookes
- Start date
- Status
Should have left it as was station and star stuttering is now not so livable as before.
Could you post a link where the XML file is explained as it's difficult to know what goes there? Also I read once that there's a way to create a user version of this file with customers settings that don't get wiped on an update but again no link to reference this. Thanks.
** Damn, had to verify my install as the upgrade hung and it wiped the file so not even the new settings are there and I have no idea of the syntax **
Last edited:
If you mean how to re-enable the shader caching it's here:
https://forums.frontier.co.uk/showthread.php?t=164760&p=2513014&viewfull=1#post2513014
There was a post somewhere about using AppConfigLocal.xml which I thought was a more elegant solution than editing AppConfig.xml, but this will do for now - thanks! Have some rep
There was a post somewhere about using AppConfigLocal.xml which I thought was a more elegant solution than editing AppConfig.xml, but this will do for now - thanks! Have some rep
Yes and I actually wrote such a post myself but can't find it now
As you said this update has overwritten the Local file (I thought the whole purpose of the Local file was that it wasn't overwritten - that'll teach me not to backup these files in future).EDIT: I'm fairly certain that this is what the AppConfigLocal.xml file should contain (have not tested at the time of writing):
<AppConfig>
<PlanetNoiseTextures
Enabled="auto"
ShaderWarmingEnabled="1"
ShaderWarmingDialogAnimTimeInMs="600">
<AutoDisableOnOsx>ATI Radeon HD 2400</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 2600 Pro</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 5770</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 5870</AutoDisableOnOsx>
<AutoDisableOnOsx>ATI Radeon HD 6800 Series</AutoDisableOnOsx>
<AutoDisableOnOsx>AMD Radeon HD 6970M</AutoDisableOnOsx>
<AutoDisableOnOsx>AMD Radeon HD 6870 Series</AutoDisableOnOsx>
<AutoDisableOnOsx>AMD Radeon HD 6xxx</AutoDisableOnOsx>
<AutoDisableOnOsx>Intel HD Graphics 3000</AutoDisableOnOsx>
<AutoDisableOnOsx>NVIDIA GeForce GT 120</AutoDisableOnOsx>
</PlanetNoiseTextures>
</AppConfig>
p.s. you can delete the AutoDisable lines if you are on PC not Mac.
Last edited:
Amazing FD! Always fix even the most minor things that other devs don't even come close to recognising. This actually happened to me, but was ok because I was able to jettison the cargo and switch ship and rebuy the same goods.
Also, wondering if any of those complex sounding fixes are going to fix the "sector" search bug on the galmap? Installing now to find out
Thank you for that, as I had the same problem. Very annoying of FD to reset this file when then failing to fix the shader problem properly (postponed to v1.4). I didn't like having to tinker with the computer code last time either.
Well my issue is still around after recent patch, which is a shame. Ive sent off yet another bug report.....6 weeks now and still cant wing on local network, getting quite tedious now to say the least.
I tried it in the < Network ... tag as in there, and it did nothing. Using the Port="xxxxx" attribute is still working. DID this make it into the patch ? If so, is there somewhere else it's meant to go ? No mention of RouterPort in the defauly AppConfig.xml.
FD - I have no idea what you done, but my stuttering is all but gone and my graphics performance greatly improved. Thank you, I just couldn't stop playing tonight.
Yes and I actually wrote such a post myself but can't find it now
And the AppConfigLocal.xml file goes in the same folder as AppConfig.xml?
Yep.
Sounds promising, maybe it was the low-level thread change. Going to try it now.
Yep - just did extensive testing - two people on same LAN and cannot Wing Up.
AppNetCfg.xml adds this line to each:
<AppNetCfg ip="####IP####" upnp="true" router="6" />
Wings used to be great before 1.3. Is there anything at all I can try? I am prepared to test ANYTHING to get this working again!
EDIT:::
I've been having a mess and tried editing appconfig.xml to disable upnp and set one PC to port 5100 and the other to 5101:
<Network
Port="5100"
upnpenabled="0"
LogFile="netLog"
DatestampLog="1"
>
</Network>
I then set up two UDP port forwards on the router and now wings work!
There was an initial delay of one PC taking a while to realize the other was online (even though it was receiving text chat messages from it) but that could just be because I'd left that PC on sat in docked for a while.
Anyway - looks like the problem is that upnp isn't handling more than one machine behind a network (which seems a bit mad as surely this happens at the FD offices all the time!)
Will write up a bug report tomorrow but it's now 3.20am
Can't wait to get a Wing on tomorrow eve!
Last edited:
I don't think this is the best place to ask, but will we be able to play with the Xbon-errr. Xbox people in the future? Or will it always be the way it is now.
The last official answer to that was that once XB1 is live we'll be playing in and affecting the same Galaxy, but at the present time they can't guarantee that we'll ever be cross playing in the same instances between PC/Mac and XB1, but neither are FD entirely ruling it out yet.
Is there going to be a fix or is there a work around for Delivery missions where the required cargo needs to be purchased but is not Sold by any local commodities market?
For instance last night picked up a Cargo transfer where I had to buy 3Cobalt around LHS 3447 sector island but None of the Markets would sell them. Even though they had stock!
For instance last night picked up a Cargo transfer where I had to buy 3Cobalt around LHS 3447 sector island but None of the Markets would sell them. Even though they had stock!
- Status