STANDALONE STANDALONE-VIDEO-CALL-SYSTEM Version 3.0 (2 Viewers)

[zDjdani816]

-=Stripped Content=-
FIXED IT SO ITS WORKING WITH OPEN TCP AND UDP PORT, AND OPTION FOR PROXY SERVER.

It is a standalone resource and works with any framework and can be hooked to any Lua NUI-based phone given you can develop the hook for it.

Features

• Real-time video call experience using WebRTC technology.
• Zero interaction with your phone's VoIP meaning it will work in parallel with any VoIP (TokoVoip, Mumble, WebRTC etc.).
• Ability to switch between the back and the front camera.
• Dynamic adjustment to center properly in various resolutions.
• Plug-and-play integration with phones that we offer out-of-the-box hooks for.
• Color filters (grayscale, sepia, invert, saturate, etc.).
• Image filters with real-time player ped face-tracking (dog, cat, etc.).
• Optimized for a balance between quality and performance.
• Routing via a TURN server to protect your players' privacy never revealing their IP address.
• Automatic video reconnect in case of WebRTC disconnects with a minimal video downtime.
• An experimental camera mode that allows the player to move while video calling.

1. Make sure you have yarn in your resources folder.
2. Download cs-video-call and place it in your resources folder.
3. Add ensure cs-video-call to your server's configuration file before ensuring your phone.
4. Edit your phone's __resource.lua or fxmanifest.lua file and add '@cs-video-call/client/hooks/core.lua' as the last client script and '@cs-video-call/server/hooks/core.lua' as the last server script.
5. Edit your phone's NUI file (usually index.html) and add <script type="text/javascript" src="nui://cs-video-call/client/hooks/core.js"></script> right before </body>.
6. Check the config.js file inside cs-video-call for further configuration and read through all options and their comments as some are very important for the setup process and adjust them to your setup and preferences.
7. Given you're using the internal solution, open the required port (by default 34540; incoming - inbound) in your firewall, both TCP and UDP.
8. Run the command refresh and the command ensure cs-video-call and wait until yarn finishes the installation.
9. If your phone uses an animation loop you may need to edit it (usually found in an animation.lua file) and add a not CS_VIDEO_CALL.ACTIVE check before playing an animation to ensure an animation glitch does not occur when the video call camera is opened.
10. Ensure your phone.
    
    
    
11. Important Information
    • The video call will not work without the proxy server, direct P2P is not given as an option in order to protect players' anonymity.
    • Besides your proxy server's network speeds which must match the amount of maximum active transmissions you want to have (you can limit those in the configuration), you will also need to consider bandwidth consumption if that is not unlimited by your host.
    • If your phone's fx_version is cerulean or higher, you will need to setup the video call proxy server as HTTPs or override the WebSocket URL to pass through Cloudflare to mimic HTTPs in order to use it, alternatively you can set the version to bodacious if you don't have a use case for cerulean.
    • Due to WebSocket usage and imposed restrictions you will not be able to test the resource if you connect to your server via localhost, unless you connect to it via your external IP address and configure it accordingly.
    • Video render lag / freezes may be caused in very high resolutions or in very low-spec systems.
    • When video call is active, the player who transmits the video cannot move. This is default GTA:V camera behavior. You can try using experimental camera mode which allows the player to move however it might not be as smooth as the native one.
    • The video call works using game capture (similar to screenshot-basic), the player sees whatever it's on the game of the other player. That includes visual settings / mods, game drawings / UIs but not NUIs.
    • If your server is running behind a reverse proxy that you have no control over and cannot handle an extra TCP / UDP port as required by the resource, your only option may be to externally host the video call's proxy server in a different machine (for example a cheap VPS with enough bandwidth / network to work within your own limits).
    • When a player initiates a video call, it will consume approximately 2mbps of their upload speed for the transmission and when they are in a call and the other player initiates a video call it will consume approximately 2mbps of their download speed.
    • Your players may be prompted by their Windows Firewall to allow a connection the first time a video call happens, this is due to the WebRTC protocol connection and cannot be circumvented.
    • There are checks in place to ensure that the transmitted video feed is legitimate and is coming from the game itself, however since the client sends it, it cannot be fully trusted.
      
      
      
    • Frequent Issues & Questions
      
      Q: I can see the video call button and all seem to work but when the other player opens their camera all I see is a black screen, why?
      A: Black screen issue is usually related to UDP blocking, complex network setup or anti-DDoS protection. Try a different port, preferably in a high range to see if that will resolve your issue and make sure that port is open for both TCP and UDP protocols. If that doesn't work then your best solution here may be to externally host the video call's proxy server in a different machine (for example a cheap VPS with enough bandwidth / network to work within your own limits).
      
      Q: I've done everything but I cannot see a video call button, what's wrong?
      A: Not seeing a video call button may be related to a couple of things, first make sure the proxy server's port is open and accessible and your network configuration is reflected in the config. Then make sure your phone events and DOM elements are properly reflected in the hook and that the hook is configured properly. Finally if you are connecting via localhost that also may be why, connect via your external IP address and configure the resource accordingly.
      
      Q: My yarn is repeatedly trying to install the resource, what do I do?
      A: This seems to be a current bug in the yarn resource (will PR it eventually) related to package.json and the server's time zone related to the time zone of the system you copied the resource from. Edit package.json and just add or remove a space character, save it and the issue will go away.

