Jump to content
RKSL Studios Community

Archived

This topic is now archived and is closed to further replies.

RKSL News Bot

EuroFighter Typhoon FGR4 V2.601

Recommended Posts

Hello everyone...okay I am a noob from the states. LOL. Love the Typhoon because of its power and elegance. I noticed that one of the typhoons is missing the default texture or am I loading this wrong? I completely reinstalled the software and deleted all mods so this is a fresh installation. Here is the error I get for the Typhoon FGR4 (SR1):

Cannot load texture

rksl\rksl_typhoon_raf\data\6sqdrn_efa_ext1_co.paa

If someone would be kind enough to give me some insight to add a texture to this plan I would greatly appreciate it (the plane is invisible) LOL.

Trod

Share this post


Link to post
Share on other sites

It's just a typo in the config really, where 6sqdrn_efa_ext1_co.paa should be 06sqdrn_efa_ext1_co.paa. Until Rock releases an updated plugin to resolve the issue, you can easily apply a manual fix in the mission editor by using the setobjecttexture command to change the path to the correct texture:

this setObjectTexture [0, "rksl\rksl_typhoon_raf\data\06sqdrn_efa_ext1_co.paa"]

Likewise you can assign any of the other squadron textures listed in the RAF Plugin Documentation and the aircraft will use that texture instead of the default one.

Share this post


Link to post
Share on other sites

Hi guys, we've been loving this bit of kit using it in our Operations (Will have some tasty footage to follow hopefully!) but all of a sudden after the introduction of enemy AI we had a spam on the RPT which completely totalled our server with desync issues and then made it crash was just hoping for some help!

[THIS MIGHT BE THE CAUSE OF THE SERVER DESYNC]

Ref to nonnetwork object 1ca3c800# 2001670: rksl_invtarget.p3d

Ref to nonnetwork object 25adf200# 2001673: rksl_invtarget.p3d

Ref to nonnetwork object 30848f00# 2001675: rksl_invtarget.p3d

Ref to nonnetwork object 30848800# 2001677: rksl_invtarget.p3d

Ref to nonnetwork object 1ca3e400# 2001679: rksl_invtarget.p3d

Ref to nonnetwork object 1ca3f900# 2001681: rksl_invtarget.p3d

Ref to nonnetwork object 1ca3c800# 2001670: rksl_invtarget.p3d

Ref to nonnetwork object 25adf200# 2001673: rksl_invtarget.p3d

Ref to nonnetwork object 30848f00# 2001675: rksl_invtarget.p3d

Ref to nonnetwork object 1ca3e400# 2001679: rksl_invtarget.p3d

Ref to nonnetwork object 1ca3f900# 2001681: rksl_invtarget.p3d

Ref to nonnetwork object 1ca3c800# 2001670: rksl_invtarget.p3d

Ref to nonnetwork object 25adf200# 2001673: rksl_invtarget.p3d

Ref to nonnetwork object 30848f00# 2001675: rksl_invtarget.p3d

Ref to nonnetwork object 30848800# 2001677: rksl_invtarget.p3d

Thanks again guys for the awesome work, hope we can get it fixed!

Cheers

Bradley

Share this post


Link to post
Share on other sites

I'll have to check with UNN. "Ref to nonnetwork object" isnt an error i know anything about.

I'll get back to you asap.

Can you give us the server RPT?

Were you using any custom addons?

What sort of mission are you using? ie heavily scripted? do you spawn the RKSL aircraft?

Share this post


Link to post
Share on other sites

Hi,

Ref to nonnetwork object 30848800# 2001677: rksl_invtarget.p3d

That's caused by the flare object, each flare object is created local to the client. It isn't an error message just something that's written out to the log. I don't know if anything has changed in recent patches, but it should not crash the server. If you don't fire off any flares and the server still crashes, it won't be down to that.

Share this post


Link to post
Share on other sites

Hi guys,

Thanks for your quick responses!

