Bugs and issues Nordic 1.0
-
Hey Guys,
I just loaded up a BARCAP mission out of BODO (F16RNoAF) and noticed that the right wingtip station (9 I think) was not showing a loaded missile when viewed from the cockpit. I tested with an AIM9 and AIM120B, both did not show in the view, but were definitely loaded on the SMS. They showed up when looking from external orbit view [Key 9]. Has anyone else seen this? Just wanted to check if it was my local installation. I have attached some screen shots.
Thanks to all involved in creating this theatre, awesome work :drink:
Cheers!
Dave -
The first and biggest problem seems to be that there is no Nordic map to choose from, so I cannot choose any of the airfields in the theater. Until there is a Nordic map to choose from it may be a waste of time listing all the faults. WDP seems to be looking for all sorts of files in other theaters.
-
I used both WDP and MC with this theater. WDP gives me this warning , the data in the datacard for the flights I created looked valid, albeit as long as the aircraft you are using is present in the database. Looking at the warning message WDP uses Korea DB so you might have some problems or invalid data for some types of aircraft. Did not test. MC ran without problems (so far), the only thing I did is resize the map, it comes 2000x2000 and MC requires 2048x2048.
-
Falcas really helped us getting mc to run with nordic. aside from that map size issue it runs fine i used it a lot. but WDP isnt going to work right with our db if its based on another. this will be a favor to ask Falcas. add that to the list.
-
bugs page is still open for issues check post one. I will be checking bugs page very often, dont feel like you will be a drop in the bucket here. I am less likely to miss a bug if its in this thread,
cheers
-
I need someone to upload either their entire Nordic Campaign-NTO folder or just the Save0.cam and Save0.tri files.
I’m getting a CTD in this campaign Russian Bear at the very beginning 0905. Want to make sure I don’t have bogus files.
Thanks,
C9
-
@Cloud:
I need someone to upload either their entire Nordic Campaign-NTO folder or just the Save0.cam and Save0.tri files.
I’m getting a CTD in this campaign Russian Bear at the very beginning 0905. Want to make sure I don’t have bogus files.
Thanks,
C9
PM me your email and I will send them to you directly.
-
Email has been sent.
-
I have no sounds in viggen pit, switches and engine, sound is just in external view
-
Just checked, out of curiosity, and all internal sounds are OK in my setup (regular Realtek HD Audio on-board sound card, 2 speakers + sub, Win7x64)
-
For your DB issues list.
1985 Soviet Bear Campaign
The following equipment did not exist in 1985:NATO
Remove Weapons- AIM-120
- IRIS-T
- JDAMS (GBU-31, GBU-32, GBU-38, GBU-54)
- GBU-39 SDB
- CBU-87
- CBU-97
- CBU-103
- CBU-105
- Taurus KEPD 350 (Tornado)
Remove Aircraft
- F-16 Block 52+ CFT
- F-16 AM
- A-10C
- Saab 340 AEW&C
- E-8C JSTARS
Add Aircraft/Weapons
- F-16A Block 5, 10, 15 (Norway/Denmark)
- Aim-9P
- F-15C (USA)
- A-10A (USA)
- F-16C Block 25 (USA)
- HARMs would be carried by the F-4G
Remove Ground Vehicles
- M2A2
- M2A3
Remove SAMs
- Avenger
SOVIET
Remove Weapons- AA-12 Adder
- AS-17A
- AS-17P
- AS-18
- Sorbtsiya wingtip Jammers
I don’t know much about russian bombs
Remove Aircraft
- Mi-28N
Remove Ground Vehicles
- BMP-3
Remove SAMs
- SA-15
-Add SA-6 , SA-11 ?
I’ve probably missed some, but this would be a good start
I like 80’s campaigns -
Just checked, out of curiosity, and all internal sounds are OK in my setup (regular Realtek HD Audio on-board sound card, 2 speakers + sub, Win7x64)
ok I solved with sound setup sliders. Thanks
-
I put the havoc in because it was from 1982 but I don’t know when it was in combat readiness. I will update page one Saturday. I think I can make a Cwc (vintage) object folder db without the actual db file and direct cwc tdf to two different directions to get models from nto and get stats from cwc.
Thanks for the detailed list.
-
I put the havoc in because it was from 1982 but I don’t know when it was in combat readiness. I will update page one Saturday. I think I can make a Cwc (vintage) object folder db without the actual db file and direct cwc tdf to two different directions to get models from nto and get stats from cwc.
Thanks for the detailed list.
https://sputniknews.com/onlinenews/2006053048833202/
Russia received their first Mi-28 prototype in 2004 and it entered service in 2006
-
If we need two object folders to pull off early version . . that is really going to bump up the size of the installer. I might suggest we look at two totally separate installers then … the size of the installer at the moment is about 2.3 GB and this would nearly double with a new objects folder. An alternative would be to re-engineers some a/c and rename and then have two different eras of the same a/c ect . . . with different loadouts and such. I think there are enough CTs that are still sort of unused that we can pull this off. There is still a lot of Isreali Theater stuff and excess stuff we don’t/won’t use to repurpose it. But, it would need to be looked at. The easiest and quickest course of action would be two separate theaters for maximum accuracy/validity of a/c wpns etc.
-
Ac with different loadouts - may create new Squadron unit+ new SSD record.
-
https://sputniknews.com/onlinenews/2006053048833202/
Russia received their first Mi-28 prototype in 2004 and it entered service in 2006
wow! thanks my research was wayy off! no havocs in old corps. gotcha.
-
check out the objects folder in carrier ops ito theater. i was able to change loadouts with f4browse and falcon edit. but all models come from uri_ba’s theater. all we need in the cwc is a very small sized objects folder. im going to make some examples and see what you think. we can make a whole new theater if you want. but i dont think its necissary.
-
OK I did it with a 3.15 mb objects folder added to cwc art folder and took away aim120 from noaf f16 for test. seems to be working fine. edit: used f4browse to recalculate this time.
-
Ac with different loadouts - may create new Squadron unit+ new SSD record.
a/c vehicle will have set CT record –with type/subtype/specific . . . that has to sync with unit and flt CTs, adding another sqd record also needs CT record added with the same subtype/specific introduces a conflict with one vehicle CT using the the same flt/sqd specific numbers. That may test fine but I would prefer to always keep all aircraft vehicles as complete sets of type/subtype/specifics to avoid accidental edits and conflicts. I sorted out several of these conflicts in early DB work and prefer not to bring them back in.