nice

 

[Minion]

-=Stripped Content=-
FIXED IT SO ITS WORKING WITH OPEN TCP AND UDP PORT, AND OPTION FOR PROXY SERVER.

It is a standalone resource and works with any framework and can be hooked to any Lua NUI-based phone given you can develop the hook for it.

Features

• Real-time video call experience using WebRTC technology.
• Zero interaction with your phone's VoIP meaning it will work in parallel with any VoIP (TokoVoip, Mumble, WebRTC etc.).
• Ability to switch between the back and the front camera.
• Dynamic adjustment to center properly in various resolutions.
• Plug-and-play integration with phones that we offer out-of-the-box hooks for.
• Color filters (grayscale, sepia, invert, saturate, etc.).
• Image filters with real-time player ped face-tracking (dog, cat, etc.).
• Optimized for a balance between quality and performance.
• Routing via a TURN server to protect your players' privacy never revealing their IP address.
• Automatic video reconnect in case of WebRTC disconnects with a minimal video downtime.
• An experimental camera mode that allows the player to move while video calling.

1. Make sure you have yarn in your resources folder.
2. Download cs-video-call and place it in your resources folder.
3. Add ensure cs-video-call to your server's configuration file before ensuring your phone.
4. Edit your phone's __resource.lua or fxmanifest.lua file and add '@cs-video-call/client/hooks/core.lua' as the last client script and '@cs-video-call/server/hooks/core.lua' as the last server script.
5. Edit your phone's NUI file (usually index.html) and add <script type="text/javascript" src="nui://cs-video-call/client/hooks/core.js"></script> right before </body>.
6. Check the config.js file inside cs-video-call for further configuration and read through all options and their comments as some are very important for the setup process and adjust them to your setup and preferences.
7. Given you're using the internal solution, open the required port (by default 34540; incoming - inbound) in your firewall, both TCP and UDP.
8. Run the command refresh and the command ensure cs-video-call and wait until yarn finishes the installation.
9. If your phone uses an animation loop you may need to edit it (usually found in an animation.lua file) and add a not CS_VIDEO_CALL.ACTIVE check before playing an animation to ensure an animation glitch does not occur when the video call camera is opened.
10. Ensure your phone.
    
    
    
