+- Discovery Gaming Community (https://discoverygc.com/forums)
+-- Forum: Discovery Development (https://discoverygc.com/forums/forumdisplay.php?fid=7)
+--- Forum: Discovery Mod General Discussion (https://discoverygc.com/forums/forumdisplay.php?fid=37)
+--- Thread: Raven Claw problem... (/showthread.php?tid=2282)
Raven Claw problem... - Mickk - 01-27-2007
The topic Description says it all really, I bought a 'Raven Claw' fighter today, switching from a Colonial Viper.
No problem with the guns at that point, as the game moved 2 guns into positions 7 & 8.
I then went out to Gas Miner Naha to get some Skyblast B, thinking that having 6 of those plus 2 Tizonas would be a really nice thing to have.
To my horror, it stopped mounting them after I had bought (and auto-mounted) 4!
I figured it was a glitch, bought 2 more guns and tried to mount them. No go.
I undocked then docked again. No go.
The funny thing is, it looks a lot like it will let me mount missiles on those gun/missile mounts :crazy:
The only thing I haven't tried (I'm about to) is getting out of the game, going back in and seeing if they will mount......
EDIT:
Ok, I've fixed the problem..... sort of.
I mounted 2 Skyblast A in position 7 & 8.
This still leaves the question of what is going on with those two mounts.
FYI, I *tried* to move the Tizonas to mounts 7 & 8....... No go, ended up with Tizonas on 1 & 2, Skyblast B on 3 -> 6 and Skyblast A on 7 & 8.
Wierd huh?
Raven Claw problem... - Fellow Hoodlum - 01-27-2007
Mickk, couple of us have had this problem in the past. It would appear that mounts seven and eight for
some reason, don't seem to like level nines guns.
It has been reported aswell, though I can't remember the outcome. Normally just use your choice of
level tens on there.
Best place for these types of problems is in the 'Bugs and Suggestions' thread, where most people would
see it, and where Igiss regularly reads.
Hoodlum
Raven Claw problem... - Doom - 01-27-2007
well it is not a bug...slots 7 and 8 can take only weapons level 1 to 8 and 10...
it is simply little glitch in the code for that ship...it is easily corrected and i have no doubt it will be in next release