Rock, we use our own custom mod pack so there are a few things. We have noticed when the Typhoon is placed on a map it overwrites the flare key ® to just the Typhoon so we have to assign the vanilla flare key to another key (c for example). I.e. to release flares on say the Hercules we would have to press the c key as only R works on the Typhoon.

RKSL Aircraft weren't spawned and it was a Co-Op mission. It may be heavily scripted.

The server took a dump after that was spammed after missiles were launched towards the Typhoon to which the server then died completely. When we've had no missiles launched towards it, yet had 70+ people on training there have been no issues. We love this aircraft a ton but we're a bit snookered if we can't use it with enemy missile launchers. Any ideas?

Thanks again.

Share this post


Link to post
Share on other sites
Rock, we use our own custom mod pack so there are a few things. We have noticed when the Typhoon is placed on a map it overwrites the flare key ® to just the Typhoon so we have to assign the vanilla flare key to another key (c for example). I.e. to release flares on say the Hercules we would have to press the c key as only R works on the Typhoon.

This is more UNN's territory than mine but just a few questions...

Are you running ACE or any other mod that alters the vanilla game?

How are you binding keys? The reason I ask is I cannot replicate this in any way. I've just run a test with all the stock planes and helos + the Typhoon. I have no issue.

What other addons are you using?

RKSL Aircraft weren't spawned and it was a Co-Op mission. It may be heavily scripted.

There was an init related bug reported but that was only with the old flare system. Are you sure you are running only the v2.600+ packs?

The server took a dump after that was spammed after missiles were launched towards the Typhoon to which the server then died completely. When we've had no missiles launched towards it, yet had 70+ people on training there have been no issues. We love this aircraft a ton but we're a bit snookered if we can't use it with enemy missile launchers. Any ideas?

Can you swap out the plane for a stock one and re-run the mission to see if it crashes without the flares?

Share this post


Link to post
Share on other sites

We do run ACE along with a few of our own custom mods.

We do also use the GLT addon in conjunction with the Typhoon so we can conduct CAS Strikes. We use our own modpack, then all the cbas, ace, acex and acre. The only time this issue has reared its head was when we took to theater and were engaged by enemy aircraft/missile sites. When the flares deployed, it seemed to crash the server. This issue only happened when missiles were fired towards the Typhoon.

I believe we had a similar experience with the Merlin a while back whereby some errors were also noted in the RPT log;

Error in expression

_Flares=_pRadar>

Error position:

_Flares=_pRadar>

Error Zero divisor

Error in expression

_Flares=_pRadar>

Error position:

_Flares=_pRadar>

Error Zero divisor

Error in expression

_Flares=_pRadar>

Error position:

_Flares=_pRadar>

Error Zero divisor

Error in expression

_Flares=_pRadar>

Error position:

We've played it again with normal ArmA planes with no crashes or RPT errors. These were solely caused by the Typhoon on this occasion. May conduct further tests into if it is just the plane itself or the OPFOR elements' AA/AAA assets that cause the Typhoon to spaz out due to incompatibility or conflicting modpacks.

Share this post


Link to post
Share on other sites
_Flares=_pRadar>

Error Zero divisor

Error in expression

_Flares=_pRadar>

Error position:

We've played it again with normal ArmA planes with no crashes or RPT errors. These were solely caused by the Typhoon on this occasion.

I'm a bit confused, are you saying you see the above script errors in the RPT when flying the Tornado. Or are you just seeing the server messages you posted previously?

BTW What AAA addons are you using?

Share this post


Link to post
Share on other sites
We do run ACE along with a few of our own custom mods.

Based of past experience I'm willing to bet thats most of the problem. Everytime I've come across problems like this its been down to ACE conflicts. It messes everything up. The Key bindings issue especially is common to ACE.

But I'll bow to UNN's experience here.

I believe we had a similar experience with the Merlin a while back whereby some errors were also noted in the RPT log;

Again, are you sure you are running ONLY the latest flares that come with the 2.601 Typhoon?

Share this post


Link to post
Share on other sites

