Nordic V2 bugs and issues
-
Thanks for encouraging me, Starrats, and guess what, the problem is still there. I plugged an Xbox controller and tried to pop and disappear. The SA-2 site won’t let me go. ALTA airbase, approach from West, still the same thing. In a TE, with nothing else.
But the SA-6 works correctly. Thanks luke777 for suggesting that in private. The SA-6 spots me above the mountain, not behind, popping in and out several times, under exactly the same conditions as we had with the SA-2.
PS: some of you guys made me fly with an Xbox controller, The North doesn’t forget
PPS: some of you guys made me dodge SA-6s with a Xbox controller… now that’s a murder attempt
PPPS: Out of curiosity, I tested a jamming aircraft in Nordic V1, for what it’s worth, it worked correctly. It happened to be with the same SA-2.
-
@pat:
Hello,
when I download Nordic, I have a Nordic V2.0.RAR file and it says on BMS this: Extract the file and execute the install.
The problem is that after having “unzip” I do not have an installer but directly Add-On Nordic!
Is this normal?
thank you in advance. V2 has two files in the zip or rar file. if you unzip it a certain way it will create a folder. and in that folder are the source file and nordic v2 instaler exe. if this is not the case for you then something is wrong. i tested installer yesterday after dl it from Chuckles post, it worked fine. try again and take some pics of your process, because this not normal.
-
I plugged an Xbox controller and tried to pop and disappear.
Pure blasphemy!!! [emoji38]
Στάλθηκε από το MI 5 μου χρησιμοποιώντας Tapatalk
-
Maybe some height changes where done and some new created files fixed it?
Tapatalki did fix a large flat spot in the middle northern mountains and created new terrain files and .thr file for roads for v2. but i also tried that with v1 before the changes were made the first time i tested this issue. i guess with these speratic test results, i am going to leave it as a known bug until we figure out exactly what is going on.
-
Apparently not totally related to terrain, Starrats. I suppose you saw my last post
-
yes that you had correct response from sam radar in jammer plane but not the other. now i had correct response in those 3 jets i tested. i should try all jets in same alta sead flight. that would be jets have a possible prob. however if sa6 tracks correctly but not sa2, that kind of points to the sams. i will test against sa2 until i duplicate the mountain radar issue again. and make a broad comparison to the tests that work fine. this may produce a discrepency… i hope.
-
Yes, SA6 working with terrain and SA2 not. Anything else is just off topic really, including jammer aircrafts. It was just a personal interest in it.
-
?
building TE from scratch,
added Squadrons
Add Package, AWACS E3 Bad Timing,
Also had this problem in v1Why is it bad timing, I haven’t added Enemy Squadrons yet,?
Flight is well within engagement time settings, “Victory conditions”?Thank you in advance
-
?
building TE from scratch,
added Squadrons
Add Package, AWACS E3 Bad Timing,
Also had this problem in v1Why is it bad timing, I haven’t added Enemy Squadrons yet,?
Flight is well within engagement time settings, “Victory conditions”?Thank you in advance
Bad timing is a quite common problem, especially for tanker, AWACS, ELINT… Try fragging that flight near the squadron base, then move the patrol steerpoints where you need them. If you have trouble with take-off times (No slots available, damnit!), use Mission Commander to force them. Useful if you have to consent to a take-off time you wouldn’t want in the first place, to finally change it.
But if you post it here, you may have a problem specific to Nordic, which is surprising to the sound of it since it’s a common one, but who knows better than you?
-
?
building TE from scratch,
added Squadrons
Add Package, AWACS E3 Bad Timing,
Also had this problem in v1Why is it bad timing, I haven’t added Enemy Squadrons yet,?
Flight is well within engagement time settings, “Victory conditions”?Thank you in advance
. check to make sure it set to size 1 and on AEW\ABCCC and not FAC
-
I will do some tests this afternoon (UTC+1), I have an idea how to conduct the tests. Will post the results. Testing the TE I can confirm that the SA6 and the SA10 are masked correctly by the terrain.
Cheers
Luke
-
Hi
I have done some testing and this is what I could find out: single battalion radar is masked by the terrain and the mechanics work as they should; get some terrain between the aircraft and the SAM site and and the SAM loses lock and tracking, RWR goes blank.
With multiple battalions of different types things get weird; some types, namely SA2 SA11 SA17, keep lock and tracking trough the terrain. Missiles impact the terrain surface as they should, none goes trough solid rock as if it was not there, but if the missile trajectory takes it above the obstacle used to mask the radar then it homes in on the target.
I tested at 2 different locations with SA2 SA6 SA10 SA11 SA17, SA6 and SA10 being the types that work correctly alone or in combination with other types.Some screen shots front view and side view respectively, RWR screaming like an eagle the whole time.
Don’t know what to make of it.
Cheers
Luke
-
I think Lorik was right after all the sams themselves may be the issue and not any jet problem, I got the SA2 working good.(I think) still testing.
I still don’t know what exactly the issue is, but I imported SA2 info from KTO, (which tests fine) and now the issue is seemingly gone at first testing.
I tried the same of bk52 import before sa2 import and the issue was RWR always tracking behind the hills.
after testing all sams and seeing about replacing the all the f4 data where needed this bug may be fixed for v3
-
I think Lorik was right after all the sams themselves may be the issue and not any jet problem, I got the SA2 working good.(I think) still testing.
I still don’t know what exactly the issue is, but I imported SA2 info from KTO, (which tests fine) and now the issue is seemingly gone at first testing.
I tried the same of bk52 import before sa2 import and the issue was RWR always tracking behind the hills.
after testing all sams and seeing about replacing the all the f4 data where needed this bug may be fixed for v3
Big up!
-
I may have reported initially but Kaos (Luke) really had the different SAM idea after running tests himself. Also, the same issue may apply with SA-11 and SA-17 according to him, which is a solid statement in my understanding of BMS world :P.
-
Thanks to dfang the f35b afm is improved to keep wheels from sinking slightly into carrier or tarmac.
https://www.benchmarksims.org/forum/showthread.php?31862-Nordic-V2-bugs-and-issues&p=445429&viewfull=1#post445429 -
Thanks to dfang the f35b afm is improved to keep wheels from sinking slightly into carrier or tarmac.
https://www.benchmarksims.org/forum/showthread.php?31862-Nordic-V2-bugs-and-issues&p=445429&viewfull=1#post445429So - it gets the greenlight as is? If so I will put that in the installer as I start prepping for V3.0. Add to the DB bugs list the updated qty for aa-12’s for the internal bay from 1 to 3 for the Su-47 and Su-57. It is a super easy fix in DB.
-
as is looks good to me.
-
Weather is not displayed in the in-game briefing screen
-
shucks ! i thought we were done on ui. checking it out.