Nordic V2 bugs and issues
-
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.
-
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
Any chance we can get a quickfix for this bug? I’m guessing V3 will take some time to be released.
JayJay
-
I think the answer is all stated, import the SA-2 from Korea (and the SA-11 and SA-17). I’m not sure the devs of Nordic should give more details about that, it’s something you’d better get informed about, as it’s really better to know what you’re doing rather than following a list of tasks to tick.
-
I was hoping it was only the matter of replacing files with a patch.
I have no idea how to import these SAM’s. So unless someone can make an easy to follow guide, this will be “impossible”.I think the answer is all stated, import the SA-2 from Korea (and the SA-11 and SA-17). I’m not sure the devs of Nordic should give more details about that, it’s something you’d better get informed about, as it’s really better to know what you’re doing rather than following a list of tasks to tick.
-
Absolutely fantastic theater and congrats to the Nordic team first of all, really great professional quality and teamwork!
Now for 2 things I noticed during a ‘On the brink’ campaign flying F16-A from Langnes.
-After returning home from strike mission north flying in the area over the oil platforms, suddenly shot down by friendly fire. 4x SM2-MR missiles fired last one struck me (shown in debrief).
-Runways were destroyed by enemy, after being repaired and missions being created again, craters where still on runway in 3D that will destroy human aircraft on takeoff. (status is repaired in 2D though)Just to inform and help to improve, will do more flying next week.
Cheers Obi1
-
I have seen this problem with the craters in KTO; the runway was destroyed and subsequently repaired but the craters remained for some reason. 2D and MC showed runway repaired. In MC you can find a list called persistent objects, the craters are there and you can remove them from the specific airbase. You have to remove the craters one at the time.
-
hi my friends
why F-22 weapon bay doors is open in nordic
they must open only when i fire a weapon not only selecting it
i saw this before for B-1 Bay door
is it cause to increase F-22 radar Cs ?
how i can fix this
thank you for your answering and helping -
First Theater where i get a black screen!
Switching to Nordic: black screen. killing BMS. restart i have the UI.
Starting a CA: i have the Countdown BG , then BLACK screen, no loading screen, hear the sounds, so i’m in the 3d wold in the pit. ESC …E … BLACK… right corner …click click… (exit exit) back on dektop.I’m the only one???
When i switch to OMA no probs !!! -
Noticed that all weather fmap files are missing. At least one fmap file is needed when starting a new campaign in order to enable “Maps Auto Update” (F4Wx).
I imported the fmap files from Korea campaign, Maps Auto Update works OK.But the weather report is still missing from mission briefing :?
Hoping for a quickfix. The weather report often (at least for me) is an important factor when deciding what weapons to use.
JayJay
-
First Theater where i get a black screen!
Switching to Nordic: black screen. killing BMS. restart i have the UI.
Starting a CA: i have the Countdown BG , then BLACK screen, no loading screen, hear the sounds, so i’m in the 3d wold in the pit. ESC …E … BLACK… right corner …click click… (exit exit) back on dektop.I’m the only one???
When i switch to OMA no probs !!!Hi there.
Well do you have an AMD graphics card? IF yes, then DO NOT use any later Crimson driver from the 17.7.1!
This one (AMD Crimson driver 17.7.1) is the latest for the moment that works fine with some 3rd party theaters like Balkans, Nordic, POH e.t.c. ;).
Nikos. -
Noticed that all weather fmap files are missing. At least one fmap file is needed when starting a new campaign in order to enable “Maps Auto Update” (F4Wx).
I imported the fmap files from Korea campaign, Maps Auto Update works OK.But the weather report is still missing from mission briefing :?
Hoping for a quickfix. The weather report often (at least for me) is an important factor when deciding what weapons to use.
JayJay
if you copy the weather.b file from kto camp folder to both nordic camp folders this will work. thanks for the advice on the other. this is just another thing we never noticed , but easy to fix