The problem isn't ACE itself I don't think. We're going to see if its the incompatibility between a 3rd party OPFOR AA/AAA unit as we believe that's what caused the Merlin's issue last time. But to be on the safe side, we may as well test all avenues.

The Typhoon seems to overwrite the vanilla flare button on other aircraft. If it isn't on a map, the vanilla button works. As soon as the Typhoon is on then vanilla button is replaced.

We are running the latest flares for both Aircraft but the Merlin is yet to be tested. I'm currently testing a few things now and will let you know the outcome.

Cheers

Share this post


Link to post
Share on other sites

Sorry to double post too but I can message our Server logs to you if need be to examine? We're not running the latest CBA's/ACE too as it requires the end-users to utilise the A2 Beta's to game which until the official patch release is something that isn't feasible to the unit.

Share this post


Link to post
Share on other sites
The problem isn't ACE itself I don't think. We're going to see if its the incompatibility between a 3rd party OPFOR AA/AAA unit as we believe that's what caused the Merlin's issue last time. But to be on the safe side, we may as well test all avenues.

All I am saying is that previous experience suggest that the likeliest culprit is ACE. Tested in the Vanilla games with Non-ACE addons no one reports any issues.

If you do find that its a 3rd party AAA addon I would like to know which ones and why.

The Typhoon seems to overwrite the vanilla flare button on other aircraft. If it isn't on a map, the vanilla button works. As soon as the Typhoon is on then vanilla button is replaced.

We are running the latest flares for both Aircraft but the Merlin is yet to be tested. I'm currently testing a few things now and will let you know the outcome.

Again i really don't think its the RKSL system because, as I explained earlier:

  1. I cant reproduce it in the Vanilla environment
  2. We don't use any fancy key mapping just the basic user defined action keys supported by the default game.
  3. No one else has reported this behavior outside of ACE before.

Do you have any other (conflicting) keys bound to Action 20?

Share this post


Link to post
Share on other sites

The problem isn't ACE itself I don't think. We're going to see if its the incompatibility between a 3rd party OPFOR AA/AAA

If you can let us know the Addon or better still package up the exact same version you are using and send it to us, I can try and reproduce the problem. Having to download ACE isn't really an option, but a couple of standalone addons is ok.

The Typhoon seems to overwrite the vanilla flare button on other aircraft. If it isn't on a map, the vanilla button works. As soon as the Typhoon is on then vanilla button is replaced.

We are running the latest flares for both Aircraft but the Merlin is yet to be tested. I'm currently testing a few things now and will let you know the outcome.

Is that sometime you can reproduced in Single Player using the Vanilla ARMA2 editor with Just the Typhoon addons installed? That's is, place a Typhoon and place and A10, run the mission and try to launch flares from the A10?

Share this post


Link to post
Share on other sites

We've sussed it out the server crash. This is due to the Takistani Army Extension and clashing mods.

SA-6, SA-2 SAM missile systems cause the server to crash when it comes into contact with RKSL stuff. We believe this is down to their new little config to make their missiles more deadlier clashes with the RKSL 'nothing can touch me' flares causing the RPT errors to spam. This is also further continued on the MIG-21's they have in this addon pack.

I do believe we have some custom key mapping that may interfere with flares due to our in house stuff. I believe this is the addon that has created the errors;

http://www.armaholic.com/page.php?id=16236

Thanks for your time gents. Keep firing things back if you want to know more and I'll try and ascertain more info. Messiah regularly checks in on us so feel free to call over whenever.

Share this post


Link to post
Share on other sites
We've sussed it out the server crash. This is due to the Takistani Army Extension and clashing mods.

SA-6, SA-2 SAM missile systems cause the server to crash when it comes into contact with RKSL stuff.

What leads you to this conclusion?

We believe this is down to their new little config to make their missiles more deadlier clashes with the RKSL 'nothing can touch me' flares causing the RPT errors to spam. This is also further continued on the MIG-21's they have in this addon pack.

Would you mind explaining the bit in bold?