11. Important Information
    • The video call will not work without the proxy server, direct P2P is not given as an option in order to protect players' anonymity.
    • Besides your proxy server's network speeds which must match the amount of maximum active transmissions you want to have (you can limit those in the configuration), you will also need to consider bandwidth consumption if that is not unlimited by your host.
    • If your phone's fx_version is cerulean or higher, you will need to setup the video call proxy server as HTTPs or override the WebSocket URL to pass through Cloudflare to mimic HTTPs in order to use it, alternatively you can set the version to bodacious if you don't have a use case for cerulean.
    • Due to WebSocket usage and imposed restrictions you will not be able to test the resource if you connect to your server via localhost, unless you connect to it via your external IP address and configure it accordingly.
    • Video render lag / freezes may be caused in very high resolutions or in very low-spec systems.
    • When video call is active, the player who transmits the video cannot move. This is default GTA:V camera behavior. You can try using experimental camera mode which allows the player to move however it might not be as smooth as the native one.
    • The video call works using game capture (similar to screenshot-basic), the player sees whatever it's on the game of the other player. That includes visual settings / mods, game drawings / UIs but not NUIs.
    • If your server is running behind a reverse proxy that you have no control over and cannot handle an extra TCP / UDP port as required by the resource, your only option may be to externally host the video call's proxy server in a different machine (for example a cheap VPS with enough bandwidth / network to work within your own limits).
    • When a player initiates a video call, it will consume approximately 2mbps of their upload speed for the transmission and when they are in a call and the other player initiates a video call it will consume approximately 2mbps of their download speed.
    • Your players may be prompted by their Windows Firewall to allow a connection the first time a video call happens, this is due to the WebRTC protocol connection and cannot be circumvented.
    • There are checks in place to ensure that the transmitted video feed is legitimate and is coming from the game itself, however since the client sends it, it cannot be fully trusted.
      
      
      
    • Frequent Issues & Questions
      
      Q: I can see the video call button and all seem to work but when the other player opens their camera all I see is a black screen, why?
      A: Black screen issue is usually related to UDP blocking, complex network setup or anti-DDoS protection. Try a different port, preferably in a high range to see if that will resolve your issue and make sure that port is open for both TCP and UDP protocols. If that doesn't work then your best solution here may be to externally host the video call's proxy server in a different machine (for example a cheap VPS with enough bandwidth / network to work within your own limits).
      
      Q: I've done everything but I cannot see a video call button, what's wrong?
      A: Not seeing a video call button may be related to a couple of things, first make sure the proxy server's port is open and accessible and your network configuration is reflected in the config. Then make sure your phone events and DOM elements are properly reflected in the hook and that the hook is configured properly. Finally if you are connecting via localhost that also may be why, connect via your external IP address and configure the resource accordingly.
      
      Q: My yarn is repeatedly trying to install the resource, what do I do?
      A: This seems to be a current bug in the yarn resource (will PR it eventually) related to package.json and the server's time zone related to the time zone of the system you copied the resource from. Edit package.json and just add or remove a space character, save it and the issue will go away.

nice

 

[Minion]

ty bro

 

[Minion]

i love you so much

 

[Minion]

nice nice

 

[Minion]

thank you

 

[programok3]

nice

 

[surajraj9]

Great Post

 

[MrPatate03]

lol

 

[DrMacs]

work?

 

[DrMacs]

link not working

 

[moath0129]

thx

 

[moath0129]

thx

 

[zana kurd]

-=Stripped Content=-
FIXED IT SO ITS WORKING WITH OPEN TCP AND UDP PORT, AND OPTION FOR PROXY SERVER.

It is a standalone resource and works with any framework and can be hooked to any Lua NUI-based phone given you can develop the hook for it.

Features

• Real-time video call experience using WebRTC technology.
• Zero interaction with your phone's VoIP meaning it will work in parallel with any VoIP (TokoVoip, Mumble, WebRTC etc.).
• Ability to switch between the back and the front camera.
• Dynamic adjustment to center properly in various resolutions.
• Plug-and-play integration with phones that we offer out-of-the-box hooks for.
• Color filters (grayscale, sepia, invert, saturate, etc.).
• Image filters with real-time player ped face-tracking (dog, cat, etc.).
• Optimized for a balance between quality and performance.
• Routing via a TURN server to protect your players' privacy never revealing their IP address.
• Automatic video reconnect in case of WebRTC disconnects with a minimal video downtime.
• An experimental camera mode that allows the player to move while video calling.

