Andydigital
-
Posts
1,227 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Andydigital
-
-
Just remove the whole line that says Patchsimfriction.
-
Yes, but also read further through that thread and take notice of posts 8 and 9 seeing as you have been using a patched sim1.dll
-
A quick search of the forum got me this;
http://forum.simflight.com/topic/75702-dynamic-friction-with-fsuipc-4923/?hl=dynamicfriction
-
Restore the original sim1.dll file and use the dynamicfrictions.lua instead it much better and more sophisticated than then version you are trying to use now.
-
For some reason Simconnect was not installed when you updated or installed version 2.1, please ask for help at the P3D forums for advice on how to install Simconnect. This is a known 2.1 issue (for a few people) and finding the remedy over at the official forums shouldn't take you too long.
-
I'm talking about default mouse look in FSX Pete, I don't use these functions in FSUIPC. But I thought I'd mention how I circumvented the issue in the past.
-
Swap the middle mouse button to another button in your mouse software if you can, that's what I did with my Logitech G700S, I use the mouse wheel click for very rarely used features just because of that zoom problem. I use it to toggle between DPi levels and have middle click on one of the other buttons now instead.
-
Actually I just remembered RXP doesn't support the Tab key so you are more limited in key assignment numbers, but it is still possible, you will just have to remove some of the default keys from FSX itself, 90% of them are never used anyway.
-
I don't think FSX crashing, it's probably minimising because of the keys used, Emutec shouldn't be using Win + 7 or any other such Win key combinations as those keys are reserved for use by the Windows operating system itself. Win +7 will actually cause your 7th from left quick launch icon program to load or minimise depending on its current state. Use Tab, CTRL and Shift and combinations there of as modifiers instead if you are stuck for modifier keys to use and don't use the ALT key either as that will cause the FSX menu to appear.
Unfortunately RealityXP only allow you to control their excellent gauges with keystrokes as mouse macros don't work and stupidly they do not support joystick devices being assigned directly either.
-
You can't, A2A broke the facility, the above fix is just to get the brakes working properly so you can actually stop the plane. You can't release the parking brake with the pedals unfortunately, but at least you can still use the facility with all your other aircraft.
-
-
Thanks Pete, I should have known better.
-
Pete can this BrakeReleaseThreshold= feature be used in a profile section? If not is there any chance it can be made to work in a profile so that A2A C172 users can disable this feature for this aircraft. I find it very useful in the rest of my aircraft and its not needed with the 172 because they already simulate this feature, I think that is why there is this clash. Thanks.
-
It's a bug in P3Dv2 that will be fixed by Lockheed Martin in their first update due in the near future.
-
Remove the \ from the beginning of the line before the word FSLabs it shouldn't be there.
-
Check your computer time then, if the PC clock time and date is set to a date before you purchased your key from Simmarket then the key will fail validation.
-
Press the opposite set button first, it sounds like you are setting a maximum instead of a minimum (or vice versa) for the direction you are moving your axis.
-
It can use any port you like as long as there is nothing else on your PC that is already using that port for something else unrelated to FSX. Use the default MSFS selected port of 4506.
By the way my name is Andy, its in my signature, Andydigital is just my screen name.
-
I don't fly online so I have no experience with IVAP, but it may be a unique case in that it expects to find the simconnect.cfg file in its own folder, simply make a copy of the simconnect.cfg file from your Documents folder and paste it to the IVAP folder you mention above. Hopefully that fixes it.
All apps should be using the same Simconnect port number, in your case 4506. Simconnect is more or less the same as WideFS from FSUIPC, i.e. only one port it used to link the FS server PC to the Client PC i.e. where you are running your maps and other FS related addons. It doesn't matter what the port number is as long as it is configured the same at both FSX server and client PC. The port must also must not be being used by some other program/processes that are not related to simconnect. I know that sounds confusing, but multiple programs designed to use Simconnect can share the same port, other none FS programs that don't use Simconnect cannot share ports at the same time.
-
Make backups of everything just in case it does stop working and you can then restore everything, but yes by my understanding of Simconnect most of the above is correct. Do not delete the simconnect.ini file, its not doing any harm, I believe that is just for logging purposes, so removing it won't do an harm either.
Also this below needs the red section removing, and the edit needs making in orange;
simconnect.cfg path: C:\Users\[user]\Documents -> the file now gets completely deleted ?
[simConnect]
Protocol=IPv4
Address=my FSX server adressPort=500 <-------- change this to 4506 the same as the simconnect.xml above.
MaxReceiveSize=4096
DisableNagle=0
[simConnect.1]
Protocol=IPv4
Address=my FSX server adress
Port=6811
MaxReceiveSize=4096
DisableNagle=0
[simConnect.2]
Protocol=IPv4
Address=my FSX server adress
Port=4506
MaxReceiveSize=4096
DisableNagle=0simconnect.cfg path: C:\Program Files (x86)\IVAO\IvAp v2 -> without entering my FSX server adress, IvApV2 does not connect online at clients computer -> the file now gets completely deleted ?
Yes as far as I understand it you shouldn't need the above in the IVAP folder. As I said though make backups of stuff that you delete so you can restore things if my advice is bad, I'm fairly certain its not though.
-
See my previous post, you only require one port for all programs, I don't know where you got the simconnect.1 simconnect.2 business from but its not required.
-
Simconnect only needs one connection and one port to service all addons that use simconnect as a means of interfacing with FSX, you are not required to open multiple ports for diffferent programs.
-
Your file looks like this, everything in red text can be deleted as it is not required.
<?xml version="1.0" encoding="windows-1252"?>
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<Disabled>False</Disabled>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>my FSX server adress</Address>
<MaxClients>64</MaxClients>
<Port>500</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>my FSX server adress</Address>
<MaxClients>64</MaxClients>
<Port>6811</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>my FSX server adress</Address>
<MaxClients>64</MaxClients>
<Port>445</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>my FSX server adress</Address>
<MaxClients>64</MaxClients>
<Port>4506</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Auto</Protocol>
<Scope>local</Scope>
</SimConnect.Comm>
</SimBase.Document>Here is what mine looks like;
<?xml version="1.0" encoding="Windows-1252"?>
<SimBase.Document Type="SimConnect" version="1,0">
<Descr>SimConnect</Descr>
<Filename>SimConnect.xml</Filename>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>IPv4</Protocol>
<Scope>global</Scope>
<Address>192.168.1.114</Address>
<MaxClients>64</MaxClients>
<Port>4506</Port>
<MaxRecvSize>4096</MaxRecvSize>
<DisableNagle>False</DisableNagle>
</SimConnect.Comm>
<SimConnect.Comm>
<Disabled>False</Disabled>
<Protocol>Auto</Protocol>
<Scope>local</Scope>
</SimConnect.Comm>
</SimBase.Document> -
Also looking at your first post with the Simconnect.xml, if yours really looks like that then it is surprising it works at all, you repeated the same code many times over with different ports in each section. Please see the ASN manual for the correct format of that file, yours is far too long.
Strange problem with DynamicFriction.lua
in FSUIPC Support Pete Dowson Modules
Posted
Even though the brakes message is not showing on the screen it is still possible for the brakes to bind ever so slightly if you haven't created a big enough null zone for your pedals. I'd try making the null zone bigger and assign the brakes through FSUIPC not in FSX, remember to recalibrate after Reversing the axis if needed.