I do believe we have some custom key mapping that may interfere with flares due to our in house stuff. I believe this is the addon that has created the errors;

http://www.armaholic.com/page.php?id=16236

Thanks for your time gents. Keep firing things back if you want to know more and I'll try and ascertain more info. Messiah regularly checks in on us so feel free to call over whenever.

As much info as you can give us would help. I'm especially keen to understand what clashes and why. Please let us know what you find.

Share this post


Link to post
Share on other sites

Thanks for getting back

We believe this is down to their new little config to make their missiles more deadlier clashes with the RKSL 'nothing can touch me' flares

Pity they didn't mention it to us. I went to some length to allow you to adjust the lethality of incoming missiles. Unlike other flares we can open up all aspects of the system to adjustment.

Share this post


Link to post
Share on other sites

Hello, I'm also part of the 16AA and one of the people over there who's attempted to look for a solution to the issue we faced.

Let me first quickly apologize if this was thrown into the wrong thread, it probably could of used a thread of its own as I'm uncertain how relevant it is to the majority of people coming by.

This is what happened in basic, we had a MIG from this addon http://www.armaholic.com/page.php?id=16236

Engage the newest version of the RKSL Typhoon -shortly- after the server came to a halt and crashed.

The following error was spammed across Clients and Server RPT.

Ref to nonnetwork object 59e42b00# 2041165: rksl_invtarget.p3d

Let me just point out, we -don't- know or have solid evidence on what exactly cursed it.

We simply got observations.

We just know removing the Typhoon has fixed it, adding the above RPT-spam, it seemed obvious to some people that it was the issue.

could replacing the MIG with a default something-something fix the issue?

No idea, further testing is required, it seems you been contacted pre-maturely.

We're obviously thankful for any help received but right now, I personally feel we could do plenty more in terms of bug-hunting and finding a solution here our self.

//That includes removing ACE from the equation.

And I'm slightly embarrassed that you guys have been asked for help without us fully understanding what happened.

Resulting in some shit-poor 'bug' report thrown into an announcement post.

I cannot apologize enough.

Edit:

Obviously a clash has occurred where in the RKSL Typhoon is involved, we just don't fully understand where it happened.

Share this post


Link to post
Share on other sites
We believe this is down to their new little config to make their missiles more deadlier clashes with the RKSL 'nothing can touch me' flares

Well it isn't rare for people to believe all sorts of odd things, so don't feel bad about that. Look on the bright side, not being able to clearly say what is on your mind, in an adult and straightforward manner, would be far more worrying, don't you think?

Hello, I'm also part of the 16AA and one of the people over there who's attempted to look for a solution to the issue we faced.

Hi Knudsen,

We have noticed when the Typhoon is placed on a map it overwrites the flare key ®

I can confirm the above bug and have fixed it, thanks for reporting it.