1. Make sure you have yarn in your resources folder.
2. Download cs-video-call and place it in your resources folder.
3. Add ensure cs-video-call to your server's configuration file before ensuring your phone.
4. Edit your phone's __resource.lua or fxmanifest.lua file and add '@cs-video-call/client/hooks/core.lua' as the last client script and '@cs-video-call/server/hooks/core.lua' as the last server script.
5. Edit your phone's NUI file (usually index.html) and add <script type="text/javascript" src="nui://cs-video-call/client/hooks/core.js"></script> right before </body>.
6. Check the config.js file inside cs-video-call for further configuration and read through all options and their comments as some are very important for the setup process and adjust them to your setup and preferences.
7. Given you're using the internal solution, open the required port (by default 34540; incoming - inbound) in your firewall, both TCP and UDP.
8. Run the command refresh and the command ensure cs-video-call and wait until yarn finishes the installation.
9. If your phone uses an animation loop you may need to edit it (usually found in an animation.lua file) and add a not CS_VIDEO_CALL.ACTIVE check before playing an animation to ensure an animation glitch does not occur when the video call camera is opened.
10. Ensure your phone.
    
    
    
11. Important Information
    • The video call will not work without the proxy server, direct P2P is not given as an option in order to protect players' anonymity.
    • Besides your proxy server's network speeds which must match the amount of maximum active transmissions you want to have (you can limit those in the configuration), you will also need to consider bandwidth consumption if that is not unlimited by your host.
    • If your phone's fx_version is cerulean or higher, you will need to setup the video call proxy server as HTTPs or override the WebSocket URL to pass through Cloudflare to mimic HTTPs in order to use it, alternatively you can set the version to bodacious if you don't have a use case for cerulean.
    • Due to WebSocket usage and imposed restrictions you will not be able to test the resource if you connect to your server via localhost, unless you connect to it via your external IP address and configure it accordingly.
    • Video render lag / freezes may be caused in very high resolutions or in very low-spec systems.
    • When video call is active, the player who transmits the video cannot move. This is default GTA:V camera behavior. You can try using experimental camera mode which allows the player to move however it might not be as smooth as the native one.
    • The video call works using game capture (similar to screenshot-basic), the player sees whatever it's on the game of the other player. That includes visual settings / mods, game drawings / UIs but not NUIs.
    • If your server is running behind a reverse proxy that you have no control over and cannot handle an extra TCP / UDP port as required by the resource, your only option may be to externally host the video call's proxy server in a different machine (for example a cheap VPS with enough bandwidth / network to work within your own limits).
    • When a player initiates a video call, it will consume approximately 2mbps of their upload speed for the transmission and when they are in a call and the other player initiates a video call it will consume approximately 2mbps of their download speed.
    • Your players may be prompted by their Windows Firewall to allow a connection the first time a video call happens, this is due to the WebRTC protocol connection and cannot be circumvented.
    • There are checks in place to ensure that the transmitted video feed is legitimate and is coming from the game itself, however since the client sends it, it cannot be fully trusted.
      
      
      
    • Frequent Issues & Questions
      
      Q: I can see the video call button and all seem to work but when the other player opens their camera all I see is a black screen, why?
      A: Black screen issue is usually related to UDP blocking, complex network setup or anti-DDoS protection. Try a different port, preferably in a high range to see if that will resolve your issue and make sure that port is open for both TCP and UDP protocols. If that doesn't work then your best solution here may be to externally host the video call's proxy server in a different machine (for example a cheap VPS with enough bandwidth / network to work within your own limits).
      
      Q: I've done everything but I cannot see a video call button, what's wrong?
      A: Not seeing a video call button may be related to a couple of things, first make sure the proxy server's port is open and accessible and your network configuration is reflected in the config. Then make sure your phone events and DOM elements are properly reflected in the hook and that the hook is configured properly. Finally if you are connecting via localhost that also may be why, connect via your external IP address and configure the resource accordingly.
      
      Q: My yarn is repeatedly trying to install the resource, what do I do?
      A: This seems to be a current bug in the yarn resource (will PR it eventually) related to package.json and the server's time zone related to the time zone of the system you copied the resource from. Edit package.json and just add or remove a space character, save it and the issue will go away.

thank you thats nice

 

[zana kurd]

thank you thats nice

 

[ninja12345]