High-speed holoemitter

[Fizyk]

Update bump.

I've added the feature that ZeikJT suggested, byte 1 now returns the number of used point. I have also added 2 inputs, "Active" and "Reset", so that you can reset it and turn on/off in a non-high-speed way.

[ZeikJT]

Update bump.

I've added the feature that ZeikJT suggested, byte 1 now returns the number of used point. I have also added 2 inputs, "Active" and "Reset", so that you can reset it and turn on/off in a non-high-speed way.

Hooray! Sounds awesome. Great work.

[jamescorbett]

In the wiremod extras svn please.

[Anticept]

Due to the potential abuse of this addon, please add a convar that could either disable the addon, or prevent too much from being drawn at once.

Added to UWSVN.

[Fizyk]

Thanks

I added a convar, hsholoemitter_max_points, that lets you set maximum number of rendered points. Updated holoemitter is in the attachment in the first post. I can't test it right now, so I'm not sure everything is ok, but it should be.

EDIT: Tested, the convar works.

[Fizyk]

Update bump!

This update fixes usermessage spam when updating holoemitter's point list too fast. Also it adds the requested concommand, which AFAIK is still not committed. Please commit (Anticept?), because I don't have commit access.

EDIT: There seems to be some bug with the convar, it looks like it's working in single player only. I'm looking into it now, when I manage to fix it I will update the files in the attachment.

EDIT2: Ok, it now works in multiplayer too.

EDIT3: Removed attachment, most recent version is in the UWSVN.

[E_net4]

I've been trying to make this work for some time now. It simply won't turn on. I tried using both ways to turn it on (1st memory cell and Active input), but no points show up at all.

[Fizyk]

It's because it has no points in the memory by default. You need to put some in there by setting cells 5,6,7 to coordinates of the first point, 7,8,9 - second point etc., and put number of points to cell 4 (if it's 0, like when you spawn it, it means there are no points in the memory, and so the holoemitter doesn't display anything).

[E_net4]

I did just that. Allow me to insert my code here. It's supposed to display a single dot in (2,2,2):

DATA;

define holo,65536
define holo_point,65538

CODE;

main:
 mov EAX,holo
 mov #EAX,1   //Active
 mov EAX,holo_point
 mov #EAX,1   //Point size
 inc EAX
 mov #EAX,0   //Show Beam
 inc EAX
 mov #EAX,1   //Number of points
 //Point 1
 inc EAX
 mov #EAX,2   //X
 inc EAX
 mov #EAX,2   //Y
 inc EAX
 mov #EAX,2   //Z 
jmp main;

The CPU is linked to an address bus, Memory1 is linked to the holoemitter, offset is 0, size is 2048, IIRC.

[Fizyk]

Try increasing point size to something like 10, it may be hard to see a single point that is this small and not moving. But if it's not it, then I don't know what's happening, I had no problems with it. I'll check if everything works, maybe some update broke it or whatever.

EDIT: Indeed something is broken, I'm looking into it now.

EDIT2: It was a problem with the convar that I added, it got lost somewhere when holoemitters were moved to "Wire - Render" tab, fixed it and committed, thanks for the information