I'm using this alongside robco certified with the compatibility patch but after hacking a robot, the option to talk to it stops working. Which makes it so that I can't further upgrade or pack a robot
Investigate longer... I found what in "robot in range scan" checks all creature's Refs in cell (GetFirstRef function), and then call GetDead function on each Ref but without check GetType == 43 or 44 (creature or leveled creature). Sometimes non-creature Refs may be scanned (engine bug?) and GetDead on it cause immediately game crash. In Project Nevada realized scan with GetType check for heat/em vision/target scan and it allways worked without crashes.
In this case piece of script must look as:
If rActor.GetType == 43 || rActor.GetType == 44 if rActor.GetIsCreatureType 6 && (rActor.GetDisabled == 0) && (fRange < 300) If rActor.GetDead != 1 if rRobot01 == 0 set rRobot01 to rActor set fRobot01Range to fRange elseif rRobot02 == 0 set rRobot02 to rActor set fRobot02Range to fRange elseif rRobot03 == 0 set rRobot03 to rActor set fRobot03Range to fRange elseif rRobot04 == 0 set rRobot04 to rActor set fRobot04Range to fRange elseif rRobot05 == 0 set rRobot05 to rActor set fRobot05Range to fRange elseif rRobot06 == 0 set rRobot06 to rActor set fRobot06Range to fRange elseif rRobot07 == 0 set rRobot07 to rActor set fRobot07Range to fRange elseif rRobot08 == 0 set rRobot08 to rActor set fRobot08Range to fRange elseif rRobot09 == 0 set rRobot09 to rActor set fRobot09Range to fRange endif set iRobotsInRange to iRobotsInRange + 1 endif endif endif
Hello! Marvelous modification! Great work! But I have a problem. While piggyback mode there is buggy control and no interface of HP, Weap type and signal loss. Actually, I use a Fate of Wanderer mods pack with some other mods including "self-made" (trying to make a short list of them). I tried to use a 4GB launcher - did not work (crash). How should I solve this proplem?
For the future, might I recommend getting FNVEdit? That tool will allow you to check stuff like this yourself, so you don't need to wait on anybody getting back to you.
That's an interesting question since Cyberian Dawn affects neither companions nor factions. Did you disable the robots' IFFs?
If not, please disable Cyberian Dawn and verify that the problem no longer occurs - if it still does then CD is not causing your problem.
If the problem does not persist after CD's deactivation, please reactivate CD and disable your other mods. From here if you still experience this problem please send me a PM and I'll see what I can do about it - if the problem does not persist, please reactivate each of your mods one by one until the problem presents itself again - once it's happening again send me a PM of whichever mod caused it and I will start on making a patch for it.
Give Feedback
129 comments
- The 4GB Launcher
- Making a clean save.
- Decreasing graphical settings. (This includes disabling texture packs)
Hope this helps.
No idea how fix it yet ( May be somebody help?
I found what in "robot in range scan" checks all creature's Refs in cell (GetFirstRef function), and then call GetDead function on each Ref but without check GetType == 43 or 44 (creature or leveled creature). Sometimes non-creature Refs may be scanned (engine bug?) and GetDead on it cause immediately game crash.
In Project Nevada realized scan with GetType check for heat/em vision/target scan and it allways worked without crashes.
In this case piece of script must look as:
But I have a problem. While piggyback mode there is buggy control and no interface of HP, Weap type and signal loss. Actually, I use a Fate of Wanderer mods pack with some other mods including "self-made" (trying to make a short list of them). I tried to use a 4GB launcher - did not work (crash).
How should I solve this proplem?
For the future, might I recommend getting FNVEdit? That tool will allow you to check stuff like this yourself, so you don't need to wait on anybody getting back to you.
If not, please disable Cyberian Dawn and verify that the problem no longer occurs - if it still does then CD is not causing your problem.
If the problem does not persist after CD's deactivation, please reactivate CD and disable your other mods. From here if you still experience this problem please send me a PM and I'll see what I can do about it - if the problem does not persist, please reactivate each of your mods one by one until the problem presents itself again - once it's happening again send me a PM of whichever mod caused it and I will start on making a patch for it.