Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Topics - VanFanel1980mx

#1
I'll be releasing partial but functioning stuff I make here, this could be considered "open beta" so to speak, report any problems and all.

Yavin Hills - Conquest Level
version: 0.1
This one is very basic, Medium size level, 7 control zones, all content here is basic for now, no custom sides or anything, no vehicles for now, any feedback for vehicles and other elements is welcome, other than that have fun, I have been getting some BSODs but it is apparently due to the way I made my PC work with Zero Editor, if you get BSODs please tell me.
>>DOWNLOAD HERE<<
#2
I have gotten many BSODs lately while testing a mod map, different map each time, the only consistent traits are the use of lighting and other settings from shipped maps (to have a sun, water, and grass) but according to google some other people have the same problem, it seems to always be related to affinity, the downside of playing the Steam version in this case is how Steam locks the affinity options from the task manager on games, time to get a crack I guess.

If you have experienced BSODs while playing please leave a comment just to confirm.
#3
SWBF2 Modding / SWBF2 ZE "fix" - Runs on Windows 7
April 29, 2015, 12:41:20 PM
My specs

Windows 7 Ultimate 64-bit SP1
Intel Core i5 4430 @ 3.00 Ghz
8GB RAM DDR3

DELL Monitor 1708FPBLK

NVIDIA Driver 353.06
GeForce GTX 650 2047MB
SLI Disabled

On-Board Intel HD Graphics 4600*

.NET Framework versions
4.5
4.5.1
4.6
4.6.1

The fix? well, first of all I had the on-board graphics enabled, then I connected a VGA Cable to the free VGA input on my monitor since the NVIDIA card is connected through DVI.

Now ZeroEditor runs, need to test it and all but no more runtime error, no compatibility mode, no admin elevation, nothing, just plugged in the on-board graphics, please tell me if you get it working (assuming you didn't), looks like NVIDIA was still the problem.