However I can't confirm any of the other issues you reported. We think we know where the problem lies, but without examples of the RPT files you have mentioned, there isn't much else we can say. I have downloaded and tested the PRACS addons alongside the RKSL addons, without any problems or any of the RPT messages you have quoted (Again for the record they aren't errors, at best they are just server messages, at worse warnings. But they can be avoided none the less).

If you still can't provide examples of the RPT's we can at least provide an update to the default key assignment issue, we suspect that may also fix the entries in the RPT. But can't say if this will also fix the server lag.

If you're are interested I can also provide you with details on how to configure the effectiveness of the RKSL flares using something as simple as the missions description.ext.

Share this post


Link to post
Share on other sites
Hello, I'm also part of the 16AA and one of the people over there who's attempted to look for a solution to the issue we faced.

Let me first quickly apologize if this was thrown into the wrong thread, it probably could of used a thread of its own as I'm uncertain how relevant it is to the majority of people coming by.

I can split it off/delete easily enough once we bottom this issue so no harm done.

This is what happened in basic, we had a MIG from this addon http://www.armaholic.com/page.php?id=16236

Engage the newest version of the RKSL Typhoon -shortly- after the server came to a halt and crashed.

Well I've gone through the Taki Extension again ( I helped Eddie with some of it). On the face of it there is nothing that would cause a crash that I can see. It has minimal scripting so its unlikely to be the culprit.

The following error was spammed across Clients and Server RPT.

Ref to nonnetwork object 59e42b00# 2041165: rksl_invtarget.p3d

That isnt actually an error. Its a debug message confirming the creation of a local object on the clients so will have no detrimental effects on the server. But again, if you can show us the offending server.rpt and a client RPT we can help narrow it down.

Let me just point out, we -don't- know or have solid evidence on what exactly cursed it.

We simply got observations.

Judging from 16aaBradley's comments it was implied you had. Thank you for stating that all the same.

We just know removing the Typhoon has fixed it, adding the above RPT-spam, it seemed obvious to some people that it was the issue.

could replacing the MIG with a default something-something fix the issue?

Well its obvious there is some issue. But whos it is, is not clear. It seems we get the "obvious" accusation leveled at us a lot by "some" people. Usually followed with little or no evidence so you'll understand that we'd like to get this proved or disproved so we can debunk it or fix the underlying issue.

Can I ask when you re-tested with fewer players did the server crash a second time?

Can you give us the RPT files?

No idea, further testing is required, it seems you been contacted pre-maturely.

We'd rather be contacted than left in ignorance :D If only to stop further damage to our reputation.

Honestly, I dont think its the Typhoon or the flares. I'm sure we would have heard something by now. Since the 2.601 release its been downloaded over 6000 times. No one else has reported any issue like this.

UNN and I have spent the last hour trying to recreate it with "no joy" but going off the info you have provided so far:

  1. Bradley's post here: http://www.rkslstudios.info/public-foru ... t=10#p3018 - That message is likely caused by someone running 2.03 or 2.02 version of the flares. 2.04 (The current version) fixed that bug. it is only possible with an older version. Check to make sure your user base is using the correct version and no one is loading an older version. This is common with anyone using Wings of Russia or Sarmat IL76 addons since they use a hacked version of the old flares system.
  2. Do you allow people to run custom addons too?
  3. I'm not aware of anyone else having server issues with the latest Takistan Extension but I'll have a word with Eddie/WLD427 tonight on TS and see if he is aware of anything but as I said I seriously doubt thats the cause.
  4. Having 71 people on the server is rather alot. In my nearly 10 years experience I've never managed to get anything stable over 40-50 with custom addons. I'd be interested to know what server spec and connection you use because that is an impressive number.

We're obviously thankful for any help received but right now, I personally feel we could do plenty more in terms of bug-hunting and finding a solution here our self.

//That includes removing ACE from the equation.

And I'm slightly embarrassed that you guys have been asked for help without us fully understanding what happened.

Resulting in some shit-poor 'bug' report thrown into an announcement post.

I cannot apologize enough.

I've got 3 other people testing for use right now. So I'd like some specifics if possible so we can compare results. Regardless I'd very much like to see what you find either way.

Edit:

Obviously a clash has occurred where in the RKSL Typhoon is involved, we just don't fully understand where it happened.

Until you can test with a similar server load OR replicate the crash with just one or two players, It still feels like you are playing cluedo in the dark and pointing at the "unpopular guy" when the lights come up to me :P

Until then you have more than just the RKSL Typhoon as a suspect. ACE, TK-Ex custom addons, server issues, mismatched addons. Sound packs. Effects packs there are many more.

Share this post


Link to post
Share on other sites

Hey Rock/UNN.

We did a bunch of testing with the same mission, same server.

To explain things a bit at numbers between 1-10 players (Or there about) our missions usually run at a decent 50 FPS server wise.

With drops as stuff happens, but usually a stable number is achieved between 40-50 FPS.

When loaded between 55-65 players (Depending on the day/time of year, and what have you)

We are usually located around 10-20 FPS.

Everything was pretty much as usual.

Now we managed to recreate the events without fault with 1-3 players, we could of gone higher but there really wasn't any need.

Now this time the server -didn't- crash however a FPS drop from 50 to 18 would usually occur.

The drop in frames would happen exactly as a missile was fired at the Typhoon, and would last until the missile was no more.

Every time.

With past experience in mind a heavy drop in FPS can be 'fatal' for a server when running at the lower numbers such as between 10-20 FPS.

Where when we where only 3 players the server had room to recover.

_______________________

After knowing how to recreate the event we decided to try and eliminate some of the variables by removing content from the mod-pack.

Now to you some of the obvious ones may be 'ACE' or of the sort but seeing as we already 'name and shamed' the Taki Extension mod.

I found it best to either confirm that the issue laid there, or clear their name if not.

I can confirm though without the Taki Extension mod, but with all our other mods enabled the issue was still present.

So I doubt there is any fault of theirs in any of this.

And I do apologize if anyone took offence to the early claims, they where not meant as a pointed finger, rather to describe the 'event' accurately as it happened.

As a quick little note, I know you mentioned the line we posted was a debug message, but the thing appears in numbers of up to 200 within -seconds.-

Could this be an issue?

We ran out of time for the day so sadly I cannot comment if disabling ACE would help the issue.

It's not a 'quick' task either sadly, as I have to make our mod-pack none-ace compatible before being able to run with as many of our other mods as possible to further eliminate the issue.

Just throwing our mod-pack out of the window and ACE with it, would just leave me @RKSL and that surely will work with no fault at all, so there is little point in that. :)

__________

Probably time I answer some of those questions!

First of all here is a link for those logs: https://www.dropbox.com/s/aollao6bvvoqg ... freeze.zip these are from the actual night of the original crash and not the test sessions. You'll find one from our headless client, and one from our server.

UNN and I have spent the last hour trying to recreate it with "no joy" but going off the info you have provided so far:

  1. Bradley's post here: http://www.rkslstudios.info/public-foru ... t=10#p3018 - That message is likely caused by someone running 2.03 or 2.02 version of the flares. 2.04 (The current version) fixed that bug. it is only possible with an older version. Check to make sure your user base is using the correct version and no one is loading an older version. This is common with anyone using Wings of Russia or Sarmat IL76 addons since they use a hacked version of the old flares system.
  2. Do you allow people to run custom addons too?
  3. I'm not aware of anyone else having server issues with the latest Takistan Extension but I'll have a word with Eddie/WLD427 tonight on TS and see if he is aware of anything but as I said I seriously doubt thats the cause.
  4. Having 71 people on the server is rather alot. In my nearly 10 years experience I've never managed to get anything stable over 40-50 with custom addons. I'd be interested to know what server spec and connection you use because that is an impressive number.

1. We use signature checking, so our version is the same across the board and the latest at that.

2. See 1. But no, we do have some 'optionals' but these are very light and usually limited to the like of fthud, the biggest one being JSRS 1.42.

3. You're corret, we cleared them off the list, again I apologize to make the 'blame' go that way.

4. It's no easy feat, we are lucky that a lot of modders out there (You included!) allow us to make very small but required changes to configs or indeed help us when issues arise to keep the experience enjoyable.

We also had to result to signature checking as people connecting with wrong mods is literally capable of pulling the server offline.

Other then that, we get mods build in house by many talented people, some I'm sure you been in contact with before.

Server specs are as follows;

Intel i5-2500 @ 3.3Ghz - Quad Core.

8GB RAM PC2-1066

500GB 7200 RPM HDD.

Windows 7, x64

I'm uncertain of the connection, but it's quite a beefy one.

Thank you a lot for giving it some attention, I really appreciate it.

Hopefully I didn't miss anything above, and wasn't either to obvious or to confusing.

@UNN

In regards to this below:

If you're are interested I can also provide you with details on how to configure the effectiveness of the RKSL flares using something as simple as the missions description.ext.

That would be really neat, I'm sure some of our guys would love to know how. :)

Share this post


Link to post
Share on other sites

×